• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4974
  • Last Modified:

Sage Server changed domains and now clients cant connect

I have been migrating users over to a new domain and they have been connecting to the Timberline server fine.  But now that I moved the Timberline Server to the new domain the users cannot connect.  I believe it has something to do with the Pervasive Database Engine as connections are not going through.  Anyone have any suggestions?
0
ianober
Asked:
ianober
  • 7
  • 5
1 Solution
 
Bill BachPresidentCommented:
The Pervasive Server Engine authenticates users against the OS access rights.  If the users do not have access rights to the database, then they are denied access.  If you are going to be migrating things for a while, create a trust relationship between the two domains.  Otherwise, just increase the migration speed and get the servers and users on the same domain again.

You can test the Pervasive database, irrespective of Timberline, by trying to run the WBEXEC32 tool (if they provided it).  This tool allows you to open a file directly at the Btrieve level.  So, try to open your database file, and see if it works at THAT level. If not, then it will at least give you a reasonable Status Code, from which we can troubleshoot it further.  Post the status code!
0
 
ianoberAuthor Commented:
I am getting a status code 94 error for when I try and point to the data file.  There is currently a trust setup between the 2 domains.  The status 94 is a permissions issue so I checked them on the server share and they all have proper permissions to the data folder, but I am not sure what permissions they are asking about.  I will post the precise error here in a sec.
0
 
Bill BachPresidentCommented:
Status 94, or permissions, can be returned from a few different several areas:
1) The user logging in must have the correct rights.  Even if you get the Status 94, you might have still established a connection to the database engine.  Check in the Pervasive Monitor and see if any username shows up there.  Verify that THAT username has proper access rights.  Alternatively, try accessing the files in the Pervasive DEMODATA directory (C:\PVSW\DEMODATA\PERSON.MKD is a good choice) and see if they work or not.
2) The Server Engine itself must have the correct rights.  The service is probably set to log in as the SYSTEM user.  Verify this with the Services applet and go to the "Logon As" tab.  This SYSTEM user also MUST have access rights to the database files, as well as to other locations on the local HD where Pervasive wants to store files.  By default, the SYSTEM user is granted full access to the entire HDD at the root.  However, if you migrated to a new envronment, it is possible that the "old" SYSTEM account has rights, and the "new" one does not.  Try removing any user accounts that don't look right (i.e. lots of numbers in the account name) and re-grant the access to the SYSTEM user to the entire HDD.  Make sure that the rights cascade through to the data directory.

I could see the second one becoming an issue if you migrated the server to a new environment, changed its name, and then tried to just keep on running.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
ianoberAuthor Commented:
Ok, so I tried to run a Test Conneciton using the Analyzer and this is what I got:

Failed to connect to **********IP********** via TCP/IP protocol due to Winsock error 10060.  Connected host failed to respond.

I was on the monitor utility on the server and nothing came up.  The above was from a remote machine running the Timberline program.
0
 
ianoberAuthor Commented:
Ok, now I am almost positive the problem is on the server.  Again, I try to Specify a folder to read that data from and I get a Microsoft.Net Framework message box stating that it cannot connect to the Pervasive database engine on the server.  So I guess now we should focus there.

Also, when I run the Pervasive System Analyzer and select the "View Loaded Modules" options it shows a lot of modules as "Not Loaded" such as BREQNT.exe and such.  How do I get these loaded again?
0
 
ianoberAuthor Commented:
Permissions look good on the server.
0
 
Bill BachPresidentCommented:
View Loaded Modules is not useful in this case.  The 10060, however, is VERY useful.  

First, verify the Firewall is allowing Ports 3351 and 1583 through it.  Try disabling the server-side firewall if you have to.

On the server:  Go to a command prompt and enter "NETSTAT -A" and look for both ports to be in a LISTENING state.  
On a WS: Go to a command prompt and enter "TELNET servername 3351" and verify that you get a black screen, wiht no error message.  Do the same with 1583 (the SQL port).  Post your results.

If the server is NOT listening, check the status of "Accept Remote Requests" in the PCC.  Also, check the status of BOTH Pervasive services, which must be running.  Post these results.
0
 
ianoberAuthor Commented:
On the server:  Go to a command prompt and enter "NETSTAT -A" and look for both ports to be in a LISTENING state.  
On a WS: Go to a command prompt and enter "TELNET servername 3351" and verify that you get a black screen, wiht no error message.  Do the same with 1583 (the SQL port).  Post your results.

