Installation & Licensing

[#1]

Need Expert Advice

Our office is caught with a serious Autocad problem. There are many
factors involved so it is hard to pin down just what the problem is.
Perhaps someone has experienced this before.

This is not happening to everyone. There are a few people who are having
this problem repeatedly, but not all the time. The people who are having
problems tend to be on the same teams. We have 2 or 3 projects which are
continually having the problem while the others are usually fine.

What's happening is that a file will be opened but does not close when
the user exits out. So, he can then not save it. It tells him that
someone else has the file open. We have the program "Who Has It" and can
see many files open which really are not. Most of the time it is the
user himself who the computer thinks has the file open. If the user logs
off the computer the files are closed.

Sometimes the files save without a problem. But when it does save, it is
making multiple .bak files. It is naming them savxxxx.bak where xxxx is
a random number. When the file cannot be saved it creates an ac$ temp
file.

Some of our users are running Win95, some Win98. All of them are running
Autocad 14.01 Build version P.033c. The c patch is supposed to deal with
this file not closing problem but I loaded that this weekend and the
problem is still happening today.

We are also running Netware 4.11 Service Pack 7. SP7 is also supposed to
deal with a problem of files not being closed. There is an additional
patch called Rev... something which I have also loaded on the server,
but to no avail. Everyone is running Client 32 ver 3.1 SP2.

This problem started when I first loaded SP1 on a few computers. I was
able to remove SP1 at that time and everything went back to normal. It
was after that that I loaded SP7 on the server and hoped that would
solve the problem. I then loaded the client service packs hoping that
would solve the problem. But, now I have tried removing Client 3.1 from
one computer and the problem continued to happen. At this point everyone
is forced to have to log off the network every time they want to get out
of a file.

Another factor that is probably not relevant is that two of the people
who have this problem most and who actually seemed to have started it
have just previously gotten Dell Pentium III 450 mhz machines. I am
clutching at straws.

Would anyone vote for unloading Client 32 3.1 from all computers and
Service Pack 7 from the server? Or is it an Autocad problem?

[#2]

Connie,

The patch you applied helps with read only problems associated with some
Unix server connectivity products, as documented with the patch
distribution. The read only problems with Netware servers is not addressed
in this patch. If you still have this problem after installing Novell's
latest client software, I suggest that you report the problem to Novell. If
you are using the Netware AdLM to control licenses, you are stuck with using
Novell's Client software. If you are running standalone licenses for
AutoCAD or are using a Windows system to run the TCP/IP version of AdLM, you
may want to try the Microsoft Client for Netware which is shipped with your
Operating System.

Jerry Milana,
Autodesk Product Support

Connie Durst wrote:

> Need Expert Advice
>
> Our office is caught with a serious Autocad problem. There are many
> factors involved so it is hard to pin down just what the problem is.
> Perhaps someone has experienced this before.
>
> This is not happening to everyone. There are a few people who are having
> this problem repeatedly, but not all the time. The people who are having
> problems tend to be on the same teams. We have 2 or 3 projects which are
> continually having the problem while the others are usually fine.
>
> What's happening is that a file will be opened but does not close when
> the user exits out. So, he can then not save it. It tells him that
> someone else has the file open. We have the program "Who Has It" and can
> see many files open which really are not. Most of the time it is the
> user himself who the computer thinks has the file open. If the user logs
> off the computer the files are closed.
>
> Sometimes the files save without a problem. But when it does save, it is
> making multiple .bak files. It is naming them savxxxx.bak where xxxx is
> a random number. When the file cannot be saved it creates an ac$ temp
> file.
>
> Some of our users are running Win95, some Win98. All of them are running
> Autocad 14.01 Build version P.033c. The c patch is supposed to deal with
> this file not closing problem but I loaded that this weekend and the
> problem is still happening today.
>
> We are also running Netware 4.11 Service Pack 7. SP7 is also supposed to
> deal with a problem of files not being closed. There is an additional
> patch called Rev... something which I have also loaded on the server,
> but to no avail. Everyone is running Client 32 ver 3.1 SP2.
>
> This problem started when I first loaded SP1 on a few computers. I was
> able to remove SP1 at that time and everything went back to normal. It
> was after that that I loaded SP7 on the server and hoped that would
> solve the problem. I then loaded the client service packs hoping that
> would solve the problem. But, now I have tried removing Client 3.1 from
> one computer and the problem continued to happen. At this point everyone
> is forced to have to log off the network every time they want to get out
> of a file.
>
> Another factor that is probably not relevant is that two of the people
> who have this problem most and who actually seemed to have started it
> have just previously gotten Dell Pentium III 450 mhz machines. I am
> clutching at straws.
>
> Would anyone vote for unloading Client 32 3.1 from all computers and
> Service Pack 7 from the server? Or is it an Autocad problem?

[#3]

Jerry,

Connie's problem seems to be similar to the one I reported
that MMWD was having. I talked to them today, and of all
things, they said that if they set their isavepercent to
100, (!!!????), the problem goes away. 'Makes no sense to
me, but it's working for them, and they're happy with it...

John