Quantcast
Channel: Ivanti User Community : Discussion List - All Communities
Viewing all articles
Browse latest Browse all 15294

Client Sync schlägt fehl - "Bad document format"

$
0
0

Hallo Zusammen,

 

vielleicht kann mir jemand bei diesem Fehlerbild weiterhelfen. Wir hatten bis dato einige wenige Fälle dieses Sync Problems, aber keine alternative Lösung, als

das DSM Objekt komplett neu anzulegen und eine Neuinstallation des Rechners vorzunehmen.

 

Der besagte Client lief bis vor ein paar Tagen völlig unaufällig und erhielt alle Policies. Nun schlägt der Sync fehl, weil offenbar das Sync Archiv nicht korrekt gelesen werden kann.

 

Folgende Lösungsversuche brachten keinen Erfolg:

 

- Löschen des Sync Ordners auf dem Client

 

============================================================================================

Eintäge aus dem NISRV32.log

________________________________________________________________________________________________

04:19:40.634 2     Retrieving login information from xnidNT32.dll (NT-Server, LAN-Manager, LAN-Server)

04:19:42.996 2     WkstaGroups :

04:19:43.030 2  SWMSRT: Initializing SWMSRunTimeMgr

04:19:47.093 2    SWMSRT: Could not get all needed ClientObjects!

04:19:47.094 2   SWMSRT: Performing client sync for computer '226973' and user '302' with QoS level 'Polling'

04:20:18.827 E   Warning (Module:SWMSClntLib, Severity:0x03): Failed to synchronize with BLS

Bad document format. (0xe0080711)

04:20:18.828 E   Warning (Module:SWMSRT, Severity:0x03): Client sync () failed [-536344815]

04:20:18.831 E   Warning (Module:SWMSRT, Severity:0x03): ClientSync failed with error code 3758622481

Bad document format. (0xe0080711)

04:20:18.833 2   SWMSRT: Client sync for computer '226973' and user '302' (QoS level 'Polling') failed with 'Bad document format. (0xe0080711)' (3758622481)

04:20:18.833 E   Warning (Module:SWMSRT, Severity:0x03): The initialize synchronization failed

04:20:18.835 E   Warning (Module:Main, Severity:0x03): Initialization of TargetProvider SWMSTP failed!

________________________________________________________________________________________________

Einträge aus dem PerformSync_AGG.log

 

09:44.23.030  0 syncserv.dll    :"NI","Version":"7.3.0.3181"},"LocalTime":"2017-07-12T09:44:23+02:00","ServerInfo":{"CmdbGuid":"{45CAD71B-E4F9-4918-9C2E-04E9129DDD3C}","MetaModelVers

09:44.23.030  0 syncserv.dll    ion":0},"UserCulture":"en"},"UserRevisions":{}}

09:44.23.046  2 CMSClntLib.dll  Calling 'http://XXXX.XXX.ads.XXX:8080/blsClientManagement/ClientService.svc/Sync?qos=0'

09:44.23.623  0 HttpSupport.dll  Request was compressed by 82 percent. Compressed size 15920 bytes. Uncompressed size 84147 bytes

09:44.23.623  2 CMSClntLib.dll  Webservice call suceeded with status code 200

09:44.23.623  0 syncserv.dll  HTTP status of sync request is 200

09:44.23.638  0 syncserv.dll  Archiver command line is nisyncar.exe "C:\Program Files (x86)\Common Files\enteo\sync\archive" "C:\Windows\Temp\JARC7A7.tmp" 25920000000000 sync_ SyncLogs\nisyncar

09:44.23.638  0 syncserv.dll  Successfully launched archiver process

09:44.23.638  2 syncserv.dll  The response from the server is not a valid document

 

Vorab vielen Dank für jede Unterstützung!

 

Schönen Gruß

 

Carsten


Viewing all articles
Browse latest Browse all 15294

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>