Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to attach to \\HQMAIL002\Mic 1

Status
Not open for further replies.

Americas911

IS-IT--Management
Nov 19, 2002
19
US
Unable to attach to \\HQMAIL002\Microsoft Exchange Directory.
The device cannot be found.
Has anyone ever gottn this error?



Unable to attach to \\HQMAIL002\Microsoft Exchange Directory.
^ ^ ^ ^ ^
Unable to attach to \\HQMAIL002\Microsoft Exchange Information Store.
The device cannot be found.


^ ^ ^ ^ ^
Unable to attach to \\HQMAIL002\Microsoft Exchange Information Store.



I can backup everything else...Seems like a permissions problem but everything seems good. Giving that error on 5 of the 9 Exchange 5.5 servers we have.
Tried reinstalling backup exec 8.6 and checked all permissions. I started backing up using NT Backup yesterday.
But would like to get this fixed as soon as possible.

Any help would be appreciated.
 
I had this same issue last week when I built a new server for my backup system. I upgraded the server to Windows 2000. When I ran the full backup over the weekend it missed the Information store and the Exchanged directory. I am assuming you have the Veritas option licence for Exchange already installed. You will need to install the Exchange Administration Utility on the Server that is running Veritas. Same goes when backing up SQL databases. The SQL Admin Utility needs to be installed. Hope this helps.

Keith H., MCSE
 
I have a similar error. The error I got is:

Unable to attach to \\LST2\E$.
Access is denied.

^ ^ ^ ^ ^
Unable to attach to \\LST2\E$.
^ ^ ^ ^ ^

LST2 is a NT4.0 domain server and drive E is not shared. I am able to map to drive E$ fine. I also see the drive E$ available in the Backup Selection tab too. I am also sure that the remote agent service is also running fine in the client comuter too. We do not have an exchange server. Mind if anyone give me a hint on this problem?

Thank you,

ljCharlie
 
Has there been any resolution to this issue.. I have the same issue.

Alshrim
System Administrator
MCSE, MCP+Internet
 
For the exchange error, check your DNS settings to make sure the Exchange server resolves properly. Use nslookup to verify this.

Also ensure that the Backup Exec Service account is a Service Account admin on the site, organization, configuration and server levels.

Open Exchange Admin on your BE server, make sure you can access that while logged on as the Backup Exec Service account.

Just a couple of quick thoughts there.

Hope one helps.
 
Yeees.. that's it !!!

I did this a year ago - and i remember seeing this error before .. but i couldn't remember for the life of me was the resolution was... Thank you thank you thank you!!!

It will gimme something to work with.



Alshrim
System Administrator
MCSE, MCP+Internet
 
As luck would have it .. i don't even have a restrictanonymous DWord in my registry... something very odd here...

I've added the DWORD.. let you know how it works out.

Alshrim
System Administrator
MCSE, MCP+Internet
 
Cripes!! Ok.. i feel like a dink.... the solution is simple...

In going over the complete installation of my veritas software.. i realized that I hadn't installed the Exchange Server agent...

As shown here:
Thanks all...

Alshrim
System Administrator
MCSE, MCP+Internet
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top