Help: NMM 2.3 and Exchange 2010 error 0x80010105.

Question

Hi cant seem to get this working. First, I run 2008R2 and Exchange 14.01.0218.006. First, Config Checker looks ok, however last row says: Checking Exchange Configuration.. Fail EXCHANGE_NAME Exchange version [14.01.0218.005] is installed.The supported version is not installed.The supported versions are : Exchange 2003 SP2 or later, Exchange 2007 SP1 or later, and Exchange 2010 SP1 Rollup2 or later. Wrong version detected? When trying to run nsrsnap_vss_save.exe -? i get: C:\Program Files\Legato
srmagentps\client\bin>nsrsnap_vss_save.exe -?NMM .. changing backup name SLC-DC01 to primary name slc-dc01.contoso.com for multi NIC client. List of valid saveset entries for APPLICATIONS on client slc-dc01.contoso.com ...Initializing data to display...NMM ... Using client name SLC-DC01, the version of the Exchange server is Exchange 2010. 'APPLICATIONS:\Microsoft Exchange 2010''APPLICATIONS:\Microsoft Exchange 2010\MDB01''APPLICATIONS:\Microsoft Exchange 2010\MDB02''APPLICATIONS:\Microsoft Exchange 2010\MDBARC01' 68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success. When running from client: C:\Program Files\Legato
srmagentps\client\bin>nsrsnap_vss_save.exe -A  optype=conventional  -A 'NSR_SNAP_TYPE=vss'  -A 'NSR_ALT_PATH=c:\snapmnt'  -A 'NSR_CHECK_JET_ERRORS=all' -c slc-dc01.contoso.com -g 'Snapshot_Group' -m slc-dc01.contoso.com -s backup.hostname.se -l full -A snap_sessionid=1319462128 'APPLICATIONS:\Microsoft Exchange 2010'73064:nsrsnap_vss_save:Version information for C:\Program Files\Legato
sr\bin
srsnap_vss_save.exe:        Original file name: nsrsnap_vss_save.exe        Version: 2.3.0.87        Comments: NetWorker Module for Microsoft Applications (x64)50411:nsrsnap_vss_save:nsrsnap_vss_save: Data mover host name not specified. Assuming local host: slc-dc01.contoso.com80271:nsrsnap_vss_save:NMM .. Valid snapshot policy. Group: 'Snapshot_Group' Snapshot Policy: 'Serverless Backup' Snapshots Per Day: '1'  Retain: '0' Backup Snapshots: 'All' Level: 'full'.47363:nsrsnap_vss_save: nsrpsd service is running on SLC-DC01.contoso.com.NMM ... Using client name SLC-DC01, the version of the Exchange server is Exchange 2010.82624:nsrsnap_vss_save:Save set name APPLICATIONS:\Microsoft Exchange 2010 is valid.63352:nsrsnap_vss_save:NMM .. start the creation of a replica. Replica will be of type Default - which is VSS determined  Non Transportable.71224:nsrsnap_vss_save:NMM .. Exchange Writer: Consistency check required on the Proxy can take a long time 83164:nsrsnap_vss_save:NMM .. An error was detected during the replica creation.  Details in nmm.raw on SLC-DC01.contoso.com and in the Windows Application or System Event Log. 49931:nsrsnap_vss_save:RM .. 026671 ERROR:A COM error occurred while validating the version of Exchange. The error code is 0x80010105. The error message is: The server threw an exception..49931:nsrsnap_vss_save:RM .. 102206 ERROR:Validation failed.63335:nsrsnap_vss_save:NMM backup failed to complete successfully.Internal error.nsrsnap_vss_save: APPLICATIONS:\Microsoft Exchange 2010: failed68151 1319466630 2 0 0 3012 3080 0 slc-dc01.contoso.com nsrsnap_vss_save 39 nsrsnap_vss_save: Exiting with failure. 0 Please help, anyone experiencing the same problem?

36115_carloscor · Answer

Hi,

This is a configuration issue. It is documented in the NMM 2.3 Documentation.

You need to change the authentication in IIS. To do it so please do as follows:

1. Go to IIS Manager > Your Host > Sites > Default Web Site > Powershell.

2. On the right-hand side pane, double-click Authentication and Enable Windows Authentication.

3. In Windows Authentication, right-click and ensure that the Kernel Mode Authentication is clear.

Also check the bindings:

