FMS

[edie209]

I have been having a problem with FMS for quite some time now and I was hoping that the new update would end this error but it hasn't, It seems to happen when we have two users on FMS and surley it should cope with that?

 

Here is a scrren shot of the error just incase someone has seen it and know a fix, (our local sims support have been looking into this for a couple of months now and still have not come back with any real solution

 

 

 

 

<!--url{0}-->

[plexer]

Is it happening on a particualr machine or machines or from anywhere.

 

I presume the database server is running and is generally conatactable from where you have the problem?

 

Any client firewalls running that may be blocking connections?

 

Ben

[edie209]

We only use FMS on 3 machine in the admin offices, the database is running and the XP firewall has been opened and still we get the error

[plexer]

Have you tried turning the firewall off completely?

 

OBDC setup correctly?

 

You can ping etc.. the host that you are trying to connect to?

 

Ben

[pete]

Is the FMS database server (SQLAnywhere) installed on the main SIMS server or one of the XP workstations?

[edie209]

@pete yes the SQLAnywhere database is on the main sims server

 

@plexer I have turned the firewall off completly and still get the problem as to ODBC how can I check the setup?

[wesleyw]

Have you got an installation of FMS on the Server?

 

 

Wes

[edie209]

Yes the installation of FMS is on the Sims server

[wesleyw]

When running FMS on the server do you get the same error?

 

Wes

[edie209]

I have not tried running it directly on the server I will try that tomorrow as I will have to get one of the admin girls to do what they do thats when the problem seems to happen

[Ric_]

Check that the SQLAnywhere location is that as seen on the server, not the client and that the user has sufficient priviledges to the IDAPI and .OCX files on c:\ of the client.

 

FMS does some wiered stuff and will go off hunting for the server if the path is wrong - this is why it will work sometimes and not others.

[edie209]

Thanks Ric I will try in the morning

[pete]

Work through KB7885 on Capita Supportnet, reproduced below (the error is slightly different). I had this handy because we got caught out by the "2 network cards" bit recently after replacing dumb switches with managed ones. If you don't have a login, apply here:

 

http://support.capitaes.co.uk/newlogin/register.asp

General SQL error
Sybase ODBC Driver Unable to connect to Database Server: unable to start Database engine
Alias: dbInitialConnection

Occurs after running the FMS Module shortcut.
Advice 	
Fix 1

Check the database server is running on the server as follows:

1. At Start | Run type DBSVMN50

2. If the service is not running, click the Start button to start service.

3. If the service is running, check which protocols are being used by following the next fix:

Fix 2

On the Server:

1. Stop the Database Server using Start | Run | DBSVMN50 and click Stop.

2. At Start | Run type: DBSRV50 -n SIMS_Server

This will try and broadcast on all protocols: make a note of which protocols are used.

On the Workstation:

1. At Start | Run type DBCLIENT -n SIMS_Server

2. This will try all protocols and will display which are used

3. Check if the protocol used by the client is also being used by the server, e.g TCPIP.

Note: the server normally uses NamedPipes as a protocol to connect to itself.

The protocol should be specified in the Database Server as follows:

1. At Start | Run type: DBSVMN50 and open the SQL Anywhere Service Manager.

2. Click Edit and then edit the parameter line. So, for example if protocols used are Named Pipes and TCP/IP it should read as follows:

-n SIMS_Server -c 8192 -tl 1500 -x NamedPipes,TCPIP

Note: The Service will need to be restarted for this to take effect.

The protocol should be specified on the Client machine as follows:

1. At Start | Run type: odbcad32

2. Select the System DSN tab

3. Select SIMS32

4. Click the Configure button

5. Click the Options button

6. The parameter line for TCP/IP should read as follows:

c:\sqlany50\win32\dbclient.exe -ta 600 -x TCPIP

Fix 3

Try pinging the IP address of the server from the workstation AND the IP address of the workstation from the server as follows:

1. Start | Run | CMD  

2. Type PING [iP address of server/workstation] 

eg. Ping 192.168.2.1

If two way connection is not possible this may be a problem with addressing on the network. 

Fix 4

This error can also occur if the workstation or server are using 2 IP addresses, or are on a subnet. If this is the case, unplug, or disable one of the cards to confirm that this resolves the problem.

To resolve the above issue, and other possible network issues, it is also possible to specify explicitly the hostname of the FMS Server the client is trying to connect to and for the FMS Server to only accept requests.

To try this:

1. Stop the Database Server using Start | Run type: DBSVMN50 and click Stop.

2. On the Database Server at Start | Run type:

dbsrv50 -n SIMS_server -x tcpip{Broadcast=FALSE}

3. At the workstation at Start | Run type:

dbclient -n SIMS_server -x TCPIP{host=10.128.2.226} (e.g ipaddress of Database Server)

4. If both of these respond positively (server starts and dbclient can see server):

5: At Start | Run type: DBSVMN50 and open the SQL Anywhere Service Manager.

6: Click Edit and then Edit the parameter line. So, for example:

-n SIMS_Server -c 8192 -tl 1500 -x NamedPipes,TCPIP{Broadcast=FALSE}

Note: The Service will need to be restarted for this to take effect.

The protocol should be specified on the Client machine as follows:

1. At Start | Run type: odbcad32

2. Select the System DSN tab

3. Select SIMS32

4. Click the Configure button

5. Click the Options button

6. The parameter line, for example should read as follows:

c:\sqlany50\win32\dbclient.exe -ta 600 -x TCPIP{host=10.128.2.226}

[edie209]

Thats really helpful pete all three of my PCs have two IPs (this is the way they were set up before I got here) so maybe there is some mileage in this fix.

 

I signed up to the Capita Supportnet site just before I came home from work tonight.

 

I will try these and post the results thanks

[PhilNeal]

I think that for multi-user FMS needs to be on the workstations.

[SpuffMonkey]

For us - the solution was a combination of adding the {host=} in the odbc stuff and ensuring that the user had permissions on the local FMS folder, the database folder, the sims.ini files in the c:\windows folder and the pdoxusrs file in c:\

[bossman]

Its a general ODBC error on the local machine: Just check that the two areas highlighted are correct for you sims server and that should be all. What i would do is check these settings with a workstation that works with FMS and then copy the settings.

[edie209]

Thanks for you replies I am looking at the machines now hope to post an update soon

[HodgeHi]

Did you resolve this? if so how since we are having the same problem here now. We ran an update and it had crashed half-way through and had to have the database rebuilt. The server FMS is now working but the 2 workstation clients aren't.

[klawd]

We are having same problem here. FMS took a shit when admin were using Equipment Register. Ever since then, FMS (randomly it seems) wont let users log into it.

 

The only "solution" seems to be to wait for a few minutes, retry login and it works.