Installation & Licensing

Reply
*milana, jerry
Message 21 of 30 (120 Views)

Re:

07-02-2000 07:49 AM in reply to: *Fisk, Justin
That's a good clue, guys. I'll work on that lead on Wednesday when we come
back from holiday.

jerry

"Jeff Portman" wrote in message news:ef2569d.17@WebX.SaUCah8kaAW...
> Justin:
>
> I just corresponded with one other person today who relayed the same info:
> Upgrading from NT4.0 to Win2k allows ADT2 to work fine - it's the clean
> Win2k installs that are killing us.
>
> Looks like we really need a Windows "downgrade" package, not a ADT
> "upgrade". (Well, ok, an ADT upgrade would be great, but not just to solve
> this problem.)
>
> Anybody out there know if this would be as simple as copying a few files
off
> the NT 4.0 cd into the appropriate directories of Win2k?
>
> Jeff
>
> "Justin Fisk" wrote in message
> news:395C988C.46C8A3D8@csd-eng.com...
> > Here's something you may want to pass on to the ADT team. I have
upgraded
> some
> > workstations from Windows NT to Windows 2000 and the software works!
When
> I do
> > a clean install on Windows 2000 it doesn't work. Maybe this points to a
> dll or
> > a registry file that is retained in the upgrade process that is just
> overwritten
> > in the clean install.
> > Justin Fisk
> >
> > jerry milana wrote:
> >
> > > We are looking at this situation.
> > > You are correct that ADT was developed prior to the release of Windows
> 2000
> > > and is thus not 'supported' on the OS. This means we will do what we
> can
> > > but if something major is required to make the product work on the OS,
> you
> > > may have to wait for an upgrade. As application developers, we do not
> have
> > > control over compatibility with future operating systems, your OS
> developer
> > > has control over that.
> > > I will update this news group when I find out more information on this
> > > specific problem.
> > >
> > > Jerry Milana,
> > > Autodesk Product Support
>
*Burrill, John
Message 22 of 30 (120 Views)

Re:

07-06-2000 07:37 AM in reply to: *Fisk, Justin
I'm deploying running ADT from a Win2k ADLM install to an NT4.0 client with
no problems. On your win2k machines (the virgin ones), did you correct the
system registry like it says to in this doc?
http://www3.autodesk.com/adsk/support/techdoc/0,,253509--125452-20022_21841,
00.html

"shorn" wrote in message
news:ef2569d.18@WebX.SaUCah8kaAW...
> Everyone and AutoDesk: We are seeing a similar problem with LDD2 on
Win2k,
> trying to talk to a TCP/IP AdLM. We get the same "Unable to send license\
> daemon message" error reported at the top of this thread.
*Portman, Jeff
Message 23 of 30 (120 Views)

Re:

07-07-2000 06:45 AM in reply to: *Fisk, Justin
John:

I did a local install, so I didn't have the trailing comma problem mentioned
in the techdoc you referenced.

Jeff

"John Burrill" wrote in message
news:ef2569d.20@WebX.SaUCah8kaAW...
> I'm deploying running ADT from a Win2k ADLM install to an NT4.0 client
with
> no problems. On your win2k machines (the virgin ones), did you correct
the
> system registry like it says to in this doc?
>
http://www3.autodesk.com/adsk/support/techdoc/0,,253509--125452-20022_21841,
> 00.html
>
> "shorn" wrote in message
> news:ef2569d.18@WebX.SaUCah8kaAW...
> > Everyone and AutoDesk: We are seeing a similar problem with LDD2 on
> Win2k,
> > trying to talk to a TCP/IP AdLM. We get the same "Unable to send
license\
> > daemon message" error reported at the top of this thread.
>
*Fisk, Justin
Message 24 of 30 (120 Views)

Re:

07-07-2000 01:53 PM in reply to: *Fisk, Justin
The ADLM works fine, it is the Win 2k CLIENT machines that will not run LDT or
ADT network copies.
Thanks for at least trying to help.

