Network drive error. Strange

[rtshort]

I got a call today from the "office". They were having trouble logging on to a networked software that we have. I went out to have a look at it.

The first thing I did of course was to check the mapped drive. It didn't have a red "X", but when I clicked to open it, I got the "open with" dialog box. Right clicked on it, properties, 0 bytes used 0 bytes available.

Right clicked on the drive to disconnect. Message "path can not be found".

Tried to remap the drive with a different drive letter. Got the "famous 'Send' 'Do Not Send'" message. "Install.exe has encountered a problem and needs to close. We are sorry for the inconvenience".

Formatted and reloaded the computer. Got the same message when I tried to map the drive, but let it run until the "hour glass" stopped. It mapped the drive and let the networked program run, but when I click on the drive in "My Computer" I got the same message again.

This seems like it may be a "memory resident" virus to me, since formatting and reloading didn't solve it, but the virus scan didn't detect one.

Anyone else ever ran across this problem or have any suggestions?

Thanks

Rob
Just my $.02.

 

[bcastner]

I agree all the behavior is odd.
Could you specify the server OS, and sevice pack level?
Connection type?
Could you specify the client OS, (I assume XP) and service pack level?

This at least "Tried to remap the drive with a different drive letter. Got the "famous 'Send' 'Do Not Send'" message. "Install.exe has encountered a problem and needs to close. We are sorry for the inconvenience"." is likely a profile issue.

However this: "The first thing I did of course was to check the mapped drive. It didn't have a red "X", but when I clicked to open it, I got the "open with" dialog box. Right clicked on it, properties, 0 bytes used 0 bytes available." makes sense only if the map was to the root of a volume that had no root entries, or the server disconnected that mapped session.

Start with the Windows Installer cleanup utility:

http://support.microsoft.com/default.aspx?scid=kb;en-us;290301

Lets get msiexec.exe out of the picture.

 

[rtshort]

Hi Bcastner,

Thanks for the response.

The Server OS is Windows XP Pro, with all of the updates current after SP2.

The Client OS is Windows XP Home with all of the current updates after SP2.

The connection type is Ethernet with static IP's.

I'll try the "installer clean up" but at the time I don't think that will help.

Everything was working fine until she couldn't get on this afternoon. I did install an Epson printer eariler that I thought may have caused the problem. I uninstalled all of the added items from Epson from "Add Remove Programs" and went through the registry and deleted all keys before that related to Epson before formatting and reinstalling Windows. Still the "almost" the same result after formatting and reloading.

Thx for the response. Any more help will be greatly appreciated.



Rob
Just my $.02.