Unable to attach message. Access is denied. 3

[nuedge]

Hi all!

Recently we have moved a folder from one server to another. The server we moved the folder to is a Snap! server. Anyway, since we have moved this folder and told backup exec to include this folder to be backed up it hasn't worked. We get a message of:

Unable to attach to \\FP-03\ScanFile.
Access is denied.
^ ^ ^ ^ ^
Unable to attach to \\FP-03\ScanFile.
^ ^ ^ ^ ^

When I go to the job definitions tab and select the job. Under the selections tab I can see my folder on the snap! server fine (no access is denied messages or log on as blah blah messages!)

Can someone please help me????

Regards..

 

[snowbird]

I'm having similar problem. A scheduled unattended backup won't/can't attach to a user-defined share if I have logged off of the server (NT4). Gives same message you get.
I'm hoping someone has a solution.

 

[nuedge]

Sorry, need to get this back to the top, has ANYBODY else ever encountered this problem before?

 

[BACKUPDUDEw2k]

There is a fix for this on the Veritas website. Check your local security policy. And make sure your settings for "Additional restrictions for anonymous connections" is set to "None, Relay on default permissions".

 

[Guest_imported]

I had EXACTLY the same problem and discovered by trial and error and some help from SNAP [Quantum] that I could get around this by setting up and using a specific account.

I configured all the BEx for NT services to login as user Backup and set a password. I ensured, using the SNAP security, that user Backup had full control and using NT security that Backup was in the Domain Admin user group. I then logged on to the NT console as that user, opened BEx and made my backup selections. When prompted by BEx to login I used the Backup account and was able to select and consistently backup the SNAP server. Kind of a klugey fix but in the absence of anything else, it solved the problem.

 

[Guest_imported]

We are currently experiencing the same 'Unable to attach' message whilst trying to use B/E and the Oracle Agent. We have done this successfully on other servers and databases but we haven't come across this error before. This particular database is Oracle version 8.1.5. We initially thought we had a problem with the OCIW32.dll but this was a red herring. If anybody has had similar problems I would be grateful if they would post their solutions.

 

[nikpatel]

I am having a similar problem in that Backup Exec will let me attach to some userdefined shares using the admin account and others it will not attach to on the selection screen.

I also have selections which can be connected to and selected for a backup, but when the back up actually runs it will not go thru!! access denied>>>>unable to attach>>> to \\server\share!

Any ideas please!!

 

[nikpatel]

Thanks but have corrected this problem by using a standard account for attaching and also i just put on service pack 2 for windows 2000 server....

Thanks anyway

 

[Tobez]

The wonderfull world of veritas. ok Ive had this problem several times, system state also not being able to attach to whole servers etc. What the process that did me was . firstly make sure the backup user is admin and domain admin rights, then ( i dont know exactly where this is but if u search veritas its in there) there is a file called BEWINNT <<<<<< this holds all the login and permission info for veritas so if this is incorrect IE you have altered permissions or logins this doesnt change. Follow the instructions on Veritas site in short DELETE it restart veritas and relog it on, it will then recreate this file with all the info needed. I did this and mine now backs up all 3 of my servers and system states etc.


Can i just say before i did this i tried registy edits , new user accounts permisions etc none worked , but this did.

if you get permission denied and the user is domain admin or admin then im more or less 90% thats u need to do the BEWINNT file..

hope i helped

Rob

 

[Guest_imported]

Yes,Rob, that worked! (I'm using BE 7.3)

I had installed a copy of the BE Admin tool on another computer and this problem started appearing on Jobs I had editted from there - even though the attach accounts were never altered.

As you suggested, I re-named the file c:\Program Files\VERITAS\Backup Exec\NT\DATA\Bewinnt7.sch, re-started the services and the offending backup is now &quot;running&quot;.

I'll have to check if this re-occurs when I alter back-ups from &quot;remote&quot;.

Cheers

Phil

 

[protos]

This file you need to rename that holds all the network config. info
is called

bewinui.uni

stop BE services
rename this file to bewinui.old
or
delete
then restart BE services
this will 'blank' out the attaching info.
also there is a utility on the support.veritas.com
website that you can use to see what is in this file.
do a search on support.veritas.com
for file type of Utility only
GooD LucK

 

[nuedge]

Many thanks to Tobez and Protos.

I had to delete BOTH the bewinnt7.sch and the bewinui.uni files to solve the problem

Thanks again

 

[Spirit]

Thanks Tobez & protos that fixed it nicely!

Nothing like that on the Veritas website.

Thx,

Iain