Start IIS Manager
Navigate to Ã Sites Ã Default Web Site
Select 'Bindings' under Actions - Edit Site or right click 'Default Web Site' and do properties -> Bindings.
Under Site Bindings, look for 'https' entry, select it and do 'Edit'
In Edit site Bindings Ensure 'SSL certificate' shows Microsoft Exchange (The certificate name may be different)
If the https binding does not exists for Exchange, create a new binding. (One for all 'all assigned' IP address and one for the local host (127.0.0.1))
Restart IIS.
Rerun the backup.

Thank you.

Carlos.

Mark_Bellows · Answer

Hello!

Oddly enough I am in a class on the NMM 2.3. The question is:

Do you have Rollup 2 installed with Exchange 2010?

If not, that is your issue. If so, we will dig into it further.

Let us know.

Release notes attached.

Mark Bellows

ltfrebac_d68d9c · Answer

I think I did all those changes regarding Bindings and Powershell. See attached screenshots:

ltfrebac_d68d9c · Answer

Sorry, I got the information from collegues that this particular Exchange server had been updated to RU5.I have applied Rollup 5 now and still same error as above.

Mark_Bellows · Answer

I am still working on this.

In the IIS permissions, be sure that the Windows Authentication properties page does NOT have the "Enable Kernel-mode authentication" option selected. If it is, un-select this option and see if that helps.

More to follow soon.

Mark

Mark_Bellows · Answer

I am sorry - I should have waited a few minutes before that last post.

I noted this in the information you posted:

83164:nsrsnap_vss_save:NMM .. An error was detected during the replica creation. Details in nmm.raw on SLC-DC01.contoso.com and in the Windows Application or System Event Log.

Please review this article:

NMM backups of Exchange requires unique drive letter for databases and transaction logs

http://solutions.emc.com/EMCSolutionView.asp?id=esg115055&usertype=C

I have also found out that NMM2.3 Build 81 and newer deals with a couple of the issues you are reporting.

Let me know if this informaiton helps.

Mark

Mark_Bellows · Answer

Can you tell me what the event view for the application and system shows on the exhange server?

Also, have you verified that you can performa tracert from the backup server to the exchange server and vica-versa?

Thank you,

Mark

36115_carloscor · Answer

Hi,

At this stage I would suggest you to take a look at the Application, System and Exchange event logs, so you can find more information.

Could be a permissions issue on the user starting up Replication Manager Exchange Interface.

Thank you.

Carlos

Thierry101 · Answer

hi all

seeing the same issue...it was working fine before...

RM .. 102206 ERROR:Validation failed.

RM .. 026671 ERROR:A COM error occurred while validating the version of Exchange. The error code is 0x80010105. The error message is: The server threw an exception..

36115_carloscor · Answer

Hello Thierry,

You would need to check again the IIS settings.

Please take a look at these settings:

1. Go to IIS Manager > Your Host > Sites > Default Web Site > Powershell.

2. On the right-hand side pane, double-click Authentication and Enable Windows Authentication.

3. In Windows Authentication, right-click and ensure that the Kernel Mode Authentication is clear.

Also check the bindings:

Start IIS Manager
Navigate to -> Sites -> Default Web Site
Select 'Bindings' under Actions - Edit Site or right click 'Default Web Site' and do properties -> Bindings.
Under Site Bindings, look for 'https' entry, select it and do 'Edit'
In Edit site Bindings Ensure 'SSL certificate' shows Microsoft Exchange (The certificate name may be different)
If the https binding does not exists for Exchange, create a new binding. (One for all 'all assigned' IP address and one for the local host (127.0.0.1))
Restart IIS.
Rerun the backup.

Let us know if that helps.

Thank you.

Carlos.

Thierry101 · Answer

Hi Carlos everything intact since the initial setup/config...lately failing...

36115_carloscor · Answer

Hi Thierry,

Could you please let us know if the settings I provided earlier are configured as they should, following the step-by-step I sent you?

Could you please render and paste here the full output of the backup operation?

Thank you.

Carlos.

ltfrebac_d68d9c · Answer

My issue was resolved simply by rebooting one of the Exchange hosts.

Christianlenny · Answer

Thanks, I had to restart my host and end works well. excuse my English, I speak Spanish...

NetWorker

Help: NMM 2.3 and Exchange 2010 error 0x80010105.

Was this post helpful?