ADT3.3 Deployment Problems

[Anonymous]

OK, afeter several tries, and several reboots, and hte same errors coming up
again and again, I am tossing in the towe, and crying for help.

When I set up the network deployment image files, everythign appears to go
smoothly.

When I go to install on a client, I get an error that reads:
Error 1324. The Folder Path 'Program Files' contains an invalid character.

So, I went into the appsetup.inf, and changed the path to something that had
no blank spaces, and no parts of the path were longer than 8 characters
(what the heck, might as well make the path backwards compatible to DOS 1)

Then I try again, and get the same error, only this time, the problem path
is 'CD Manager.'
That pth is not spelled out in the appsetup.inf file. I did specify to
apply the CAD Manager Controls to Today, so I am expecting that to be the
problem. I'm about to create a whole new deployment location, with a fresh
new image, short path, no CAD Manager, etc. But even so, this is
ridiculous. Does anyone have a clue what has gone wrong?

[Anonymous]

Charles -

I'd highly recommend a new deploy image. I've had some problems with appsetup.inf files
in the past and I've generally found that it's been easier just to create a new deploy
than it is to try to fix and existing deploy that has never worked. If the appsetup.inf
got hosed somehow, it's fairly likely to assume that other stuff was also "broken" during
the deployment image creation. Was it heat near the server, solar flares, ozone depletion
who knows. Try creating the deploy again and let us know if that doesn't work (just
delete the old one, it's not doing any good anyway).

hth

jason martin
frankfurt-short-bruza

"Charles Prettyman" wrote in message
news:420B617AF0EAF0B44FCF7C968B0CC2C9@in.WebX.maYIadrTaRb...
> OK, afeter several tries, and several reboots, and hte same errors coming up
> again and again, I am tossing in the towe, and crying for help.
>
> When I set up the network deployment image files, everythign appears to go
> smoothly.
>
> When I go to install on a client, I get an error that reads:
> Error 1324. The Folder Path 'Program Files' contains an invalid character.
>
> So, I went into the appsetup.inf, and changed the path to something that had
> no blank spaces, and no parts of the path were longer than 8 characters
> (what the heck, might as well make the path backwards compatible to DOS 1)
>
> Then I try again, and get the same error, only this time, the problem path
> is 'CD Manager.'
> That pth is not spelled out in the appsetup.inf file. I did specify to
> apply the CAD Manager Controls to Today, so I am expecting that to be the
> problem. I'm about to create a whole new deployment location, with a fresh
> new image, short path, no CAD Manager, etc. But even so, this is
> ridiculous. Does anyone have a clue what has gone wrong?
>
>

[Anonymous]

I just did create a whole new deploy image, on a different drive. I used a
very simple path for hte program installation (D:\ADT33\)
and I did not apply the CAD manager controls to today.

Error 1324. The Folder Path 'CAD Manager' contains an invalid character.

reared its ugly head again!

I don't think it's even actually the Appsetup.inf. I was able to compare it
to one that worked for someone (Thanks for that Jason), and there are no
differences other than obvious stuff (who it's licensed to, server, ID, etc)

My next step is to set up all over again on a different machine. Even if I
eventually have to migrate people back to the server I've been trying (it's
a load balancing issue, but there may be other solutions to that)



