Categories: Email Delivery Questions :

google apps dir sync failing - [FATAL] [plugin.postini.PostiniPlugin] Unexpected exception attempting to add remote users

Showing 1-4 of 4 messages
google apps dir sync failing - [FATAL] [plugin.postini.PostiniPlugin] Unexpected exception attempting to add remote users kob7iron 5/11/12 9:15 AM
Domain Name: 
Users Affected: 100+
Problem Description: GADS worked fine, but it didn't add aliases, but that was my fault - I forgot to add other domains to Mail Security.  I added the domains then tested with a few users by deleting the user and then running sync-cmd -a -c filename.xml again.  It worked perfectly fine and I started deleting 20 users at a time and running sync-cmd again.  It worked for about 100 users and now all of a sudden it's failing with these messages for the users I need to get back in there:

Unable to add user " user...@emaildomain.com" as a persistent, unexpected error occurred trying to process the block of changes it was in. Please check the fatal error log for more details on this problem. Exception: "com.sun.xml.internal.ws.encoding.soap.DeserializationException", Message: "Failed to read a response: javax.xml.bind.UnmarshalException
 - with linked exception:
[javax.xml.stream.XMLStreamException: ParseError at [row,col]:[10,6]
Message: The processing instruction target matching "[xX][mM][lL]" is not allowed.]"

Log file:
[2012-05-11 11:52:43,556] [INFO] [usersyncapp.cli.StatusLogger] Plugin "Postini Plugin" started remote application of changes
[2012-05-11 11:52:48,290] [FATAL] [plugin.postini.PostiniPlugin] Unexpected exception attempting to add remote users, attempt 1
com.sun.xml.internal.ws.encoding.soap.DeserializationException: Failed to read a response: javax.xml.bind.UnmarshalException
 - with linked exception:
[javax.xml.stream.XMLStreamException: ParseError at [row,col]:[10,6]
Message: The processing instruction target matching "[xX][mM][lL]" is not allowed.]
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(Unknown Source)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(Unknown Source)
at $Proxy38.addUsers(Unknown Source)
at com.postini.usersyncapp.plugin.postini.PostiniPlugin.processAddBatch(PostiniPlugin.java:1547)
at com.postini.usersyncapp.plugin.postini.PostiniPlugin.doApplyDiff(PostiniPlugin.java:908)
at com.postini.usersyncapp.sync.SynchronizationPluginGroup.executeApplyDiff(SynchronizationPluginGroup.java:129)
at com.postini.usersyncapp.sync.FullSyncAgent.applyChanges(FullSyncAgent.java:439)
at com.postini.usersyncapp.sync.FullSyncAgent.call(FullSyncAgent.java:125)
at com.postini.usersyncapp.cli.Sync.main(Sync.java:188)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
at com.exe4j.runtime.WinLauncher.main(Unknown Source)
Caused by: javax.xml.bind.UnmarshalException
 - with linked exception:
[javax.xml.stream.XMLStreamException: ParseError at [row,col]:[10,6]
Message: The processing instruction target matching "[xX][mM][lL]" is not allowed.]
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.handleStreamException(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.BridgeImpl.unmarshal(Unknown Source)
at com.sun.xml.internal.bind.api.Bridge.unmarshal(Unknown Source)
at com.sun.xml.internal.ws.client.sei.ResponseBuilder$DocLit.readResponse(Unknown Source)
... 16 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[10,6]
Message: The processing instruction target matching "[xX][mM][lL]" is not allowed.
at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(Unknown Source)
at com.sun.xml.internal.ws.util.xml.XMLStreamReaderFilter.next(Unknown Source)
at com.sun.xml.internal.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(Unknown Source)
... 20 more

It looks to me like something wrong with Postini.  I've uninstalled and re-installed GADS and still getting the same issue.

Steps to Reproduce: 
Re: google apps dir sync failing - [FATAL] [plugin.postini.PostiniPlugin] Unexpected exception attempting to add remote users pwust 5/22/12 7:02 AM
Having the same error message.

Apparently, being persistent and keeping on to run sync-cmd seems to resolve the issue over time with my setup. I was also playing with using option "--deletelimits" during troubleshooting my issue.

tail --follow=name sync-prod.log|grep -i "unable to create"

Unable to create 65 new users
Unable to create 53 new users
Unable to create 53 new users
Unable to create 46 new users
Unable to create 46 new users
Unable to create 40 new users
Unable to create 40 new users
Unable to create 34 new users
Unable to create 34 new users
Unable to create 28 new users
Unable to create 28 new users
Unable to create 28 new users
Unable to create 28 new users
Unable to create 16 new users
Unable to create 16 new users
Unable to create 10 new users
Unable to create 10 new users
Unable to create 5 new users

The last 5 users where not synced due to a different reason.

HTH, Patric

FrankM Forums-TC 5/22/12 9:41 AM <This message has been deleted.>
Re: google apps dir sync failing - [FATAL] [plugin.postini.PostiniPlugin] Unexpected exception attempting to add remote users pwust 5/25/12 4:54 AM
Me again.

I had raised a case with Postini support, and at the end the solution goes as follows:
This kind of error most likely comes from duplicate user entries when using a NONADDRESS PRIMARY KEY in your sync configuration.
Either you can get rid of the nonaddress primary key (for me this was not an option), or:
The best chance to find the root cause for the error is, running sync-cmd with --loglevel TRACE and determine exact OU and DN of the user objects of the error occuring.

In my particular case I had a problem with one of my Active Directory Global Catalog servers, which was not in sync with the rest. I had changed the GC server in my sync config, and then received these errors.

HTH, Patric