W3491 Unable to insert UUID error

[SoupRice]

Running BAB 11.5 SP2 on Win Svr 2003 Ent SP1. Everything running fine, no changes, then W3491 "Unable to insert UUID to the database" error. Backup still runs but is very very slow, with this error at beginning of each session.

I recreated the job, ran Dbcheck on all DB's (no probs), delete the 3 index files and just finished doing a DB Recovery, still get the error.

Just wondering if there was anything else I should try before reinstalling. Thought about the SP3 update but thinking it might just cause more problems.

Any ideas are appreciated!

 

[GSC]

Hi,
Before you reinstall I would initialize the DB, see FAQ:
faq478-5164


I hope you find this post helpful.

Regards,
GSC

 

[SoupRice]

Thanks for the info. I just tried reinitializating and still getting the same error.

I guess another question: is this strictly an internal BAB DB error or can it possibly be the result of say BAB fighting for system resources on the server?

 

[dgates]

Have you solved this problem? I am new to the forum and have the same error. I have been back & forth with CA to no avail. Do I need to reinstall? Backup speed varies greatly. Can not get rid of the UUID error.

 

[SoupRice]

Sorry, not solved yet. I ran all the BAB DB tools but they did not find or fix anything. I then uninstalled and reinstalled BAB. It then started having a problem of not being able to start the DB engine at all. This server has very limited down time thus I am currently backing it up remotely.

I plan to reinstall again. I will add to this post when I get it running again. Please add anything you find out.

Thanks.

 

[dgates]

Thanks for the update. I am awaiting a call from another CA Tech. This is a month old. We run a remote SQL Database so I do not think that the command line db tools work the same way that they do with the VLDB. If I reinstall, I think I am going to blow up the database too and start from scratch.

 

[dgates]

We write to an external SQL Database. Yesterday we re-ran the setupSQL.exe after backing up the ASDB database on SQL. When the setup process got to where we were to rewrite the ASDB database, since it was already present, we cancelled out instead of going through with the process. Before we did this, we also used Server Admin (in ARCServe) to set the MS SQL User Account's username/pw. Server Admin is also where the System Account login information is which also needs to correspond with server roles and logins on the SQL server. This apparently reinitialized the database enough to allow the UUID to be inserted again without a problem. If you write to the VLDB database and do not have SQL, this may not be of much help. Hopefully it will provide some insight into your issue.