Jump to content
Sign in to follow this  
valas

Exchange 2007 Support Update

Recommended Posts

Thanks ... the Assert_log is attached.

 

Following system info:

Retrospect Info --

Multi-Server: 7.5.512

Driver Update: 7.5.13.100

Add-On Value Package 7.5.512

Running on Windows Server 2003 R2 x64 SP2 with all current Windows Updates.

 

Exchange Info--

Exchange Server 2007 with Update Rollup 6

Running on Windows Server 2003 R2 x64 SP2 with all current Windows Updates

Installed: Microsoft Visual C++ 2005 SP1 Redistributable Package (x64)

 

RBU User is a member of:

Domain Admins

Domain Users

Administrators

Backup Operators

 

Note: Back up a file server and sql server is running with out issues. The SQL agent registered successfully. Just having issues when trying to register the Exchange agent -- tried using the RBU as well as the domain admin account. Always get the same error.

 

Thanks!

 

 

Share this post


Link to post
Share on other sites

Engineering is still reviewing the log, but the first throught it some type of corruption to the config file itself, as I also suspected.

 

Please remove the config75.dat and see if you can license exchange. if this works, then unfortunately the old config is corrupted.

Share this post


Link to post
Share on other sites

Thank you for your assistance -- unfortunately we will have to wait to see what the engineers come up with. I deleted the config75.dat file and still no luck.

 

Anxiously awaiting a solution! Thanks again!

Share this post


Link to post
Share on other sites

Can you email me a copy of the most recent config75.dat file that failed? You would zip the file and email it to emcinsignia_forums@emc.com. Our engineers was to look in the file for a smoking gun.

 

Thanks!

Share this post


Link to post
Share on other sites

Rob,

 

Have you tried to backup the exchange server locally rather then as a client? Do you get the same problem if you install the Retrospect application directly on the server?

 

We would like to try and capture a debug log showing the failure.

 

1) type ctrl-alt-p-p (at the same time)

2) Go to Debug Logging and Set Trees and Volumes to 7

3) Go to Programmer and check Flush Log on write.

 

Reproduce the failure and then email me the operations log.utx file

Share this post


Link to post
Share on other sites

Sorry I have not gotten to this ealier -- between several other events going on here and waiting to see if the new version fixed this I did not try the instructions and upload the file. Needless to say, the new version did not fix my problem. Let me know how and I can send you the assert & operations log files.

Share this post


Link to post
Share on other sites
Have you tried to backup the exchange server locally rather then as a client? Do you get the same problem if you install the Retrospect application directly on the server?

 

We would like to try and capture a debug log showing the failure.

 

1) type ctrl-alt-p-p (at the same time)

2) Go to Debug Logging and Set Trees and Volumes to 7

3) Go to Programmer and check Flush Log on write.

 

Reproduce the failure and then email me the operations log.utx file

 

You can send the operations log (and assert log if Retrospect crashes) to emcinsignia_forums@emc.com

Share this post


Link to post
Share on other sites

Did you get the assert error with Retrospect installed directly on the exchange server or was exchange a client system?

 

Does it help to forget and add the client from Configure>Clients?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×