Troubleshooting MIIS Event 6801 : unsupported error

Have an ILM server with the ERPMA running quite a while, smoothly.

 

After the SAP Admins migrated the SAP platform to the Unicode character set, ILM failed to import SAP data with an extensible-extension-exception.

 

In the event viewer, this error was displayed

Source: MIIServer

Category Server

Type: Error

Event ID: 6801

 

The extensible extension returned an unsupported error in MIIS.

 The stack trace is:

 

 "Microsoft.MetadirectoryServices.ExtensibleExtensionException: Exception has been thrown by the target of an invocation.

   at Microsoft.MetadirectoryServices.ERP.SAPMA.GenerateImportFile(String fileName, String connectTo, String user, String password, ConfigParameterCollection configParameters, Boolean fFullImport, TypeDescriptionCollection types, String& customData)

Microsoft Identity Integration Server 3.2.1008.0"

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The extensible extension returned an unsupported error in MIIS.

 The stack trace is:

 

 "Microsoft.MetadirectoryServices.ExtensibleExtensionException: Exception has been thrown by the target of an invocation.

   at Microsoft.MetadirectoryServices.ERP.SAPMA.GenerateImportFile(String fileName, String connectTo, String user, String password, ConfigParameterCollection configParameters, Boolean fFullImport, TypeDescriptionCollection types, String& customData)

Microsoft Identity Integration Server 3.2.1008.0"

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

 
This error is caused by a difference in character set code page between the ILM server and the SAP server.
They must match EXACTLY.
 
The ERPMA config tools has a code page definition in the server settings option.
 
But it’s not enough to switch the server settings to unicode…
Besides the code page definition in the ERPMA config file, also the discovery cache or the ERP config tool is impacted by the code page.
So if you need to switch the code page, you also need to reload the discovery cache.
 
When the server has been changed (on SAP server side), you need to reload the cache.
Keep in mind that this can take some time to completely load the cache.
 
 
To rebuild the cache, check the server settings, select the "rebuild discovery cache on next startup".
Close the ERPMA config tool and open it again.
When you connect to the SAP server, the cache starts to rebuild.
Keep in mind: the cache is loaded on a "per server" basis. So every SAP server has another cache file…
 
Reopen the ERPMA config file. Make sure you set the correct code page.
After switching the server settings make sure you save the configuration.
 
Then you better reopen the config file, again, because apparently the ERPMA config tools just checks the code page of the config file against the discovery cache when you open the config file…
In the ILM server I mentioned, I initially set the code page to "Unicode"…
But there are 4 versions of Unicode… which aren’t necessarily compatible with the code page on SAP server side…
 
When reopening the config file (and refreshing the cache) the config tool kindly suggested to use the Unicode Big-Endian code page.
I resaved the config file….
 
And the import got started again…
 
(to be completed with some screenshot and interesting links and documents on Unicode)
 
Unicode versions
– Unicode, Unicode UTF-7, Unicode UTF-8, Unicode Big-Endian
 
 
 
 
 
 
 

 

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s