Missing Path Issues.

[dc3bb61]

THE FOLDER (%server root%\folder\filename) MAY BE LOCATED IN AN UNAVAILABLE
LOCATION, PROTECTED WITH A PASSWORD, OR THE FILENAME CONTAINS A / OR \.

This error message appears whenever my customer attempts to save a new file
to this location or save a current file as a different file name. This
applies to the whole drive on the file server. Have tried the share settings
with or without a password on the file server, deleted the original path and
re-pathed on client, the customer can open, change, and re-save original file
to drive. file server is a dell dimension x700 running windows 98se, client
is a compaq presario 6000 series running windows xp home (sp2). Also, this
started while customer had office xp on the system, un-installed office xp
professional and installed office 2003 professional an issue still continued.

 

[garfield-n-odie]

If you don't know the answer, what is your customer paying you for?

 

[Bob I]

The part about the fileserver being a dell dimension x700 running
windows 98se is problem. ;-)

 

[dc3bb61]

Thank you for your reply. More on-topic than "odie". The customer has agreed
to replace the system as I have concluded that it is a settings change on the
XP systems having to do with the latest security updates. The problem
cascaded and was not instant as the machines auto updated, also, I was able
to get a Cobol based DB program to operate properly among the clients after
re-mapping the drive. And as I stated, current files on the file server are
read/write, but any attempt to create a new file in either Office XP Pro or
Office 2003 Pro is met with the aforementioned error message.

 

[dc3bb61]

Thank you for your reply, more on-topic than "odie". (Get a life) The
customer has agreed to replace the Windows 98SE fileserver and a Dell with XP
will be replacing it shortly. I concour that it lies in how Windows 98 and
Windows XP transact. The problem was not instant among the clients but
cascaded as they received the updates. I feel it lies in one of the recent
Security Updates as all machines were in good working order untill just after
New Year's Day. (a week or so) I was able to connect among the clients a
COBOL based DB program once the drive was re-pathed. What is so unusual about
this is that the files curently on the fileserver are read/write among the
clients, but once an attempt to re-name is made, or create new, the
aformentioned error message occurs. The message suggests the drive location
doesn't exsist even after it just connected to the drive location to retrieve
the file.