Technical and Installation Discussions

[mnorton]

I'm trying to install MAS 200 4.4 on a new server and retire the old server which is running MAS 200 4.3.  The problem I keep running in to is a failure to print or preview anything due to an ODBC error. The error is:

"The following error occurred while connecting to the SQL server: S0000 [ProvideX][ODBC][SAM]Version conflict between the client driver and the server" 

This problem only happens after the migration.  Printing/previewing in the example company prior to migration is not affected.  In looking at the SOTAMAS90 dsn it changes the server from the present server to the old server.  I'm going from Server 2003 R2 to Server 2003 R2, but a different machine would have a different SAM identifier.

Anybody have any ideas?

Much appreciated,

Michael

[rmikolainis · Accepted solution]

Version Reported: 4.40 

Subject:

"The following error occurred while connecting to the SQL server:  S0000: [ProvideX][ODBC Driver][ISAM]Version conflict between the client driver and the server." when printing using the CS ODBC driver after upgrading to 4.40

Possible Resolution:

The CS ODBC driver is pointing to the prior installation.  Confirm the path is correct by viewing the properties of the Providex IO Service.  If not correct uninstall the service and reinstall from the new location 

• To Un-install the existing instance, run this program with the "-u" argument from a DOS prompt or the Start - Run Command ( for example, ..\MAS90\Home\Lib\_Appserv\CSODBCService.exe -u)
• To Install execute the CSODBCService.exe from the new location

[mnorton]

I followed your instrucrions and it worked perfectly.  Thanks!

[mnorton]

I spoke too soon............

I followed the instructions and no longer had the incorrect server listed in ODBC, but then I no longer had a connection to the company that I migrated.  As I tried to access data in that company I was asked to set up all the modules as if I had just created the company, without any data.

I was wondering:  the companies set up on the old server had the C/S ODBC service set up due to some latency issues from a previous 2 location configuration over a slow connection.  On the new server this is no longer the case as there is now only one location and the network is now full-speed gigabit.  Since the migration is pulling over the ODBC settings from the old server would it make sense to disable the service prior to migrating, thereby avoiding the issue altogether?

If I do disable it, will it affect the present users?  I am really trying to avoid interrupting present users while I run the test migration to the new server.

Thanks,

Michael

[bdelgado]

I am getting the same error - I've done these installations dozens of times without issues. I am running the new MAS 200 on Windows 2008 R2 64 bit. Upgrading to 4.50 from 4.30. The old MAS 200 is on a separate server. Trying to convert Crystal Reports and receive error "version conflict between the client driver and the server"

I see there are a few posts in the forum that mention the same issue that go back to last year however; there is no resolution that works. Sage had nothing on their knowledgebase regarding this exact issue. I'm pissed that I have to do this crap on a weekend and it does not work. In addition, this is the kind of issues that we will be charged for under their new support plans. Knowledgebase is less than adequate and we should not have to deal with these types of issues on software at this stage of the game. Sage needs to get their act together and focus on providing a quality product rather than focus on Sales - With a good quality product, sales will follow!!!

Sorry for the venting but I am getting fed up with this software and Sage.

If anyone has a resolution to this issue it would be greatly appreciated.

[bdelgado]

I think I figured it out - The ODBC setup in MAS 200 System Configuration is pointing to the old server IP address. In addition, when you run the Crystal Conversion Wizard, under servers, it is pointing to the old server IP address. Change the IP address to the new server and it seems to work. I have to do a bit more testing however; I think this will address my issue and hopefully others.