Discussions

sn.exe is not recognized as an internal or external command

 
Phoenix
Top 150 Contributor
16 Posts
12/18/09 03:06 PM

I am trying to get OLSync installed following these directions http://help.outlook.com/en-us/140/dd490626.aspx.

I am stuck at step 4. I have installed Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1 but sn.exe is still not recognized as a command. Can someone help me get this going?

All Replies

12/22/09 02:18 PM

Hi,

The command sn.exe is located in "C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin" .

"C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\sn.exe" -Vr "C:\Program Files\Microsoft Identity Integration Server\UIShell\Microsoft.DirectoryServices.MetadirectoryServices.Config.dll"

Run the command from there. screenshot example below:

 

Patrick.

Reply
suggested by Patrick Layani
01/12/10 02:14 PM

I cannot install the SDK as I am using Server 2003 so I don't have SN.EXE on my system.  I am having the same trouble with the Eventid 1042.  As stated in this thread, I've uninstalled the agent after it failed, stopped the ILM service and it still bombs out when trying to authenticate giving this message:

 

Here is what I see in my application log:

Event Type: Error
Event Source: OLMA
Event Category: GALSyncSetup
Event ID: 1042
Date:  1/12/2010
Time:  2:58:28 PM
User:  N/A
Computer: LIVE1
Description:
The description for Event ID ( 1042 ) in Source ( OLMA ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: System.Management.Automation.Runspaces.PSSnapInException: Cannot load Windows PowerShell snap-in MIIS.MA.Config because of the following error: Could not load file or assembly 'Microsoft.DirectoryServices.MetadirectoryServices.Config, Version=3.3.1080.2, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)
   at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.LoadMshSnapinAssembly(PSSnapInInfo mshsnapinInfo)
   at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.LoadCustomPSSnapIn(PSSnapInInfo mshsnapinInfo)
   at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.LoadPSSnapIn(PSSnapInInfo mshsnapinInfo)
   at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.LoadPSSnapIn(PSSnapInInfo mshsnapinInfo, PSSnapInException& warning)
   at System.Management.Automation.Runspaces.RunspaceConfigForSingleShell.DoAddPSSnapIn(String name, PSSnapInException& warning)
   at System.Management.Automation.Runspaces.RunspaceConfiguration.AddPSSnapIn(String name, PSSnapInException& warning)
   at Microsoft.Exchange.XmaConnector.GALSync.CustomAction.XmaWrapper2007.DoILMConfiguration(Dictionary`2 parameters)
   at Microsoft.Exchange.XmaConnector.GALSync.CustomAction.GALSyncCustomAction.Main(String[] args).

Any ideas?

Reply
01/12/10 02:41 PM

DUH! Nevermind...

I didn't read the requirements carefully enough.  Once I installed the SDK and copied the code, the agent installed just fine.

Sorry for the wasted ones and zeros

Reply