mcrossland
asked on
Extra Backslash in database path error during backup
WSUS installed Windows Internal Database on my server automatically.
When I run a backup using Symantec Backup Exec, I receive an error that states
that the SQL backup job failed because the database path has multiple backslashes.
Here is the article from Symantec on that. http://seer.entsupport.symantec.com/docs/286848.htm
How do I check if this database has extra backslashes and if it does, how do I remove the extra backslash?
When I run a backup using Symantec Backup Exec, I receive an error that states
that the SQL backup job failed because the database path has multiple backslashes.
Here is the article from Symantec on that. http://seer.entsupport.symantec.com/docs/286848.htm
How do I check if this database has extra backslashes and if it does, how do I remove the extra backslash?
If you go into the selections for the job you created, change from Graphical to Text selection. (see figure 3 & 4 in http://seer.support.veritas.com/docs/269681.htm). Check there if you have any paths to SQL databases defined with extra backslashes.
The related article http://seer.entsupport.symantec.com/docs/284887.htm also suggests you could just apply one of the hotfixes that applies for your build of BE10.
The related article http://seer.entsupport.symantec.com/docs/284887.htm also suggests you could just apply one of the hotfixes that applies for your build of BE10.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
What directory do I need to be in when running the following command on SQL 2005? osql -S127.0.0.1 -E -d<database name> -Q"select * from sysfiles"
ASKER
OK. Here is what I got when running that command.
C:\>osql -S127.0.0.1 -E -d<C:\WSUS\UpdateServicesD bFiles\SUS DB.mdf> -Q"select *
from sysfiles"
The process cannot access the file because it is being used by another process.
C:\>osql -S127.0.0.1 -E -d<C:\WSUS\UpdateServicesD
from sysfiles"
The process cannot access the file because it is being used by another process.
On SQL 2005, try running
sqlcmd -S 127.0.0.1\WSUS -E -d susdb -Q "select * from sysfiles"
sqlcmd -S 127.0.0.1\WSUS -E -d susdb -Q "select * from sysfiles"
I hope this helps !