Does anybody know what error 1014 means?
The background is this:
We wish to migrate our Baan system to a new server as it is getting old.

We buy and installed a new Windows 2003 server. (lets call it Baan2)
We installed SQL Server 2000 and service packed it up to date on Baan2.
We used SQL Server DTS to copy the data, all tables and objects, from our live server (let's call it Baan1). Baan1 is Windows 2000 Server and SQL Server 2000. We have used SQL Server Enterprise Manager on Baan2 to see the data in the database on Baan2 and it seems to be all there. We copied all of the folders in the BSE (e:\baanivc3) from Baan1 to Baan2.
We have used ODBC and MS Access to view data from Baan2.

However, I can't log in to Baan2 using the Baan Windows client as it gives errors. I have tried logging in using the BW client from another p.c. and also using a copy of BW client on the Baan2 server.

In the event viewer of Baan2 the error is:

Event Type: Error
Event Source: Baan
Event Category: Msql7_srv
Event ID: 1000
Date: 16/03/2007
Time: 13:26:55
User: APS-BAAN\baan
Computer: APS-BAAN
Description:
Env bse (e:\BaanIVc3)
Prog msql7_srv file \db\servers\MSQL\msql_error.c # 573
Keyword MSQL Messages
Username baan type S language 2
Process 0xf9c
Lasterror 0
Errno 0
bdberrno 0
Message
dbs_errno = 1014 Error 1014 occurred:
Error sqlcode 14 (sqlstate: 08001, Return code: -1, diagRecNum: 1) during SQLConnect.
[Microsoft][ODBC SQL Server Driver][Shared Memory]Invalid connection.
Flushed at \db\servers\MSQL\msql_error.c : #578.

I can't find any reference to what error 1014 is. Shared Memory service on Baan2 seems fine also.

Thanks

Ed

dbs_errno = 1014 Error 1014 occurred:
Error sqlcode 14 (sqlstate: 08001, Return code: -1, diagRecNum: 1) during SQLConnect


If you can look up in the manual of your database server, it should give some direction. Look for error code 14 or sqlstate 08001 in your manual.

As far as the BAAN Errors manual is concerned, error code 14 has following meaning:


14 EFAULT Bad address
The system encountered a hardware fault in attempting to use
an argument of a system call.

It looks like Baan is trying to connect to the database through ODBC rather than a named pipe.
Although that should be possible (never tried it), it's not the preferred method and there seems to be a problem with your ODBC settings.

Part of the solution was the tabledef file. "tabledef6.1" was incorrect as we had just copied it across to the new server. With multiple MS SQL Server instances it should look like this:

tisfc001:200:msql7(MSQL_LEVEL1=1,MSQL_SERVERHOST=192.168.0.99\INSTANCENAME):Y
cpcom000:*:msql7(MSQL_LEVEL1=1,MSQL_SERVERHOST=192.168.0.99\INSTANCENAME):Y
*:*:msql7(MSQL_LEVEL1=1,MSQL_SERVERHOST=192.168.0.99\INSTANCENAME):N

Where INSTANCENAME would be something like BAAN1

Hope this helps anybody migrating to a new server.

Ed,
Does it mean that if you have multiple instance on the same server, each line in the tabledef6.1 has to be repeated for as many instances(including the last line)?

Whats the last line mean anyway?
*:*:msql7(MSQL_LEVEL1=1,MSQL_SERVERHOST=192.168.0.99\INSTANCENAME):N


sk

Per Baan instance (BSE) you have to indicate what database to use. (I'm not using the word instance there to avoid confusion. lol)

In the file tabledef you can additionally point specific (groups of) tables to a different database.

So in a real heavy-duty-big-boy environment you could store your financial administration on a different server than your sales data.

Tabledef should always end with that last line. In most situations it is the only line you'll ever need. It simply meanse to store all tables (*) from all companies (*) in the SQL Server instance named INSTANCENAME on the database at 192.168.0.99.

Out of interest the last character (Y or N) relates to auditing - Y means auditing on, N means no auditing.

Ed

Thanks guys!!
One last question. The file tabledef6.1 is created when you run the session Create Runtime Database Definitions(Tabledef) {ttaad4113s000) after Maintain Database Definitions {ttaad4110m000}, isnt it? There have been cases, for instance Ed's scenario, where you had to manually update the file tabledef6.1 to point to the right server. Now the question, once this is set.. is it important to run the above mentioned session(CRDD) or any other runtime sessions once you log into Baan ?

sk

There have been cases, for instance Ed's scenario, where you had to manually update the file tabledef6.1 to point to the right server. Now the question, once this is set.. is it important to run the above mentioned session(CRDD) or any other runtime sessions once you log into Baan ?
When you login into Baan after you manually change tabledef6.1 you have to correct data in Baan tables using session Maintain Database Definitions. After that run session ttaad4113s000 and check if new tabledef6.1 is same as this manually created.