FS231 Error (Network Product)
At 02 DEC 2005 02:03:18AM David Goddard wrote:
Customer site is running the following:
AREV v3.12
Universal Driver 3.0 installed on Novell Server running in TCP/IP mode
Workstations: Windows 2000 SP2
Server: Novell V6.1
The site has a dedicated indexing machine running. Revparms with serveronly=1 in all the right places.
This configuration has been working fine since May 2005. They are in the process of upgrading the workstation to Windows XP. So far they have upgraded only one.
When the Windows XP computer logins to AREV the indexing machine gets an FS231 error, can't access !filename file (which ever index file is was trying to access at that time).
The computer running XP used to be running Windows 2000 Workstation and it ran AREV just fine.
Any clues on why this error is occuring?
Thanks
Dave G
At 05 DEC 2005 04:34PM Kevin Ruane Revelation Software wrote:
David,
What do you mean by "Revparams…in all the right places?"
If the indexer is turned off can the XP machine log in with no errors?
Is the !filename always the same or is it never the same when XP tries to log in and generates the FS231?
Anything in the lh3srvc log?
Cheers,
Kevin
At 05 DEC 2005 09:22PM David Goddard wrote:
G'day Kevin,
1. It's a different !file each time.
2. The XP workstation never gets an error. But when the XP workstation logs into AREV, the the indexing machine gets the FS231 error.
FYI - Index updates are turned off for all workstations except the dedicated indexer.
Thanks,
Dave G
At 30 DEC 2005 08:24AM Kevin Ruane wrote:
David,
I have not heard of this before…so I have no immediate solution, but a few more questions:
Are the versions of the Novell Client 32 the same on the W2K workstions as well as the XP?
Are there other Novell Servers on the Network that are running IPX (and can the Indexer and XP machines see them)?
Is the installation of the Novell Client 32 the same on the XP as it is on the W2K workstations?
What happens if you make the indexer an XP machine? Can the W2K Workstations access Arev without the FS231? Can a (2nd) XP machine?
The FS231 is a communication error - sometimes related to path, to port or a few other things. For a configuration that is working to get the FS231 would take a new element altering the existing communication . I am not sure what could do that…except for an XP workstion in your case.