I am getting the same issue as of a couple of days ago. We have made no changes to the Exchange Server or the Networker server. This started happening all of a sudden. I am going to try a reboot of the Exchange server tonight, stop Networker services and a rename of the tmp folder in C:\Program Files\Legato\nsr to tmp.old and recreate a new tmp folder and restart services as I saw this suggestion in another post.
Yes i did that. Not sure if it helped but i am sure it would have cleaned out any old files through any crashes i have had in the past
I did a lot of things last night to try and fix it and it's a bit imbarrasing the solution. Well part of maybe.
I logged a sev 1 case with EMC last night and the responce was awesome. I had a cal lback in like 5 minutes. The tech was a big help. Aparently there is a known article on power link but i couldn't find it. It must have been somewhere in the 15000 returns from my searches.
In my case i am running win2k3 2 node cluster with exchange 2003.
XBSA-1.0.1 LNMs_2008.Build.274 7640 Mon Jul 12 21:04:02 2010 _nwbsa_is_retryable_error: received a network error (Severity 5 Number 12): The feature "NetWorker Module for Microsoft Exchange Server" is not properly enabled.
P.S. I also took the opertunity to upgrade my exchange boxes to networker client 7.5.2 and exchange module 3.5 SP3 i think or the current latest from EMC.
I started the Networker services with the same logon account that i use for the cluster account.
control panel> Services> Networker Remote service> Logon as & Pasword.
Check in Exchange System administrator Permissions to the cluster account. This needs to have 6 defined permissions to backup the exchange store & I'll see if i can list them. Or you can do what i did and give it full perms.
Send as
Recieve as
Administer info Store
Read
Write, I think
List
execute.
Don't quote me on these they may not be 100% correct. Also check the Advanced tab permissions for and DENY entries for that account and get rid of them.
On the server Networker server.
I configured my Job as per mormal with no logon account required but i did stop and rename the tmp dorectory here as well and created a new one.
in a command prompt window run nsrlic -v and check you exchange boxes have licenses. This is where i had the problem of a 2007 server taking one. if you don't have any exchange licenses left you might have to get a temp enabler from EMC. Have a go at backing up a store and see how you go.
We only have one Exchange Server so the license was not the issue. I did rename the tmp folder and that did not work either. I managed to create a different problem now that I am going to call EMC on.
I uninstalled the Exchange Module and Client from the Exchange Server then removed it from the Networker Server. I have the latest version of both Networker and Exchange Module. I reinstalled the Client software and the Exchange Module and the Exchange Server. I was able to use the Client Configuration Wizard to add the Exchange Filesystem for backup and had a successful back up of it last night. What I was unable to do was use the Client Configuration Wizard to add the Exchange Information Stores. Everytime I chose Exchange under the Available Applications window in the wizard, NMC became unresponsive, javaw.exe would go to 25% cpu utilization and I would have to close out using Task Manager. This I think is a key issue as I believe just configuring the Exchange Client to manually use nsrexhsrv.exe and MSEXCH:IS as a client configuration was part of the issue Exchange was failing with the new version of software.
We will see what EMC says. Thanks again for your input.
I don't use the client wizard to setup backups. Never have. I use MSEXCH:IS in my save sets and MSEXCH:pf. i have found it far easier and faster to rebuild an exchange server in the event of a disaster then try and restore one. especially with the AD integration it has. Now thats only exchaqnge 2003 not 2007. this i would have a go at restoring.
Have you tried creating a job without using the wizard?
Also please let me know how you go with EMC. .I am interested to know your solution.
I tested creating the client without the wizard and still received the same original message.
However, upon a little bit more exploration of logs and error messages.....
I was able to use the wizard to create just a "filesystem" backup. This backed up successfully the first night. However, it failed last night. Weird it would work one night and not the other. So I looked at the error message and it told me that the server was not configure properly on the Networker server, which was not there before. The name gave a different alias than what was used. Indeed the alias was a legit alias but was not configured properly during the wizard setup. Interesting...... I added the name under the client configuration and then went to look at the xbsa.messages on the Exchange server and lo and behold there was another alias, this one valid as well, that was being referenced as not being configured on the Networker server properly for the client. So I added this one to the client configuration and kicked off the Save Group manually and viola! It is backing up. Will wait and see the results.
So I know what the issue was but why all of a sudden after working great for quite a while why all of a sudden it stops working.
Sounds like possibly a DNS change maybe. any reason why you have so many names for this exchange box?
I was doing a new 2008 R2 file cluser yesterday and had the same problem. I found that the reverse DNS was not working correctly and after i fixed this the "Client on the networker server is not configured correctly " Fixed it's self. Gererally there should only need to be one name for an exchange server in single "out of the box" config.
IF you have rebuilt this box prior then it might pay to review your DNS forward and reverse lookup zones to make sure you don't have conflicting entries? That could explain why one day it worked and the next not.
That is what is weird. There was no DNS changes made at all. Those aliases have been associated with that Exchange server for over 2 years. Oh well. I am happy to say that Backups are performing as they should now. Now in reading all of the issues that have come with 7.6 I am really hesitant to upgrade. I think I will follow the creedo "if it aint broke, don't fix it."
jerry.reddick
51 Posts
0
July 12th, 2010 08:00
I am getting the same issue as of a couple of days ago. We have made no changes to the Exchange Server or the Networker server. This started happening all of a sudden. I am going to try a reboot of the Exchange server tonight, stop Networker services and a rename of the tmp folder in C:\Program Files\Legato\nsr to tmp.old and recreate a new tmp folder and restart services as I saw this suggestion in another post.
I will let you know how it works.
dugans1
2 Intern
•
186 Posts
0
July 12th, 2010 14:00
Hi Jerry,
Yes i did that. Not sure if it helped but i am sure it would have cleaned out any old files through any crashes i have had in the past
I did a lot of things last night to try and fix it and it's a bit imbarrasing the solution. Well part of maybe.
I logged a sev 1 case with EMC last night and the responce was awesome. I had a cal lback in like 5 minutes. The tech was a big help. Aparently there is a known article on power link but i couldn't find it. It must have been somewhere in the 15000 returns from my searches.
In my case i am running win2k3 2 node cluster with exchange 2003.
Here is what we checked last night.
on the client,
c:\program files\legato\nsr\applogs\xbsa.messages.
Open woth wordpad
see if you have this listed.
XBSA-1.0.1 LNMs_2008.Build.274 7640 Mon Jul 12 21:04:02 2010 _nwbsa_is_retryable_error: received a network error (Severity 5 Number 12): The feature "NetWorker Module for Microsoft Exchange Server" is not properly enabled.
P.S. I also took the opertunity to upgrade my exchange boxes to networker client 7.5.2 and exchange module 3.5 SP3 i think or the current latest from EMC.
I started the Networker services with the same logon account that i use for the cluster account.
control panel> Services> Networker Remote service> Logon as & Pasword.
Check in Exchange System administrator Permissions to the cluster account. This needs to have 6 defined permissions to backup the exchange store & I'll see if i can list them. Or you can do what i did and give it full perms.
Send as
Recieve as
Administer info Store
Read
Write, I think
List
execute.
Don't quote me on these they may not be 100% correct. Also check the Advanced tab permissions for and DENY entries for that account and get rid of them.
On the server Networker server.
I configured my Job as per mormal with no logon account required but i did stop and rename the tmp dorectory here as well and created a new one.
in a command prompt window run nsrlic -v and check you exchange boxes have licenses. This is where i had the problem of a 2007 server taking one. if you don't have any exchange licenses left you might have to get a temp enabler from EMC. Have a go at backing up a store and see how you go.
All the best.
jerry.reddick
51 Posts
0
July 13th, 2010 09:00
Hey Scott,
Thanks for the post.
We only have one Exchange Server so the license was not the issue. I did rename the tmp folder and that did not work either. I managed to create a different problem now that I am going to call EMC on.
I uninstalled the Exchange Module and Client from the Exchange Server then removed it from the Networker Server. I have the latest version of both Networker and Exchange Module. I reinstalled the Client software and the Exchange Module and the Exchange Server. I was able to use the Client Configuration Wizard to add the Exchange Filesystem for backup and had a successful back up of it last night. What I was unable to do was use the Client Configuration Wizard to add the Exchange Information Stores. Everytime I chose Exchange under the Available Applications window in the wizard, NMC became unresponsive, javaw.exe would go to 25% cpu utilization and I would have to close out using Task Manager. This I think is a key issue as I believe just configuring the Exchange Client to manually use nsrexhsrv.exe and MSEXCH:IS as a client configuration was part of the issue Exchange was failing with the new version of software.
We will see what EMC says. Thanks again for your input.
Jerry
dugans1
2 Intern
•
186 Posts
0
July 13th, 2010 14:00
HI Jerry,
I don't use the client wizard to setup backups. Never have. I use MSEXCH:IS in my save sets and MSEXCH:pf. i have found it far easier and faster to rebuild an exchange server in the event of a disaster then try and restore one. especially with the AD integration it has. Now thats only exchaqnge 2003 not 2007. this i would have a go at restoring.
Have you tried creating a job without using the wizard?
Also please let me know how you go with EMC. .I am interested to know your solution.
jerry.reddick
51 Posts
0
July 14th, 2010 08:00
Yes,
I tested creating the client without the wizard and still received the same original message.
However, upon a little bit more exploration of logs and error messages.....
I was able to use the wizard to create just a "filesystem" backup. This backed up successfully the first night. However, it failed last night. Weird it would work one night and not the other. So I looked at the error message and it told me that the server was not configure properly on the Networker server, which was not there before. The name gave a different alias than what was used. Indeed the alias was a legit alias but was not configured properly during the wizard setup. Interesting...... I added the name under the client configuration and then went to look at the xbsa.messages on the Exchange server and lo and behold there was another alias, this one valid as well, that was being referenced as not being configured on the Networker server properly for the client. So I added this one to the client configuration and kicked off the Save Group manually and viola! It is backing up. Will wait and see the results.
So I know what the issue was but why all of a sudden after working great for quite a while why all of a sudden it stops working.
Jerry
dugans1
2 Intern
•
186 Posts
0
July 14th, 2010 14:00
Yeah good question.
Sounds like possibly a DNS change maybe. any reason why you have so many names for this exchange box?
I was doing a new 2008 R2 file cluser yesterday and had the same problem. I found that the reverse DNS was not working correctly and after i fixed this the "Client on the networker server is not configured correctly " Fixed it's self. Gererally there should only need to be one name for an exchange server in single "out of the box" config.
IF you have rebuilt this box prior then it might pay to review your DNS forward and reverse lookup zones to make sure you don't have conflicting entries? That could explain why one day it worked and the next not.
Let me know.
jerry.reddick
51 Posts
0
July 16th, 2010 07:00
That is what is weird. There was no DNS changes made at all. Those aliases have been associated with that Exchange server for over 2 years. Oh well. I am happy to say that Backups are performing as they should now. Now in reading all of the issues that have come with 7.6 I am really hesitant to upgrade. I think I will follow the creedo "if it aint broke, don't fix it."
Thanks for you suggestions Scott.
Jerry