FsXPand/FsClient Error List
There are 2 types of errors:
1. You get a box and have to click a button to get rid of it,
2. There is a bottom line in either FsXPand or FsClient, but the program continous to run.Of course you can get other annoying messages, not being errors:
"FMC machine does not exist. Please create a share to FsClient folder."
- If there is not enough permission in your PC to create the share automatically, you have to do it manually. In that case the FsClient 6.1 folder should be shared as 'FsClient' (so give it a name), and for 8 users (ample for the use of multiple clients and maybe other network use like remote administration).
- Another reason may be, that it already exists, but in another place. So before installing a new version, please make sure that the old FsClient is no longer shared!
- On some systems, an installed program gets a share from Windows. With a long number as a name. In that case, remove that share and create it yourself.
- Make sure your Windows firewall is not preventing FsXPand/FsClient to run: Allow both programs to connect and allow the use of port 9000 and higher.
Specific errors on Windows 7 or Vista
1. Box to click away
First of all, FsClient will check if the necessary system files are on your machine. It will check write permissions as well for all appropriate directories. If you get a message about a missing file, or about an inability to write somewhere, check your permissions.
If this is ok, specific errors follow below:
Error Number Action
Automation Error -2005530518 (8876086a) This is a DirectX problem. Your video card may not be up to the task. Minimal configuration requires a GeForce II MX 64 MB (to run at all)
ActiveX component can’t create object 429 Component may not be registered. Normally, components are registered automatically.
Something went wrong during installation, or a system file may have been removed/unregistered inadvertently while uninstalling other software. To restore the registration of the possibly missing file, click Start, Run, type (one by one):
- regsvr32 dao360.dll (you may need to use regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\dao360.dll") ; please note that this path is different, depending on your language settings.
- regsvr32 scrrun.dll
- regsvr32 mswinsck.ocx
- regsvr32 comctl32.ocx
- regsvr32 dx8vb.dll
You should receive a message that the component was registered successfully. If not, ask support.Directinput not initialised 10049 FsXPand requires DirectX version 8. Please install DirectX if not installed.
Still the same problem?
Something went wrong during installation, or a system file may have been removed inadvertently while uninstalling a previous version. To restore the registration of the possibly missing file, click Start, Run, type:
- regsvr32 dx8vb.dll
You should receive a message that the component was registered successfully. If not, ask support.Address family not supported 10049/10047 - Is your network up and running (TCP/IP)?
- Do ALL your firewalls (including in routers etc.) allow FsXPand and FsClient to exchange data over the network?
- Do ALL firewalls allow port number 9000 and up to be used by these programs? At least one case is known where the router firewall caused the IP asked for to be inaccessible.
Type Mismatch 13 1. Keep regional settings of all the PC's running FsXpand or FsClient THE SAME
2. If you change settings, preferably change the ENTIRE setting, not only one value.PollFS Type Mismatch
13
Is your FSUIPC version correct? No other FSUIPC dll files present?
Path/file access error
75
Is there a share to FsClient folder called 'FsClient'? If not, create it.
If yes, and application stops: Maybe you are running on Vista. Check this list, or preferably use Windows 7, see hereUnexpected error, quitting
system Maybe you are running on Vista. Check this list, or preferably use Windows 7, see here Object variable or with block variable not set
91
Missing a system file, database component tends to be absent although the program will copy and register it: DAO360.dll in Microsoft Shared directory C:\Program Files\Common Files\Microsoft Shared\DAO\dao360.dll
Register it: Click Start, Run, type : regsvr32 dao360.dll (you may need to use the full path with quotes around it)
This could very well be another one: please check the files in your system32 directory
regsvr32 scrrun.dll
regsvr32 mswinsck.ocx
regsvr32 comctl32.ocx
regsvr32 dx8vb.dll
FsClient
Error Action DataArr: & error description Call support
FsXPand data Error: & error description Call support Init****: & error description Call support Display**** Error: & error description Call support FsXPand
Error Action Set****Values & error description Call support
First of all, see to it that you are Administrator (you are in the Administrators group).
Program compatibility should have been set to XP SP3 automatically.
1. Unexpected error, quitting:
Switch off your UAC for administrators, because Windows 7 cannot always cope with programs designed in the pre-vista age. If your edition doesn't allow that, use this reg file, or switch it off entirely.
2. Could not write to \\yourcomputername\FsClient\FMS: cause is your permission on the share created by the program.
- Check your sharing permissions on the \\yourcomputername\FsClient share: Properties, Sharing, Advanced, Permissions, listed is 'Everyone', click Full control.
- Make sure you have setup your network properly so you can read and write to files on the shares on your computer.
What is said below on Network problems on mixed OS environments applies in Win7 as well.
Challenges when running on Vista:
Install and run
1. Install and run logged on as administrator. Run as is not enough.
2. Be sure to switch to pre-Vista compatibility. Setting to XP, Win2000, or even Win98 might be needed.
(MS recently has admitted that backward compatibility for XP programs is not good enough. Now the advice to companies is, to wait for Windows 7. )
Must have Vista resource: http://www.helpware.net/VistaCompat.htm
If you get something like 'unexpected error', you are running under UAC: switch it off. Or use this registry file.
Network problems on mixed OS environments (Vista/Win7 AND (XP OR Win2k))
Vista looks at the network resources in a different way than earlier Windows systems. Usually, FsXPand on XP and FsClient on Vista works well. FsXPand is the server component.
It is needful that XP can see the Vista network resource to connect to (hostname, or IP address in the host box should be recognised)If the network doesn't seem to work in a mixed OS environment:
The question is whether Vista is seeing the WinXP machine (or the Win2000 machine if applicable) on the network.
Can you copy files from one machine to the other? Can you ping either machine from the other one? (Start, Run, type: ping 192.168.0.1, or whatever the IP address is you want to check on).
If that cannot be done please check the following:
1. Turn on network discovery in Vista
http://windows.microsoft.com/en-US/windows-vista/What-is-network-discovery
2. Turn on file sharing as well under the 'network and sharing center'
3. Make sure the Vista machine is in the same workgroup as the other pc's.
4. Be sure to grant IP addresses in the same range.
5. You have to set up identical user accounts (with the same user name and password) when you network XP or Win2000 Pro and Vista in order to access pre-Vista shares. Or Vista will not allow access for security reasons.
Here's how to share a folder, you first have to enable it.
http://maximumpcguides.com/windows-vista/share-a-folder-in-windows-vista/
Your anti-virus or personal firewall might be interfering with this operation. If you suspect, disable it for the time being.