>Ok, this I tried at first and the ports were not open.  Then I checked the windows firewall and that was on >so I turned it off and the ports were then listening.

If the server is NOT listening, check the status of "Accept Remote Requests" in the PCC.  Also, check the status of BOTH Pervasive services, which must be running.  Post these results.

>Accept Remote Requests is "ON" in the server settings.

> As far as the services go only one is running, the Work Engine, the other one when you start it it >stops rights after it fires up and gives you a message saying that some services shutdown if they >have nothing to do.
0
 
Bill BachPresidentCommented:
OK -- so you have the Workgroup Engine insteads of the Server Engine.  Important fact.

After getting the ports in a LISTENING state, did it start working?  Also, please post the tail end of your PVSW.LOG file, as it may provide some additional insight.
0
 
ianoberAuthor Commented:
No, it did not start working.  I got a different error though on the Client station when I tried to connect to our database file.

Here's the log file:

11-12-2008 16:58:13 SRDESTUB        00000AAC W3SQLMGR.EXE    LAGUNA          E                        W3SQLMGR.EXE initialization failure. RC = 4083.
11-13-2008 08:31:55 ECAS_API        000007AC pcc.exe         LAGUNA          E                        ECASAPI (1.15.1.4116): Error 8508 - An error occurred when attempting to enable Btrieve access
11-13-2008 08:31:55 ECAS_API        000007AC pcc.exe         LAGUNA          E                        ECASAPI (1.19.1.4116): Error 8514 - An error occurred when unloading the MKDE
11-13-2008 08:31:55 ECAS_API        000007AC pcc.exe         LAGUNA          E                        ECASAPI (1.1.1.4116): Error 8517 - An error occurred when closing the session with the Workgroup engine
11-13-2008 08:31:57 W3MKDE          00000EB0 W3DBSMGR.EXE    LAGUNA          W                        Resources allocated
11-13-2008 08:34:11 SRDESTUB        00000B1C W3SQLMGR.EXE    LAGUNA          E                        W3SQLMGR.EXE initialization failure. RC = 4083.
11-13-2008 08:35:24 ECAS_API        000007AC pcc.exe         LAGUNA          E                        ECASAPI (5.16.1.4116): Error 8511 - An error occurred when attempting to enable SQL access
11-13-2008 08:35:24 ECAS_API        000007AC pcc.exe         LAGUNA          E                        ECASAPI (5.20.1.4116): Error 8521 - An error occurred when unloading the SRDE engine
11-13-2008 08:35:24 ECAS_API        000007AC pcc.exe         LAGUNA          E                        ECASAPI (5.1.1.4116): Error 8517 - An error occurred when closing the session with the Workgroup engine
11-13-2008 08:36:46 W3MKDE          00000EB0 W3DBSMGR.EXE    LAGUNA          I                        Resources released
11-13-2008 08:39:39 SRDESTUB        00000C54 W3SQLMGR.EXE    LAGUNA          E                        W3SQLMGR.EXE initialization failure. RC = 4083.
11-13-2008 08:39:53 SRDESTUB        000004B8 W3SQLMGR.EXE    LAGUNA          E                        W3SQLMGR.EXE initialization failure. RC = 4083.
11-13-2008 08:41:30 W3MKDE          0000085C W3dbsmgr.EXE    LAGUNA          W                        Resources allocated
11-14-2008 03:04:07 W3MKDE          0000085C W3dbsmgr.EXE    LAGUNA          I                        Resources released
11-14-2008 03:06:24 SRDESTUB        0000050C W3SQLMGR.EXE    LAGUNA          E                        W3SQLMGR.EXE initialization failure. RC = 4083.
11-14-2008 08:33:34 W3MKDE          00000678 W3dbsmgr.EXE    LAGUNA          W                        Resources allocated
0
 
Bill BachPresidentCommented:
Is this the log from the client or from the server?
What was the "new" error reported from the client?

The WGE is reporting OS Return Code 4083, which basically indicates that some module failed to load.  Not much help there.  I might recommend uninstalling all of the Pervasive components from the server and reinstalling clean.  That might be enough to kick whatever is causing this issue into the bit bucket...
0
 
ianoberAuthor Commented:
That is the log from the host.  It is running on a Windows XP PC and other PCs access the database on a shared drive on the host.  I am not sure if it is running a true SERVER role, probably not, but the SQL engine seems to be not letting people connect and use the shared database.

WOW, looks like it is working now Bill, thanks a bunch.  Winner winner chicken dinner!!
0

Featured Post

Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now