"jason martin" wrote in message
news:9EA3148944E0B507446531C14A72DE8A@in.WebX.maYIadrTaRb...
> Charles -
>
> I'd highly recommend a new deploy image. I've had some problems with
appsetup.inf files
> in the past and I've generally found that it's been easier just to create
a new deploy
> than it is to try to fix and existing deploy that has never worked. If
the appsetup.inf
> got hosed somehow, it's fairly likely to assume that other stuff was also
"broken" during
> the deployment image creation. Was it heat near the server, solar flares,
ozone depletion
> who knows. Try creating the deploy again and let us know if that doesn't
work (just
> delete the old one, it's not doing any good anyway).
>
> hth
>
> jason martin
> frankfurt-short-bruza
>
> "Charles Prettyman" wrote in message
> news:420B617AF0EAF0B44FCF7C968B0CC2C9@in.WebX.maYIadrTaRb...
> > OK, afeter several tries, and several reboots, and hte same errors
coming up
> > again and again, I am tossing in the towe, and crying for help.
> >
> > When I set up the network deployment image files, everythign appears to
go
> > smoothly.
> >
> > When I go to install on a client, I get an error that reads:
> > Error 1324. The Folder Path 'Program Files' contains an invalid
character.
> >
> > So, I went into the appsetup.inf, and changed the path to something that
had
> > no blank spaces, and no parts of the path were longer than 8 characters
> > (what the heck, might as well make the path backwards compatible to DOS
1)
> >
> > Then I try again, and get the same error, only this time, the problem
path
> > is 'CD Manager.'
> > That pth is not spelled out in the appsetup.inf file. I did specify to
> > apply the CAD Manager Controls to Today, so I am expecting that to be
the
> > problem. I'm about to create a whole new deployment location, with a
fresh
> > new image, short path, no CAD Manager, etc. But even so, this is
> > ridiculous. Does anyone have a clue what has gone wrong?
> >
> >
>
>

[Anonymous]

Also, I've noticed that when you go to create new image files, the server
remembers a lot of what you did last time. So, if there is some hidden
invalid character in those paths, as a result of some sector of my disk
getting fried, it may be getting that bad character out of local memory.

Do you know where it stores that info? Should I find that, and wipe it out,
and force it to make a clean start?

"Charles Prettyman" wrote in message
news:1BCC46BBAEE7EBC0109975FE408479F2@in.WebX.maYIadrTaRb...
> I just did create a whole new deploy image, on a different drive. I used
a
> very simple path for hte program installation (D:\ADT33\)
> and I did not apply the CAD manager controls to today.
>
> Error 1324. The Folder Path 'CAD Manager' contains an invalid character.
>
> reared its ugly head again!
>
> I don't think it's even actually the Appsetup.inf. I was able to compare
it
> to one that worked for someone (Thanks for that Jason), and there are no
> differences other than obvious stuff (who it's licensed to, server, ID,
etc)
>
> My next step is to set up all over again on a different machine. Even if
I
> eventually have to migrate people back to the server I've been trying
(it's
> a load balancing issue, but there may be other solutions to that)
>
>
>
> "jason martin" wrote in message
> news:9EA3148944E0B507446531C14A72DE8A@in.WebX.maYIadrTaRb...
> > Charles -
> >
> > I'd highly recommend a new deploy image. I've had some problems with
> appsetup.inf files
> > in the past and I've generally found that it's been easier just to
create
> a new deploy
> > than it is to try to fix and existing deploy that has never worked. If
> the appsetup.inf
> > got hosed somehow, it's fairly likely to assume that other stuff was
also
> "broken" during
> > the deployment image creation. Was it heat near the server, solar
flares,
> ozone depletion
> > who knows. Try creating the deploy again and let us know if that
doesn't
> work (just
> > delete the old one, it's not doing any good anyway).
> >
> > hth
> >
> > jason martin
> > frankfurt-short-bruza
> >
> > "Charles Prettyman" wrote in message
> > news:420B617AF0EAF0B44FCF7C968B0CC2C9@in.WebX.maYIadrTaRb...
> > > OK, afeter several tries, and several reboots, and hte same errors
> coming up
> > > again and again, I am tossing in the towe, and crying for help.
> > >
> > > When I set up the network deployment image files, everythign appears
to
> go
> > > smoothly.
> > >
> > > When I go to install on a client, I get an error that reads:
> > > Error 1324. The Folder Path 'Program Files' contains an invalid
> character.
> > >
> > > So, I went into the appsetup.inf, and changed the path to something
that
> had
> > > no blank spaces, and no parts of the path were longer than 8
characters
> > > (what the heck, might as well make the path backwards compatible to
DOS
> 1)
> > >
> > > Then I try again, and get the same error, only this time, the problem
> path
> > > is 'CD Manager.'
> > > That pth is not spelled out in the appsetup.inf file. I did specify
to
> > > apply the CAD Manager Controls to Today, so I am expecting that to be
> the
> > > problem. I'm about to create a whole new deployment location, with a
> fresh
> > > new image, short path, no CAD Manager, etc. But even so, this is
> > > ridiculous. Does anyone have a clue what has gone wrong?
> > >
> > >
> >
> >
>
>

[Anonymous]

OK, a whole new image file on a different machine (although it was pointed
to the same ADLM) brought up the same freaking errors.

So, two things occur to me:
1. The CD has a scratch, or fingerprint on it that repeatedly casues the
same error (unlikely, but a lot of things that actuallyhappen defy all
reason)
or
2. The first failed install, for whatever reason, left some garbage behind
on the workstation that is getting in the way of all these new installation
attempts. (I'd say that this is more likely, but what do I know)



"jason martin" wrote in message
news:9EA3148944E0B507446531C14A72DE8A@in.WebX.maYIadrTaRb...
> Charles -
>
> I'd highly recommend a new deploy image. I've had some problems with
appsetup.inf files
> in the past and I've generally found that it's been easier just to create
a new deploy
> than it is to try to fix and existing deploy that has never worked. If
the appsetup.inf
> got hosed somehow, it's fairly likely to assume that other stuff was also
"broken" during
> the deployment image creation. Was it heat near the server, solar flares,
ozone depletion
> who knows. Try creating the deploy again and let us know if that doesn't
work (just
> delete the old one, it's not doing any good anyway).
>
> hth
>
> jason martin
> frankfurt-short-bruza
>
> "Charles Prettyman" wrote in message
> news:420B617AF0EAF0B44FCF7C968B0CC2C9@in.WebX.maYIadrTaRb...
> > OK, afeter several tries, and several reboots, and hte same errors
coming up
> > again and again, I am tossing in the towe, and crying for help.
> >
> > When I set up the network deployment image files, everythign appears to
go
> > smoothly.
> >
> > When I go to install on a client, I get an error that reads:
> > Error 1324. The Folder Path 'Program Files' contains an invalid
character.
> >
> > So, I went into the appsetup.inf, and changed the path to something that
had
> > no blank spaces, and no parts of the path were longer than 8 characters
> > (what the heck, might as well make the path backwards compatible to DOS
1)
> >
> > Then I try again, and get the same error, only this time, the problem
path
> > is 'CD Manager.'
> > That pth is not spelled out in the appsetup.inf file. I did specify to
> > apply the CAD Manager Controls to Today, so I am expecting that to be
the
> > problem. I'm about to create a whole new deployment location, with a
fresh
> > new image, short path, no CAD Manager, etc. But even so, this is
> > ridiculous. Does anyone have a clue what has gone wrong?
> >
> >
>
>

[Anonymous]

It continues
I had a chat with my reseller, and at his suggestion, I wiped out the
registry key for Autodesk, and rebooted, and that still didn't solve it.

For the time being I have ADT3.3 installed locally, so I can get some work
done. But I need to get this resolved.




"Charles Prettyman" wrote in message
news:C946F3A046A5E3A5B7D2BE7B0C46DE5E@in.WebX.maYIadrTaRb...
> OK, a whole new image file on a different machine (although it was pointed
> to the same ADLM) brought up the same freaking errors.
>
> So, two things occur to me:
> 1. The CD has a scratch, or fingerprint on it that repeatedly casues the
> same error (unlikely, but a lot of things that actuallyhappen defy all
> reason)
> or
> 2. The first failed install, for whatever reason, left some garbage behind
> on the workstation that is getting in the way of all these new
installation
> attempts. (I'd say that this is more likely, but what do I know)
>
>
>
> "jason martin" wrote in message
> news:9EA3148944E0B507446531C14A72DE8A@in.WebX.maYIadrTaRb...
> > Charles -
> >
> > I'd highly recommend a new deploy image. I've had some problems with
> appsetup.inf files
> > in the past and I've generally found that it's been easier just to
create
> a new deploy
> > than it is to try to fix and existing deploy that has never worked. If
> the appsetup.inf
> > got hosed somehow, it's fairly likely to assume that other stuff was
also
> "broken" during
> > the deployment image creation. Was it heat near the server, solar
flares,
> ozone depletion
> > who knows. Try creating the deploy again and let us know if that
doesn't
> work (just
> > delete the old one, it's not doing any good anyway).
> >
> > hth
> >
> > jason martin
> > frankfurt-short-bruza
> >
> > "Charles Prettyman" wrote in message
> > news:420B617AF0EAF0B44FCF7C968B0CC2C9@in.WebX.maYIadrTaRb...
> > > OK, afeter several tries, and several reboots, and hte same errors
> coming up
> > > again and again, I am tossing in the towe, and crying for help.
> > >
> > > When I set up the network deployment image files, everythign appears
to
> go
> > > smoothly.
> > >
> > > When I go to install on a client, I get an error that reads:
> > > Error 1324. The Folder Path 'Program Files' contains an invalid
> character.
> > >
> > > So, I went into the appsetup.inf, and changed the path to something
that
> had
> > > no blank spaces, and no parts of the path were longer than 8
characters
> > > (what the heck, might as well make the path backwards compatible to
DOS
> 1)
> > >
> > > Then I try again, and get the same error, only this time, the problem
> path
> > > is 'CD Manager.'
> > > That pth is not spelled out in the appsetup.inf file. I did specify
to
> > > apply the CAD Manager Controls to Today, so I am expecting that to be
> the
> > > problem. I'm about to create a whole new deployment location, with a
> fresh
> > > new image, short path, no CAD Manager, etc. But even so, this is
> > > ridiculous. Does anyone have a clue what has gone wrong?
> > >
> > >
> >
> >
>
>

[Anonymous]

Charles - The 1324 error generally indicates that the path specified for 'Cad Manager'
contains a pointer to a drive that doesn't exist. The only thing that I can think of that
would cause it to error on 'Cad Manager' is the cad manager control of the autocad today
window. It could also be possible (although not likely) that there isn't enough temp space
on the C drive of the machine that you are trying to install to. This doesn't make any
sense at all but I've seen all kinds of problems that shouldn't occur when there isn't
enough space on C.

hth

jason

"Charles Prettyman" wrote in message
news:1BCC46BBAEE7EBC0109975FE408479F2@in.WebX.maYIadrTaRb...
> I just did create a whole new deploy image, on a different drive. I used a
> very simple path for hte program installation (D:\ADT33\)
> and I did not apply the CAD manager controls to today.
>
> Error 1324. The Folder Path 'CAD Manager' contains an invalid character.
>
> reared its ugly head again!
>
> I don't think it's even actually the Appsetup.inf. I was able to compare it
> to one that worked for someone (Thanks for that Jason), and there are no
> differences other than obvious stuff (who it's licensed to, server, ID, etc)
>
> My next step is to set up all over again on a different machine. Even if I
> eventually have to migrate people back to the server I've been trying (it's
> a load balancing issue, but there may be other solutions to that)
>
>
>
> "jason martin" wrote in message
> news:9EA3148944E0B507446531C14A72DE8A@in.WebX.maYIadrTaRb...
> > Charles -
> >
> > I'd highly recommend a new deploy image. I've had some problems with
> appsetup.inf files
> > in the past and I've generally found that it's been easier just to create
> a new deploy
> > than it is to try to fix and existing deploy that has never worked. If
> the appsetup.inf
> > got hosed somehow, it's fairly likely to assume that other stuff was also
> "broken" during
> > the deployment image creation. Was it heat near the server, solar flares,
> ozone depletion
> > who knows. Try creating the deploy again and let us know if that doesn't
> work (just
> > delete the old one, it's not doing any good anyway).
> >
> > hth
> >
> > jason martin
> > frankfurt-short-bruza
> >
> > "Charles Prettyman" wrote in message
> > news:420B617AF0EAF0B44FCF7C968B0CC2C9@in.WebX.maYIadrTaRb...
> > > OK, afeter several tries, and several reboots, and hte same errors
> coming up
> > > again and again, I am tossing in the towe, and crying for help.
> > >
> > > When I set up the network deployment image files, everythign appears to
> go
> > > smoothly.
> > >
> > > When I go to install on a client, I get an error that reads:
> > > Error 1324. The Folder Path 'Program Files' contains an invalid
> character.
> > >
> > > So, I went into the appsetup.inf, and changed the path to something that
> had
> > > no blank spaces, and no parts of the path were longer than 8 characters
> > > (what the heck, might as well make the path backwards compatible to DOS
> 1)
> > >
> > > Then I try again, and get the same error, only this time, the problem
> path
> > > is 'CD Manager.'
> > > That pth is not spelled out in the appsetup.inf file. I did specify to
> > > apply the CAD Manager Controls to Today, so I am expecting that to be
> the
> > > problem. I'm about to create a whole new deployment location, with a
> fresh
> > > new image, short path, no CAD Manager, etc. But even so, this is
> > > ridiculous. Does anyone have a clue what has gone wrong?
> > >
> > >
> >
> >
>
>

[Anonymous]

Actually I don't think that the server remembers. I think that it is stored in the
registry of the workstation from which the image is being created.

jason

"Charles Prettyman" wrote in message
news:7E2628FABD922E94A40D887778C0E14F@in.WebX.maYIadrTaRb...
> Also, I've noticed that when you go to create new image files, the server
> remembers a lot of what you did last time. So, if there is some hidden
> invalid character in those paths, as a result of some sector of my disk
> getting fried, it may be getting that bad character out of local memory.
>
> Do you know where it stores that info? Should I find that, and wipe it out,
> and force it to make a clean start?
>

[Anonymous]

That makes some sense. We have an ongoing problem with several of hte
workstations here that they came from the factory with undersizd C drives,
and a nice big D drive. Lacking a site license for partition magic, I have
been loathe to reformat the drives and start over, but enough hot fixes and
service packs, etc have come along that the C drives have slowly filled up,
and it's very hard to get them stripped all the way clean. I guess it's
time.


"jason martin" wrote in message
news:4AADA09E6F10D41C903DF98536DB95B7@in.WebX.maYIadrTaRb...
> Charles - The 1324 error generally indicates that the path specified for
'Cad Manager'
> contains a pointer to a drive that doesn't exist. The only thing that I
can think of that
> would cause it to error on 'Cad Manager' is the cad manager control of the
autocad today
> window. It could also be possible (although not likely) that there isn't
enough temp space
> on the C drive of the machine that you are trying to install to. This
doesn't make any
> sense at all but I've seen all kinds of problems that shouldn't occur when
there isn't
> enough space on C.
>
> hth
>
> jason
>
> "Charles Prettyman" wrote in message
> news:1BCC46BBAEE7EBC0109975FE408479F2@in.WebX.maYIadrTaRb...
> > I just did create a whole new deploy image, on a different drive. I
used a
> > very simple path for hte program installation (D:\ADT33\)
> > and I did not apply the CAD manager controls to today.
> >
> > Error 1324. The Folder Path 'CAD Manager' contains an invalid
character.
> >
> > reared its ugly head again!
> >
> > I don't think it's even actually the Appsetup.inf. I was able to
compare it
> > to one that worked for someone (Thanks for that Jason), and there are no
> > differences other than obvious stuff (who it's licensed to, server, ID,
etc)
> >
> > My next step is to set up all over again on a different machine. Even
if I
> > eventually have to migrate people back to the server I've been trying (i
t's
> > a load balancing issue, but there may be other solutions to that)
> >
> >
> >
> > "jason martin" wrote in message
> > news:9EA3148944E0B507446531C14A72DE8A@in.WebX.maYIadrTaRb...
> > > Charles -
> > >
> > > I'd highly recommend a new deploy image. I've had some problems with
> > appsetup.inf files
> > > in the past and I've generally found that it's been easier just to
create
> > a new deploy
> > > than it is to try to fix and existing deploy that has never worked.
If
> > the appsetup.inf
> > > got hosed somehow, it's fairly likely to assume that other stuff was
also
> > "broken" during
> > > the deployment image creation. Was it heat near the server, solar
flares,
> > ozone depletion
> > > who knows. Try creating the deploy again and let us know if that
doesn't
> > work (just
> > > delete the old one, it's not doing any good anyway).
> > >
> > > hth
> > >
> > > jason martin
> > > frankfurt-short-bruza
> > >
> > > "Charles Prettyman" wrote in message
> > > news:420B617AF0EAF0B44FCF7C968B0CC2C9@in.WebX.maYIadrTaRb...
> > > > OK, afeter several tries, and several reboots, and hte same errors
> > coming up
> > > > again and again, I am tossing in the towe, and crying for help.
> > > >
> > > > When I set up the network deployment image files, everythign appears
to
> > go
> > > > smoothly.
> > > >
> > > > When I go to install on a client, I get an error that reads:
> > > > Error 1324. The Folder Path 'Program Files' contains an invalid
> > character.
> > > >
> > > > So, I went into the appsetup.inf, and changed the path to something
that
> > had
> > > > no blank spaces, and no parts of the path were longer than 8
characters
> > > > (what the heck, might as well make the path backwards compatible to
DOS
> > 1)
> > > >
> > > > Then I try again, and get the same error, only this time, the
problem
> > path
> > > > is 'CD Manager.'
> > > > That pth is not spelled out in the appsetup.inf file. I did specify
to
> > > > apply the CAD Manager Controls to Today, so I am expecting that to
be
> > the
> > > > problem. I'm about to create a whole new deployment location, with
a
> > fresh
> > > > new image, short path, no CAD Manager, etc. But even so, this is
> > > > ridiculous. Does anyone have a clue what has gone wrong?
> > > >
> > > >
> > >
> > >
> >
> >
>
>

[Anonymous]

Thank you all for the various thoughts on this. For those who face
somethign similar, the actiuual problem turned out to be this:

Most machines inthe office have very little room to spare on C, but have
room of D. So I set up the istallation files to default to D for
installation. A few machines, however, including my own, have other issues.
In my case, D is a zip drive, and all the applications got on E (don't ask
me why, Dell set it up like that). So, althoughthe error messages were
refering to paths like "CAD Standards" or "Program Files" the actual error
was in the drive letter.

One of the frustrating parts of this is htat I had somewhat anticipated the
problem, and set up the installation NOT to be silent, so that I caould have
one set of image files to install to C, D or E as appropriate. But the
error cropped up before I was able to redirect this installation to E.

Now, on to the next challenge.

[Anonymous]

BTW, it is my reseller who actually deserves any credit given for solving
this - Thank you Jan.



"Charles Prettyman" wrote in message
news:EB00435F41FCD94908D9280B17592DD1@in.WebX.maYIadrTaRb...
> Thank you all for the various thoughts on this. For those who face
> somethign similar, the actiuual problem turned out to be this:
>
> Most machines inthe office have very little room to spare on C, but have
> room of D. So I set up the istallation files to default to D for
> installation. A few machines, however, including my own, have other
issues.
> In my case, D is a zip drive, and all the applications got on E (don't ask
> me why, Dell set it up like that). So, althoughthe error messages were
> refering to paths like "CAD Standards" or "Program Files" the actual error
> was in the drive letter.
>
> One of the frustrating parts of this is htat I had somewhat anticipated
the
> problem, and set up the installation NOT to be silent, so that I caould
have
> one set of image files to install to C, D or E as appropriate. But the
> error cropped up before I was able to redirect this installation to E.
>
> Now, on to the next challenge.
>
>