Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
DennisMenace
Starting Member
4 Posts |
 Posted - 2008-03-26 : 00:25:27
|
| Our setup here is with a 2 node cluster with log shipping enabled to a DR standalone server. The DR server is also acting as the monitor server.There are 18 databases involved in the log shipping process and replication is set to occur every five minutes.The problem is that in the SQL and Windows logs on the DR server I'm seeing a series (6 in a row for each replication cycle) of connection errors for the sa user. The actual error is incorrect password sev 14 state 8 and the source in the SQL cluster.I think that I've found the problem in that one of the transaction backup jobs for one of the db's is set to use SQL authentication unlike the other 17 db's.I've reached this conclusion by1. the log_shipping_monitor_primary record for that one db on the DR/Monitor server is not updating the last backup time.2. Verified that on the Primary server in log_shipping_primary_databases that this job is the only one using SQL authentication.3. The job step that runs executes c:\Program Files\Microsoft SQL Server\90\Tools\Binn\sqllogship.exe which as part of it's process updates the monitor server record.So finally for the question, can I directly modify this table and set the field so that it use integrated authentication? Or alternatively is their some other way of changing this setting without recreating the job and refreshing the whole log shipping process? |
|
|
|
|
|
Advice on Modifying log_shipping_primary_databases