Hey Autodesk, have you gotton any further on our lead about the NT upgrade.

Justin

John Burrill wrote:

> I'm deploying running ADT from a Win2k ADLM install to an NT4.0 client with
> no problems. On your win2k machines (the virgin ones), did you correct the
> system registry like it says to in this doc?
> http://www3.autodesk.com/adsk/support/techdoc/0,,253509--125452-20022_21841,
> 00.html
>
> "shorn" wrote in message
> news:ef2569d.18@WebX.SaUCah8kaAW...
> > Everyone and AutoDesk: We are seeing a similar problem with LDD2 on
> Win2k,
> > trying to talk to a TCP/IP AdLM. We get the same "Unable to send license\
> > daemon message" error reported at the top of this thread.
*milana, jerry
Message 25 of 30 (120 Views)

Re:

07-07-2000 03:17 PM in reply to: *Fisk, Justin
Justin,

I just got off the phone with our ADT QA people, they retested fresh Win
2000 loads at my request and the clients all pulled licenses just fine.
What they did suggest is that you try setting ACADSERVER using the @ symbol
to prefix the value. Also make sure you get the case correct. The ADT/LDT
folks have found that without setting ACADSERVER using an @ prefix will
cause problems getting a license if running on Win 2000.

jerry

"Justin Fisk" wrote in message
news:39664351.3DA52B9B@csd-eng.com...
> The ADLM works fine, it is the Win 2k CLIENT machines that will not run
LDT or
> ADT network copies.
> Thanks for at least trying to help.
>
> Hey Autodesk, have you gotton any further on our lead about the NT
upgrade.
>
> Justin
>
> John Burrill wrote:
>
> > I'm deploying running ADT from a Win2k ADLM install to an NT4.0 client
with
> > no problems. On your win2k machines (the virgin ones), did you correct
the
> > system registry like it says to in this doc?
> >
http://www3.autodesk.com/adsk/support/techdoc/0,,253509--125452-20022_21841,
> > 00.html
> >
> > "shorn" wrote in message
> > news:ef2569d.18@WebX.SaUCah8kaAW...
> > > Everyone and AutoDesk: We are seeing a similar problem with LDD2 on
> > Win2k,
> > > trying to talk to a TCP/IP AdLM. We get the same "Unable to send
license\
> > > daemon message" error reported at the top of this thread.
>
*Fisk, Justin
Message 26 of 30 (120 Views)

Re: More ADT2 WIN 2k network problems

07-10-2000 08:50 AM in reply to: *Fisk, Justin
It WORKED, this must be a solution, please pass on the @ information to
anyone having problems.
Thanks,
Justin
*Portman, Jeff
Message 27 of 30 (120 Views)

We have a Winner

07-10-2000 01:59 PM in reply to: *Fisk, Justin
Worked for me, too. Also speeded up the license grabbing in "normal" AutoCad
to about zero lag time. Two users may not be a huge test pool, but I'd say
this one's about licked.

Thanks Jerry

Jeff

"Justin Fisk" wrote in message
news:3969F0DA.1E0D0C0B@csd-eng.com...
> It WORKED, this must be a solution, please pass on the @ information to
> anyone having problems.
> Thanks,
> Justin
>
*[Autodesk], Mike Szanto
Message 28 of 30 (120 Views)

We have a Winner

07-10-2000 04:06 PM in reply to: *Fisk, Justin
Jeff,

This particular problem should only occur with Land Desktop R2, Land Desktop 2i,
Arch Desktop R2 & Arch Desktop 2i.

With any AutoCAD based product, whenever you explicitly point to a license
server using the @ symbol, it will always be much quicker because it doesn't
have to 'broadcast' to find one. You'll also notice that ADLM Query is very
quick as well.

There is one down side to this work-around and that is you cannot access
licenses from multiple license servers simultaneously. You would have to reset
the ACADSERVER variable to point to another license server if your license
server runs out of licenses and there are other licenses available on another
license server.
(something to be aware of )

