cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1765
Views
2
Helpful
2
Replies

ACS database not replicating

daven.delidle
Level 1
Level 1

Greetings,

We have two cisco secure databases running in geographically diverse areas. for some reason the "master" database will not replicate to the "slave" the error I get is just "outbound database replication failed refer to CSAuthlog file" the CSAuthlog file isn't much help either. I have tried reboting the box & stopping and restarting services but no luck. any ideas?

Thanks in advance.

1 Accepted Solution

Accepted Solutions

jreekers
Level 4
Level 4

Hi. You don't mention what version of CS you are running and on what platform (Windows or Solaris), but there is a known bug...CSCeh84997...that you may be hitting. Here are the details of the Release Notes:

The following error may be generated by the ACS appliance or ACS Windows

server after a database replication.

Database Replication.csv file:

ERROR Outbound database replication failed - refer to CSAuth log file

CSAuth log file:

CSBackupRestore(OUT) Failed to create output directory C:\Program

Files\CiscoSecure ACS v3.3\CSAuth\DbSyncScratch\\RegValues for DLL

Conditions:

The target folder on the replication slave machine already exists.

Workaround:

Delete the target folder

View solution in original post

2 Replies 2

efairbanks
Level 1
Level 1

I am getting the same error.

jreekers
Level 4
Level 4

Hi. You don't mention what version of CS you are running and on what platform (Windows or Solaris), but there is a known bug...CSCeh84997...that you may be hitting. Here are the details of the Release Notes:

The following error may be generated by the ACS appliance or ACS Windows

server after a database replication.

Database Replication.csv file:

ERROR Outbound database replication failed - refer to CSAuth log file

CSAuth log file:

CSBackupRestore(OUT) Failed to create output directory C:\Program

Files\CiscoSecure ACS v3.3\CSAuth\DbSyncScratch\\RegValues for DLL

Conditions:

The target folder on the replication slave machine already exists.

Workaround:

Delete the target folder