Failover config errors with ODBC SQL Server Driver, cannot load

Unanswered Question
Jun 22nd, 2006
User Badges:

Note: A tac case have been opened, I am just posting this for a wider audience.


Unity 4.0.4 (Primary and Secondary)

SQL 2000 SP3 (800.760)

Exchange 2003 off box


Failover config runs fine on the primary server.

When running it on the secondary server, it errors out at the configuring sql replication

Error: "Failed to Configure SQL Replication"

After hitting OK, it does not terminate the wizard, but rather continues to the end and says failover config was successful.


Looking at the logs:

Error [0x800436e5] : [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot load the DLL replincrementlsn extended procedure or one of the DLLs it references. Reason: 126(The specified module could not be found.). [Microsoft][ODBC SQL Server Driver][SQL Server]The subscription could not be updated at this time. [Microsoft][ODBC SQL Server Driver][SQL Server]The subscription could not be created.

CAvSQLRep::CreateTransSubscription(SFG-HOU-VM2 UnityDb UnityDbPublication UnityDb) returned [0x800436e5]

Disconnecting from the SQL Server on 'SFG-HOU-VM1'


I noticed that all the tables in the secondary server were blank, so were the publications on the primary server.


I googled it and most of the hit mentiond

to verify if xprepl.dll dll is the correct version listed in the sp3 sp_help file.


Suggestion was to reinstall SP3.


Will SQL 2000 SP4 work in this case?

Is it supported on Unity 4.0.4?



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Tommer Catlin Thu, 06/22/2006 - 08:25
User Badges:
  • Green, 3000 points or more

Couple things..


make sure you have the latest and greatest patches for 4.0(4). (5) actually works better with SP1 and some additional patches to make Failover work and install correctly.


It will always say it is configured correctly, but when you actually look at licensing, it's not replicating anything...


Make sure you are logged in at the console. Do not use Terminal Server If did this through Terminal Server.. this where your DLL did not get installed.


Check the failover documentation.. You must create the correct accounts in AD for SQL to replicate correctly.


You might as well uninstall Failover completely on both servers and start from scratch. It's a pain in the arse.. I had to install failover about 10 times before it finally took. The fix was the new patches for 4.0(5). I'm not really sure about 4.0(4).. but I know there are issues with it.


cheers

Actions

This Discussion