Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Old Accpac on vmware, can see data, can't run executable

Status
Not open for further replies.

petermeachem

Programmer
Aug 26, 2000
2,270
GB
I have the tables linked to an Access programme, I can see the data fine. But we cannot run the executable, error 49153. It's a very old copy of Accpac we use for some historical lookups, version 5. something.

If I remote onto the server and look at the odbc's, i get 'An error occurred while retrieving local database names, Insufficient rights to get or set information'.
The monitor utility on the server says 'unable to connect to the specified remote server', i.e. cannot connect to itself.
The end of pvsw.log says

Code:
07-25-2012 18:34:53 NTMKDE          00000678 NTDBSMGR.EXE    SQL2K           I                        Error initializing the SPX protocol. Error code: 6.
07-25-2012 19:41:54 NTMKDE          00000680 NTDBSMGR.EXE    SQL2K           I                        Error initializing the SPX protocol. Error code: 6.
07-26-2012 09:06:59 NTMKDE          00000680 NTDBSMGR.EXE    SQL2K           I                        Resources allocated
07-26-2012 09:15:57 W3UPI229        00000958 W3MONV75.exe    SQL2K           I                        Btrieve server not found.  PNSL open session by name returned status = 3103.

I just found this
If you open PCC then select the Engine then
Configuration, Server, Communication Protocols, Supported Protocols
You will see lines:

Microsoft SPXII
Microsoft TCP/IP

change to

Microsoft TCP/IP
Microsoft SPXII

so I swapped them around and was told it couldn't save settings.

Anybody any idea?
 
49153 means the client can't see the server, so either Pervasive isn't running on the server, or something is blocking it like a firewall, or Accpac database setup is pointing to a different server name.
 
A reboot seems to have fixed it. It was rebooted after the vm was setup, seemed to want another one. I swapped back to the old server and guess what, the Monitor doesn't work on that either. We only use this system for the odd look up of stuff that didn't get imported to our new accounts system so I didn't realise this had broken.
Thanks for the suggestions
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top