problem connecting to remote server

[mihaak]

Hi,

We have some software that stores its information in a Pervasive SQL database. The setup is as follows:

- Server has software and database installed
- Client has special client install

The server happens to be a terminal server, so I ran the software on the server itself, in which case it runs fine. The server runs PSQL version 7.9-something WGE (so not the NT version).

The client does not seem to be able to connect to the database (I called the helpdesk for the software, and the completely undescriptive error message was interpreted as such). I don't know what version the client is running (no icon in the tray, don't know how else to retrieve that info). When I use the control center on the client, it only lists the local machine, which has a cross on it.

I can add the server by name, in which case it is also listed. When I tried to retrieve the information, it asked for a password. I tried the administrator's password for the box, which seemed to have worked.

These are the questions I have:

- How does the client know where the database is? Can I direct the client somehow?
- How is authentication set-up in case it is necessary?
- How are the licenses managed? (they are stored on the server)

Thanks for any help,

Martijn

http://www.oudheusdengroep.nl

 

[mihaak]

Some more details: The supporter advised me to turn of all protocols except TCP, which I did and later activated again to see if that resolved the problem. Also, another option was disabled and reenabled, but I will have to check the client (which I don't have access to at this moment) to see which one it is. Either way, the settings should be all set to default.

Another thing is that the original installation was SP3, but I upgraded using the SP4 I had downloaded earlier - this definitely is the update for WGE, so maybe that confirms that I am running WGE on the client also.

As a final note, I was _not_ able to install PSQL as a service on the client box, although it is running as a service on the server. This is because the server is a Windows 2000 server box, and the aforementioned software producer had told me that this was the only way to get it running properly (although it had been running as a regular program for years, until some upgrade broke the whole thing).

This is from the error log BTW:

15:58:56 W3COMSRV (*) E WinSock socket() error=10047.
15:58:57 W3MKDE (*) I Error initializing the SPX protocol. Error code: 11.
15:58:57 W3COMSRV (*) E WinSock socket() error=10022.
15:58:57 W3COMSRV (*) E WinSock socket() error=10022.
15:58:57 W3COMSRV (*) E WinSock bind() error=10050.
15:58:57 W3MKDE (*) I Error initializing the unknown protocol. Error code: 10050.
15:58:57 W3MKDE (*) I Resources allocated
15:59:32 W3MKDE (*) I Resources released
16:00:52 W3MKDE (*) I Resources allocated
16:01:41 W3MKDE (*) I Resources released
16:02:59 W3MKDE (*) I Resources allocated
16:04:58 W3MKDE (*) I Resources released

The (*) should be replaced by 0000032C IN\W3DBSMGR.EXE CLIENT_COMPTER_NAME
I also removed the dates (all one date of course) as well as excessive white space.

Thanks again,

Martijn