Network Connection Lost, InDesign Shuts Down

[jayejoseph@adobeforums.com]

I did a search and haven't found any information on this issue. There is nothing specific that I am doing that causes this to happen, it just does. I'm working on a document (doesn't matter on length) and I get an error message that "Network connection for file (name) has been lost or it has been modified outside of InDesign". Then I click OK and I get another error that InDesign has encountered a serious error and must shut down. Then I open it back up and Auto Recovery begins and almost all is well. It's just that this is happening so much sometimes that I can't go 5 minutes working in a file. What gives? I also get this message if I am working on my computer and not on the network. I am using a Windows XP 1.4 GHz Gateway with 512MB RAM. TIA

[Gabriel_Ayala@adobeforums.com]

Talk to your IT department about it.

[jayejoseph@adobeforums.com]

Thanks. That's the first thing I did and they think it's a software problem. I'm an in-house designer so I get stuck having to take care of my own issues when it comes to software.

[Gabriel_Ayala@adobeforums.com]

I also get this message if I am working on my computer and not on the
network.




Are you working from a Zip disk or other removable media? Just because it says network it doesn't mean you have to take that message literal. What it means is that InDesign has lost the ability to see, read or write to the file you are working on.

For example, you save it on a zip and the connection gets lost in your computer to the zip drive for whatever reason or the disk is ejected. The message should appear if this occurs.

[jayejoseph@adobeforums.com]

Nope, no removable media or anything. Either on the network drive I am assigned to or on my desktop. I'm just at a loss here.

[Gabriel_Ayala@adobeforums.com]

I get that message too but I assume it has to do with loss of connection to the network. I don't think there's anything wrong with my ID.

____

One of my favorite quotes is "the stupid computer".

I hear people say that one all the time when in fact it's the operator that isn't telling the computer the correct command.

I'm not saying you or your IT department is stupid. I just went off into another subject because my IT guy was just here talking to me about how people will call him and say that the computer is broken but it's not broken, THEY BROKE IT. They do not follow his instructions to keep up with the latest Windows updates, AntiVirus, Adaware ect so they blame it on the computer.

Funny how that works.

Sorry, if you're not interested, I'm just babbling.

[Gabriel_Ayala@adobeforums.com]

Ok, when you get that message, try accessing your network drive immediately and see if you have access.

[jayejoseph@adobeforums.com]

OK. It should happen again here in a second.

And I know just what you mean. I used to have to do a bit of IT stuff at an old job and people would say that all the time.

One time, a Senior VP called me b/c his computer was frozen and he couldn't get it to restart. I went to see him, and did a reboot on his keyboard (Mac), and asked him, out of curiosity how he was restarting. He pointed to the power switch on his monitor. This was only about 2 years ago. That story makes me laugh all the time. And you're right. It's always a "User Error". It's very rarely the computer or the network...

[Gabriel_Ayala@adobeforums.com]

He pointed to the power switch on his monitor.




Waaaow!8o ROTFLMAO :D

And they pay this guy how much?

[jayejoseph@adobeforums.com]

It was so great. It was a state job, so even at his level, I doubt he made much.

The problem happened again. I was able to access the network with no problem. I checked the task manager just to see what the usage on this program was and it is only 2%. I just cannot figure this out at all.

[Gabriel_Ayala@adobeforums.com]

You jinxed me! Now I'm getting the error.

InDesign.exe has encountered a problem and needs to close. We are sorry
for the inconvenience.




Not as sorry as I am!

If you were in the middle of something, the information you were working
on might be lost. For more information about this error click here.





I click the close button and poof there it goes crashing down.

The good news is; when I open Indy it's still where I left off. This shouldn't be happening at all. According to my Sys Admin there is no sign of me losing connectivity on the network but he couldn't tell me for sure. :/

I even did a search on google for something that has to do with this and couldn't find a damn thing! This isn't very much of a problem for me but if it's going to start happening to me as frequently as it does for you then I'm going to start lighting trash cans on fire, kicking over newspaper stands, throwing forty ounce bottles and what not.

[jayejoseph@adobeforums.com]

I am so sorry! I re-installed this morning and it still hasn't fixed the issue. I am going to de-frag at lunch, just to see if it helps. If it is still doing it, I am going to call Adobe Tech Support this afternoon. I'll keep you posted. This is killing me. I am not throwing the 40s yet, just drinking them.

[Gabriel_Ayala@adobeforums.com]

I don't think a defrag is going to help this but it can't hurt anything so what the heck.

This is very strange behavior, is anyone else experiencing this?

One thing I should add is I leave ID on all night when I leave at night. When this problem occurs on my machine it's usually when I come in the morning and start making changes to the document I was working on last.

I do remember the message that jayejoseph mentioned having to do with the network. The message I received a few moments ago didn't mention anything about the network but for the most part, every time my ID crashes the message does say something about loss of connection to the network.

Other than that, ID runs smother than a baby's @55.

So far so good.

[Guy_Smiley@adobeforums.com]

[email]Gabriel_Ayala@adobeforums.com[/email] wrote in
news:3bb53ea2.11@webx.la2eafNXanI:

> The message I received a few moments ago didn't
> mention anything about the network but for the most part, every
> time my ID crashes the message does say something about loss of
> connection to the network.

Is your Windows login profile on a network drive or local?

[jayejoseph@adobeforums.com]

Mine is on a network.

[Guy_Smiley@adobeforums.com]

[email]jayejoseph@adobeforums.com[/email] wrote in news:3bb53ea2.13@webx.la2eafNXanI:

> Mine is on a network.

That means that the InDesign preference files, recovery files, and
various other "scratch" files that are written to and read from more-
or-less constantly when you use InDesign are on a network share. If the
availability or latency of accessing this share is less than perfect,
it may be causing the problems you are seeing.

Ask your IT department to set you up a local profile.

[jayejoseph@adobeforums.com]

Thank you! I will go talk to them and see what they can do.

[Gabriel_Ayala@adobeforums.com]

Is your Windows login profile on a network drive or local?




Ok, I'm stupid. I don't know the answer to that one. LOL

I will have to ask my the admin I guess.

[Kathy_McDermott@adobeforums.com]

You said: "One thing I should add is I leave ID on all night when I leave at night. When this problem occurs on my machine it's usually when I come in the morning and start making changes to the document I was working on last."

Here's a suggestion: When you come in in the morning, before you start working on the ID document, double-click on My Computer and look for the Network Drive where you know your ID document resides. Under the "Type" column, see if it says "Disconnected Network Drive". If so, double-click on the Network Drive to force the computer to reconnect to the drive. After that has succeeded, begin working on your ID document. See if that fixes the problem.

It sounds to me as if your computer may not be maintaining persistent connections to the network shares. Or, in other words, your connection to the network drive may be timing out due to inactivity.

[Gabriel_Ayala@adobeforums.com]

I found out through the system admin that he sometimes re-boots the server and that's what causes the disconnection.

Thank you for that solution.