Mike

--
Mike Szanto
AEC Product Support, Americas
WW Support & Services, Autodesk
Land Development Desktop Solutions:
http://www.autodesk.com/support/landdesk/techsol.htm

Jeff Portman wrote in message news:ef2569d.25@WebX.SaUCah8kaAW...
Worked for me, too. Also speeded up the license grabbing in "normal" AutoCad
to about zero lag time. Two users may not be a huge test pool, but I'd say
this one's about licked.

Thanks Jerry

Jeff

"Justin Fisk" wrote in message
news:3969F0DA.1E0D0C0B@csd-eng.com...
> It WORKED, this must be a solution, please pass on the @ information to
> anyone having problems.
> Thanks,
> Justin
>
*Portman, Jeff
Message 29 of 30 (120 Views)

We have a Winner

07-11-2000 09:58 AM in reply to: *Fisk, Justin
Thanks Mike

Currently we only have one license server, so no problems. And yes, it's
very quick to snag a license. Thanks for the clarification.

Jeff

"Mike Szanto [Autodesk]" wrote in message
news:ef2569d.26@WebX.SaUCah8kaAW...
> Jeff,
>
> This particular problem should only occur with Land Desktop R2, Land
Desktop 2i,
> Arch Desktop R2 & Arch Desktop 2i.
>
> With any AutoCAD based product, whenever you explicitly point to a license
> server using the @ symbol, it will always be much quicker because it
doesn't
> have to 'broadcast' to find one. You'll also notice that ADLM Query is
very
> quick as well.
>
> There is one down side to this work-around and that is you cannot access
> licenses from multiple license servers simultaneously. You would have to
reset
> the ACADSERVER variable to point to another license server if your license
> server runs out of licenses and there are other licenses available on
another
> license server.
> (something to be aware of )
>
> Mike
>
> --
> Mike Szanto
> AEC Product Support, Americas
> WW Support & Services, Autodesk
> Land Development Desktop Solutions:
> http://www.autodesk.com/support/landdesk/techsol.htm
>
> Jeff Portman wrote in message news:ef2569d.25@WebX.SaUCah8kaAW...
> Worked for me, too. Also speeded up the license grabbing in "normal"
AutoCad
> to about zero lag time. Two users may not be a huge test pool, but I'd say
> this one's about licked.
>
> Thanks Jerry
>
> Jeff
>
> "Justin Fisk" wrote in message
> news:3969F0DA.1E0D0C0B@csd-eng.com...
> > It WORKED, this must be a solution, please pass on the @ information to
> > anyone having problems.
> > Thanks,
> > Justin
> >
>
*[Autodesk], Mike Szanto
Message 30 of 30 (120 Views)

We have a Winner

07-11-2000 03:10 PM in reply to: *Fisk, Justin
Actually, in circumspect, I misinformed you...
Setting the ACADSERVER variable to @hostname should not be faster than letting
the ADLM broadcast to find a server. If setting the ACADSERVER improves the
performance then it may reflect a problem with your network. I would defer to
Jerry Milana if you have questions pertaining to that issue.
It definitely will improve performance when running ADLM Query if you have
multiple license servers because it will force ADLM Query to query only one
license server instead of 2 or 3 or more.
In general, we don't recommend using @hostname except in extreme circumstances
such as this one.

Mike

You are not logged in.

Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register

Announcements
Are you familiar with the Autodesk Expert Elites? The Expert Elite program is made up of customers that help other customers by sharing knowledge and exemplifying an engaging style of collaboration. To learn more, please visit our Expert Elite website.

Need installation help?

Start with some of our most frequented solutions to get help installing your software.

Ask the Community


Up & Ready Blog

Boldly Install, Configure and Deploy Autodesk Software.

AutodeskHelp Blog

Your one-stop shop for the latest solutions, breaking news, and behind the scenes access to the world of Autodesk support.

Connect with Us

Twitter

Pinterest

Blog

Youtube