Community
Vault Forum
Welcome to Autodesk’s Vault Forums. Share your knowledge, ask questions, and explore popular Vault topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Backup Fails

4 REPLIES 4
Reply
Message 1 of 5
gross2
215 Views, 4 Replies

Backup Fails

I am running a batch file to backup my Vault. All of a sudden the backups
starting failing. This is the
message i get in the ADMDConsolelog.

6/17/2008 7:49:25
PM -Obackup -B"\\nslsnas\nsls2-sqlbkup\VAULTBKUP\A" -VU[username] -VP[password]
-S



6/17/2008 7:49:26 PM
==================================================================



6/17/2008 7:49:26 PM BACKUP PROGRESS: ADMS Console is currently in the
process of backing up a database set. Please wait...



6/17/2008 7:49:26 PM
==================================================================



6/17/2008 7:49:26 PM System.IO.IOException: Logon failure: unknown user name
or bad password.





The password has not been changed in the batch file or in the ADMS console.
I am using an

Vault administrator account to do the backup.
4 REPLIES 4
Message 2 of 5
tim.abla
in reply to: gross2

I have two questions:
1) Can you log in to ADMS Console directly with the user name and password that is failing on the command line?
2) If you back up to a local folder (i.e. use the same command line but change the backup location to something on that machine), does that succeed?

-Tim Abla


Tim Abla

Principal Engineer

Message 3 of 5
Anonymous
in reply to: gross2

It sounds like a problem with network permissions to the share location:
\\nslsnas\nsls2-sqlbkup\VAULTBKUP\A

When backing up to a remote machine, two Windows users need permissions to
the share: (1) the user the ADMS services run under [by default this is
MACHINE_NAME\AutodeskVault] (2) the user that SQL server is running under
[often this is a Windows builtin account of some kind, e.g. NetworkService]

Depending on how you have security set up, there could be different reasons
what the access is failing. One possibility would be that if you are using
Windows workgroup authentication (where you create a mirror user account and
password on the the remote machine), perhaps the user on the remote machine
has had its password expire. You could check for this by looking at the user
settings on the remote machine ( \\nslsnas).

Another possible way to diagnose this would be to turn on security auditing
on the remote machine. This would log any failures in the windows Event
Log - which might help identify the specific access problem.

Hope this is helpful,

Paul
Message 4 of 5
gross2
in reply to: gross2

Tim,
1. I can log in with the username and password that is failing.
2. Backing up to a local folder also fails with the same error.

wrote in message
news:5960150@discussion.autodesk.com...
I have two questions:
1) Can you log in to ADMS Console directly with the user name and password
that is failing on the command line?
2) If you back up to a local folder (i.e. use the same command line but
change the backup location to something on that machine), does that succeed?

-Tim Abla
Message 5 of 5
gross2
in reply to: gross2

Paul,
i will look into the permissions.


"Paul Gunn" wrote in message
news:5960707@discussion.autodesk.com...
It sounds like a problem with network permissions to the share location:
\\nslsnas\nsls2-sqlbkup\VAULTBKUP\A

When backing up to a remote machine, two Windows users need permissions to
the share: (1) the user the ADMS services run under [by default this is
MACHINE_NAME\AutodeskVault] (2) the user that SQL server is running under
[often this is a Windows builtin account of some kind, e.g. NetworkService]

Depending on how you have security set up, there could be different reasons
what the access is failing. One possibility would be that if you are using
Windows workgroup authentication (where you create a mirror user account and
password on the the remote machine), perhaps the user on the remote machine
has had its password expire. You could check for this by looking at the user
settings on the remote machine ( \\nslsnas).

Another possible way to diagnose this would be to turn on security auditing
on the remote machine. This would log any failures in the windows Event
Log - which might help identify the specific access problem.

Hope this is helpful,

Paul

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums