1 2 Previous Next 17 Replies Latest reply on May 19, 2017 4:50 AM by swabedoo

    DSM Sync failed

    konradBerlin Apprentice
      Hallo,

      nach einem (augenscheinlich) erfolgreichen Update unserer DSM Installation von Stand 2015.2 ---> 2016.2 (3651) funktioniert die Kommunikation mittels Agent nicht mehr. Wird er aufgerufen, erhalte ich die Fehlermeldung, dass die Synchronisation mit dem BLS fehlgeschlagen sei.

      Die Dienste auf dem DSM Server laufen normal und mehrere Reboots des Servers wie auch des Test-Clients sind erfolgt. Ich bin nun etwas verunsichert, da sich mehrere kleinere Verhaltensweisen auftaten:

      - der Agent hat sich nicht automatisch aktualisiert (nur auf dem DSM Server selbst, der auch den BLS beheimatet), sodass ich ihn händisch auf dem Test-Client aktualisiert habe
      - die Webadministration über Managementportal funktioniert auch nicht mehr

      Ein Konsistenzcheck der Installation ergab, dass alle Softwarekomponenten korrekt installiert wurden und auf einem aktuellen Stand sind. (7.3.2.3660)

      Was tun? Wo ansetzen? Fische gerade etwas im trüben.

      Einen Snapshot mit der laufenden 2015.1 Installation halte ich vor.
        • 1. Re: DSM Sync failed
          _Mel_ Master
          schau mal auf dem client in
          "C:\Program Files (x86)\Common Files\enteo\NiLogs\SyncLogs\PerformSync_*.log"

          falls der bls einen fehler gemeldet hat, dann sollte etwas in blsclientwebservice logfile auf dem bls stehen
          • 2. Re: DSM Sync failed
            konradBerlin Apprentice
            Korrekt, die Kommunikation zum MP funktioniert nicht:
            09:08.26.483  0 syncserv.dll  Extension C:\Program Files (x86)
            etinst\magntext\syncserv.dll has version 7.3.0.3181
            09:08.26.484  2 syncserv.dll  Caller PID is 6644
            09:08.26.485  1 FtlClient.dll  Selecting management point of type 'BLP' (Destination = 65535, Flags = 0xb)...
            09:08.26.485  0 FtlClient.dll    Creating Search Path from 66041 to 65535.
            09:08.26.485  0 FtlClient.dll    SearchPath: 66041,65535
            09:08.26.485  0 FtlClient.dll    Searching for management point at 66041 (0 Management Points).
            09:08.26.485  0 FtlClient.dll    Searching for management point at 65535 (1 Management Points).
            09:08.26.485  0 FtlClient.dll    Management point 66045 is marked as not available
            09:08.26.485  0 FtlClient.dll    Management point 66045 has rating 0.
            09:08.26.485  1 FtlClient.dll  Stopping search after container 65535, because failover is not allowed.
            09:08.26.485  1 FtlClient.dll  Found no usable management point, fallback to least recently tried management point 66045
            09:08.26.487  0 syncserv.dll  Using url 'http://A4DEPLOY:8080/mgmnt' for management point 66045
            09:08.26.491  0 syncserv.dll  Updating sync cache
            09:08.26.497  0 syncserv.dll  moving files...
            09:08.26.584  0 syncserv.dll  Logging 'SyncRequest' document now
            09:08.26.640  0 syncserv.dll  Document 'SyncRequest' has been logged into log file C:\Program Files (x86)\Common Files\enteo\NiLogs\SyncLogs\SyncRequest_0000001010.log
            09:08.26.641  0 syncserv.dll  Url is: http://A4DEPLOY:8080/mgmnt/blsClientManagement/ClientService.svc/Sync?qos=0

            Der Aufruf des genannten Links ist auch im Browser nicht möglich - es liegt wohl am IIS.

            BLS Log:
            2017-05-19 08:18:30,677 [521] ERROR Enteo.BlServer.ClientManagement - Exception in JSON-Call with JSON-Data:
            Enteo.BlServer.Common.BlServerException: The version of the DSM Client (7.3.0.3181) sent in the request does not match the version (7.3.2) of the Business Logic Server (BLS).
               at Enteo.BlServer.Orchestration.OrchestrationCallWrapper.EnsureClientVersionIsCorrect(OrchestrationCallWrapperActions actions, ClientInfo clientInfo, CallData callData)
               at Enteo.BlServer.Orchestration.OrchestrationCallWrapper..ctor(String callName, String callDetails, ICallEnvironment callEnvironment, ClientInfo clientInfo, ServerInfo serverInfo, OrchestrationCallWrapperActions actions, IDaCallScope daCallScope)
               at Enteo.BlServer.Orchestration.OrchestrationBase.HandleRequestInternal[TReply](String callName, String callDetails, TransactionHandling transactionHandling, ExecuteRequestDelegate`1 exec, Func`1 getClientInfo, Func`1 getRequestServerInfo, Func`2 getReplyServerInfo, OrchestrationCallWrapperActions actions)
               at Enteo.BlServer.Orchestration.OrchestrationBase.HandleRequestJson[TReply](String callName, JsonRequestBase request, TransactionHandling transactionHandling, OrchestrationCallWrapperActions actions, ExecuteRequestDelegate`1 executeRequest)
               at Enteo.BlServer.Orchestration.OrchestrationBase.HandleRequestJson[TReply](String callName, JsonRequestBase request, OrchestrationCallWrapperActions actions, ExecuteRequestDelegate`1 executeRequest)
               at Enteo.BlServer.Orchestration.ClientManagement.ClientManagementOrchestration.Sync(SyncRequest request, Action`1 calculatedSynchronizationDataAction)
               at Enteo.BlServer.WebService.ClientManagement.ClientService.<>c__DisplayClass1.b__0(IClientServiceOrchestration cs)
               at Enteo.BlServer.WebService.ClientManagement.ClientService.HandleRequest[TReply,TInterface](JsonRequestBase request, Func`2 exec)
               at Enteo.BlServer.Orchestration.ClientManagement.Json.JsonService.ProcessInternalWithValidation[TRequest,TReply](Stream s, Func`2 handler, Action`1 postProcessReply, Action handleServiceNotAvailable, Func`2 extendTrac


            Komisch, wieso gibt es den Aufruf nach Version 3181? Im Zuge der Updates sollte sich das doch aktualisiert haben?
            • 3. Re: DSM Sync failed
              konradBerlin Apprentice
              Nachtrag: Auf dem Test-Client wurde der DSM Agent deinstalliert und versucht, händisch zu reinstallieren. Dies schlug ebenfalls fehl:

              09:39:13.503 1   NiCfgPrv: RegValue 'ProgramFilesDir' resolved as 'C:\Program Files (x86)'
              09:39:13.503 1   NiCfgPrv: RegValue 'ProgramFilesDir' resolved as 'C:\Program Files (x86)'
              09:39:13.503 2  NiCfgPrv: No current Management Point with 'SisService'
              09:39:13.503 2  NiCfgPrv: Current Management Point ID with 'SisService': 0
              09:39:13.503 E  Warning (Module:Main, Severity:0x03): Failed to get the Management Point with a SiS installed!
              09:39:13.503 2  Current user is not local admin, and no Management Point with SIS was found. the client installation can't be continued!
              09:39:13.503 1  > Action 'Client Installer' completed with 1 warnings (Action took 453 ms.)

              Nachtrag2:

              Installationsscript als Admin gestartet, Installation des Agent 3660 erfolgreich. Fehlermeldung bezüglich Sync mit BLS bleibt aber bestehen...
              • 4. Re: DSM Sync failed
                _Mel_ Master
                die meldung "The version of the DSM Client (7.3.0.3181) sent in the request does not match the version (7.3.2) of the Business Logic Server (BLS)" ist doch recht deutlich.
                das ist ein veralteter client.

                d.h. entweder das depot das der client verwendet ist nicht aktuell oder der client hat ein updateproblem.
                • 5. Re: DSM Sync failed
                  konradBerlin Apprentice

                  die meldung "The version of the DSM Client (7.3.0.3181) sent in the request does not match the version (7.3.2) of the Business Logic Server (BLS)" ist doch recht deutlich.
                  das ist ein veralteter client.

                  d.h. entweder das depot das der client verwendet ist nicht aktuell oder der client hat ein updateproblem.



                  Habe andere Rechner ebenfalls geprüft, diese erhalten ebenfalls keinen neuen Agent (dort läuft ebenfalls noch der alte 7.3.0.3181) und bringen die Fehlermeldung bezüglich Sync mit BLS.
                  • 6. Re: DSM Sync failed
                    _Mel_ Master
                    sind die dateien auf dem depot den aktuell ?
                    falls nein: depot wurde beim update nicht aktualisiert -> nachholen
                    falls ja: ist auf dem depot unter "$SysDb$\Packages\ClientBinaries32bit\rev" eine aktuelle version ? falls nein: prepare client binaries nachholen
                    • 7. Re: DSM Sync failed
                      konradBerlin Apprentice

                      sind die dateien auf dem depot den aktuell ?
                      falls nein: depot wurde beim update nicht aktualisiert -> nachholen
                      falls ja: ist auf dem depot unter "$SysDb$\Packages\ClientBinaries32bit\rev" eine aktuelle version ? falls nein: prepare client binaries nachholen




                      Beides gecheckt, aktuelle rev ist vorhanden und liegt bereit.
                      • 8. Re: DSM Sync failed
                        _Mel_ Master
                        ok, dann mußt du auf dem client unter nilogs\clientservices im updatecheckdownload logfile schauen.
                        da mußt du darauf achten eines anzusehen in dem der client nicht nur die ncp updaten will.

                        da sollte am anfang stehen
                        03:50.01.310  0 csmanext.dll  Calling Process command line is '"C:\Program Files (x86)\NetInst\mgmtagnt.exe" /run=ersupext.dll'
                        03:50.01.310  2 csmanext.dll  Flags entitle to the following actions:
                        03:50.01.310  2 csmanext.dll    Checking client files
                        03:50.01.310  2 csmanext.dll    Checking program files

                        und weiter unten geht er dann seine ganzen checks durch. z.B.
                        03:50.01.626  1 csmanext.dll      File %ProgramFilesDir%\NetInst\magntext\syncserv.dll must exist, date: 08.5.2017 00:38:34
                        • 9. Re: DSM Sync failed
                          konradBerlin Apprentice

                          ok, dann mußt du auf dem client unter nilogs\clientservices im updatecheckdownload logfile schauen.
                          da mußt du darauf achten eines anzusehen in dem der client nicht nur die ncp updaten will.

                          da sollte am anfang stehen
                          03:50.01.310  0 csmanext.dll  Calling Process command line is '"C:\Program Files (x86)\NetInst\mgmtagnt.exe" /run=ersupext.dll'
                          03:50.01.310  2 csmanext.dll  Flags entitle to the following actions:
                          03:50.01.310  2 csmanext.dll    Checking client files
                          03:50.01.310  2 csmanext.dll    Checking program files

                          und weiter unten geht er dann seine ganzen checks durch. z.B.
                          03:50.01.626  1 csmanext.dll      File %ProgramFilesDir%\NetInst\magntext\syncserv.dll must exist, date: 08.5.2017 00:38:34



                          Client geprüft, dies ist der Inhalt der aktuellsten Log:


                          09:48.54.376  0 csmanext.dll  Extension C:\Program Files (x86)\NetInst\magntext\csmanext.dll has version 7.3.2.3660
                          09:48.54.378  0 csmanext.dll  Calling Process is 'C:\Program Files (x86)\NetInst\csmasync.exe'
                          09:48.54.378  0 csmanext.dll  Calling Process command line is 'csmasync.exe 00000203'
                          09:48.54.378  0 csmanext.dll  Calling Process PID is 5260
                          09:48.54.378  0 csmanext.dll  Calling Thread TID is 4108
                          09:48.54.378  2 csmanext.dll  Received UpdateCheck request with binding ncalrpc:E6ZACHARY.
                          09:48.54.378  0 csmanext.dll  UpdateCheckDownload called with flags = 0x00000003
                          09:48.54.378  2 csmanext.dll  Flags entitle to the following actions:
                          09:48.54.378  2 csmanext.dll    Using cached result
                          09:48.54.378  2 csmanext.dll    Checking NCP
                          09:48.54.378  0 csmanext.dll  Attempting to get current location via ICDB
                          09:48.54.378  0 csmanext.dll  Retrieved location. Site is 66041, server is 66042, network throughput is 3883
                          09:48.54.380  1 csmanext.dll  Failed to parse for locale in parameter string '-t 4294967295' passed to CSM
                          09:48.54.380  0 csmanext.dll  The csactext timeout passed is infinite
                          09:48.54.380  0 csmanext.dll  Resolving server via ICDB
                          09:48.54.381  0 csmanext.dll  Resolving site via ICDB
                          09:48.54.386  1 csmanext.dll  Using FPS to download client binaries.
                          09:48.54.386  0 csmanext.dll  Querying ICDB for auto update enabled option
                          09:48.54.386  0 csmanext.dll  We now determine if a cached result within the last hour is there
                          09:48.54.386  1 csmanext.dll  Last update check was 19.5.2017 09:48:43 -> just checking NCP
                          09:48.54.386  2 csmanext.dll  Flags entitle to the following actions:
                          09:48.54.386  2 csmanext.dll    Checking NCP
                          09:48.54.387  2 csmanext.dll  Only NCP should be checked, we do this only if 5 minutes since the last check have elapsed
                          09:48.54.387  1 csmanext.dll  Last NCP update check was 19.5.2017 09:48:37 -> we do not check or update anything
                          09:48.54.387  0 csmanext.dll  Flags are zero, quitting
                          09:48.54.387  : End Of Logfile

                          Und hier die Log von einem Client, auf dem der nicht aktualisierte Agent läuft:

                          11:12.13.857  :
                          11:12.13.857  :

                          11:12.13.856  0 csmanext.dll  Extension C:\Program Files (x86)
                          etinst\magntext\csmanext.dll has version 7.3.0.3181
                          11:12.13.857  0 csmanext.dll  Calling Process is 'C:\Program Files (x86)
                          etinst\csmasync.exe'
                          11:12.13.857  0 csmanext.dll  Calling Process command line is 'csmasync.exe 00000203'
                          11:12.13.857  0 csmanext.dll  Calling Process PID is 11548
                          11:12.13.857  0 csmanext.dll  Calling Thread TID is 13084
                          11:12.13.857  2 csmanext.dll  Received UpdateCheck request with binding ncalrpc:E6ISAMU.
                          11:12.13.858  0 csmanext.dll  UpdateCheckDownload called with flags = 0x00000003
                          11:12.13.858  2 csmanext.dll  Flags entitle to the following actions:
                          11:12.13.858  2 csmanext.dll    Using cached result
                          11:12.13.858  2 csmanext.dll    Checking NCP
                          11:12.13.858  0 csmanext.dll  Attempting to get current location via ICDB
                          11:12.13.858  0 csmanext.dll  Retrieved location. Site is 66041, server is 66042, network throughput is 4550
                          11:12.13.859  1 csmanext.dll  Failed to parse for locale in parameter string '-t 4294967295' passed to CSM
                          11:12.13.859  0 csmanext.dll  The csactext timeout passed is infinite
                          11:12.13.860  0 csmanext.dll  Resolving server via ICDB
                          11:12.13.860  0 csmanext.dll  Resolving site via ICDB
                          11:12.13.864  1 csmanext.dll  Using FPS to download client binaries.
                          11:12.13.865  0 csmanext.dll  Querying ICDB for auto update enabled option
                          11:12.13.865  0 csmanext.dll  We now determine if a cached result within the last hour is there
                          11:12.13.865  2 csmanext.dll  Only NCP should be checked, we do this only if 5 minutes since the last check have elapsed
                          11:12.13.865  1 csmanext.dll  Last NCP update check was 19.5.2017 11:11:49 -> we do not check or update anything
                          11:12.13.865  0 csmanext.dll  Flags are zero, quitting
                          11:12.13.866  : End Of Logfile
                          • 10. Re: DSM Sync failed
                            swabedoo Apprentice
                            Hallo konradBerlin,

                            das sind m.E. die falschen Logfiles, da wird nämlich nur die NCP geprüft (siehe <===):

                            09:48.54.378 2 csmanext.dll Flags entitle to the following actions:
                            09:48.54.378 2 csmanext.dll Using cached result
                            09:48.54.378 2 csmanext.dll Checking NCP  <===

                            Es sollte aber drin stehen:

                            03:50.01.310 2 csmanext.dll Flags entitle to the following actions:
                            03:50.01.310 2 csmanext.dll Checking client files     <===
                            03:50.01.310 2 csmanext.dll Checking program files <===

                            Viele Grüße,
                            swabedoo
                            • 11. Re: DSM Sync failed
                              _Mel_ Master
                              das update wird vom runtime service angestoßen, darum hilft es auch nachzusehen wer der aufrufer ist:
                              03:50.01.310 0 csmanext.dll Calling Process command line is '"C:\Program Files (x86)\NetInst\mgmtagnt.exe" /run=ersupext.dll'
                              <- das ist der runtime service

                              du kannst auch mal den runtime service durchstarten, danach sollte eines der aktuellen logfiles das mit dem update sein
                              • 12. Re: DSM Sync failed
                                konradBerlin Apprentice

                                das update wird vom runtime service angestoßen, darum hilft es auch nachzusehen wer der aufrufer ist:
                                03:50.01.310 0 csmanext.dll Calling Process command line is '"C:\Program Files (x86)\NetInst\mgmtagnt.exe" /run=ersupext.dll'
                                <- das ist der runtime service

                                du kannst auch mal den runtime service durchstarten, danach sollte eines der aktuellen logfiles das mit dem update sein



                                Habe ich eben mal gemacht, anbei die Log updatecheckdownload1921 und 1922.

                                Auszug aus 1921:
                                10:20.01.947  0 csmanext.dll  Extension C:\Program Files (x86)\NetInst\magntext\csmanext.dll has version 7.3.2.3660
                                10:20.01.948  0 csmanext.dll  Calling Process is 'C:\Program Files (x86)\NetInst\mgmtagnt.exe'
                                10:20.01.948  0 csmanext.dll  Calling Process command line is '"C:\Program Files (x86)\NetInst\mgmtagnt.exe" /run=ersupext.dll'
                                10:20.01.948  0 csmanext.dll  Calling Process PID is 4108
                                10:20.01.948  0 csmanext.dll  Calling Thread TID is 4340
                                10:20.01.948  2 csmanext.dll  Received UpdateCheck request with binding ncalrpc:E6ZACHARY.
                                10:20.01.948  0 csmanext.dll  UpdateCheckDownload called with flags = 0x0000200c
                                10:20.01.948  2 csmanext.dll  Flags entitle to the following actions:
                                10:20.01.948  2 csmanext.dll    Checking client files
                                10:20.01.948  2 csmanext.dll    Checking program files
                                10:20.01.948  2 csmanext.dll    Using the default timeout as specified in the NCP
                                10:20.01.948  0 csmanext.dll  Attempting to get current location via ICDB
                                10:20.01.949  0 csmanext.dll  Retrieved location. Site is 66041, server is 66042, network throughput is 4102
                                10:20.01.951  1 csmanext.dll  Failed to parse for locale in parameter string '-t 4294967295' passed to CSM
                                10:20.01.951  0 csmanext.dll  The csactext timeout passed is infinite
                                10:20.01.951  0 csmanext.dll  Resolving server via ICDB
                                10:20.01.952  0 csmanext.dll  Resolving site via ICDB
                                10:20.01.953  0 csmanext.dll  Successfully retrieved the default activation service timeout: 180 minutes
                                10:20.01.958  1 csmanext.dll  Using FPS to download client binaries.
                                10:20.01.958  0 csmanext.dll  Querying ICDB for auto update enabled option
                                10:20.01.958  2 csmanext.dll  We ignore any cached result
                                10:20.01.958  0 csmanext.dll  Determining if current server is in program update mode
                                10:20.01.968  1 FPS.dll 
                                10:20.01.968  1 FPS.dll  --------------- FpsCreateFileSystemProvider interface called ---------------
                                10:20.01.968  0 FPS.dll  Parameters:
                                10:20.01.968  0 FPS.dll  Base URL: \\A4DEPLOY\DSM$\
                                10:20.01.968  0 FPS.dll  Authentication mode: RoleBasedAuth, Role Depot
                                10:20.01.968  0 FPS.dll  Provider with role based authentication requested. Container ID: '66042'. Role: 'Depot' (ID 8)
                                10:20.01.968  0 FPS.dll  Checking if path '\\?\UNC\A4DEPLOY\DSM$\' is on the local machine...
                                10:20.01.968  0 FPS.dll    ...no
                                10:20.01.982  0 nwcmclnt.dll  Role based login succeeded with SHA\service.dsm
                                10:20.01.982  1 FPS.dll  Role based login to remote resource with role 'Depot' for container '66042' succeeded.
                                10:20.01.982  1 FPS.dll  --------------- FpsCreateFileSystemProvider finished ---------------
                                10:20.01.982  1 FPS.dll 
                                10:20.02.020  0 nwcmclnt.dll  Logout Nwcm succeeded with SHA\service.dsm
                                10:20.02.020  0 FPS.dll  Successfully logged out from remote resource.
                                10:20.02.020  0 csmanext.dll  Current server is not in program update mode
                                10:20.02.020  0 csmanext.dll  Create CSMDS manager
                                10:20.02.024  1 csmanext.dll  CRC of packages will be computed.
                                10:20.02.025  1 csmanext.dll  Updating client NCPs using protocol SMB
                                10:20.02.034  1 FPS.dll 
                                10:20.02.034  1 FPS.dll  --------------- FpsOpenPseudoFilePackage interface called ---------------
                                10:20.02.034  0 FPS.dll  Server: \\A4DEPLOY\DSM$\
                                10:20.02.034  0 FPS.dll  Repository directory: (null)
                                10:20.02.034  0 FPS.dll  Project directory: (null)
                                10:20.02.034  0 FPS.dll  Pseudo package ID: Ncp
                                10:20.02.034  0 FPS.dll  Additional ID:
                                10:20.02.034  0 FPS.dll  Open mode: OpenExisting
                                10:20.02.034  0 FPS.dll  Authentication mode: RoleBasedAuth
                                10:20.02.034  2 FPS.dll  Opening pseudo file package 'Ncp' on server '\\A4DEPLOY\DSM$\'.
                                10:20.02.034  2 FPS.dll  Open mode is: OpenExisting.
                                10:20.02.034  0 FPS.dll  Provider with role based authentication requested. Container ID: '66042'. Role: 'Depot' (ID 8)
                                10:20.02.034  0 FPS.dll  Checking if path '\\?\UNC\A4DEPLOY\DSM$\' is on the local machine...
                                10:20.02.034  0 FPS.dll    ...no
                                10:20.02.048  0 nwcmclnt.dll  Role based login succeeded with SHA\service.dsm
                                10:20.02.049  1 FPS.dll  Role based login to remote resource with role 'Depot' for container '66042' succeeded.
                                10:20.02.049  0 FPS.dll  Creating temporary FPI for NCP...
                                10:20.02.075  0 FPS.dll  FPI for NCP created.
                                10:20.02.075  0 FPS.dll  File package is opened.
                                10:20.02.075  0 FPS.dll  Package handle: 15B1800
                                10:20.02.075  1 FPS.dll  --------------- FpsOpenPseudoFilePackage finished ---------------
                                10:20.02.075  1 FPS.dll 
                                10:20.02.076  1 FPS.dll 
                                10:20.02.076  1 FPS.dll  --------------- FpsOpenPseudoFilePackage interface called ---------------
                                10:20.02.076  0 FPS.dll  Server: cache:\\
                                10:20.02.076  0 FPS.dll  Repository directory: C:\Program Files (x86)\Common Files\enteo\RepositoryCache\system\pseudo\Ncp\
                                10:20.02.076  0 FPS.dll  Project directory: C:\Program Files (x86)\Common Files\enteo\RepositoryCache\system\pseudo\Ncp\
                                10:20.02.076  0 FPS.dll  Pseudo package ID: Ncp
                                10:20.02.076  0 FPS.dll  Additional ID:
                                10:20.02.076  0 FPS.dll  Open mode: OpenExisting
                                10:20.02.076  0 FPS.dll  Authentication mode: NoAuth
                                10:20.02.076  2 FPS.dll  Opening pseudo file package 'Ncp' on server 'cache:\\' from 'C:\Program Files (x86)\Common Files\enteo\RepositoryCache\system\pseudo\Ncp\'.
                                10:20.02.076  2 FPS.dll  Open mode is: OpenExisting.
                                10:20.02.076  0 FPS.dll  Provider with no authentication requested.
                                10:20.02.076  0 FPS.dll  Creating temporary FPI for NCP...
                                10:20.02.076  0 FPS.dll  FPI for NCP created.
                                10:20.02.076  0 FPS.dll  File package is opened.
                                10:20.02.076  0 FPS.dll  Package handle: 15B1288
                                10:20.02.076  1 FPS.dll  --------------- FpsOpenPseudoFilePackage finished ---------------
                                10:20.02.076  1 FPS.dll 
                                10:20.02.078  0 FPS.dll  'NiCfgSrv.ncp': File size: 44213 bytes, date: 19.05.2017 - 07:22:00, version: 0.0.0.0
                                10:20.02.079  0 FPS.dll  'NiCfgSrv.ncp': File size: 44213 bytes, date: 19.05.2017 - 07:22:00, version: 0.0.0.0
                                10:20.02.079  0 FPS.dll  'NiCfgLcl.ncp': File size: 21647 bytes, date: 19.05.2017 - 07:22:00, version: 0.0.0.0
                                10:20.02.079  0 FPS.dll  'NiCfgLcl.ncp': File size: 21647 bytes, date: 19.05.2017 - 07:22:00, version: 0.0.0.0
                                10:20.02.079  0 FPSClnt.dll  Package is requested as a system package.
                                10:20.02.079  0 FPS.dll  Compressible = 0
                                10:20.02.079  0 FPSClnt.dll  Preferring uncompressed transfer of package.
                                10:20.02.079  0 FPS.dll  Package can be accessed from the cache directly.
                                10:20.02.079  0 FPS.dll  Package needs to be copied into cache: no
                                10:20.02.079  0 FPSClnt.dll  No cache needed. Returning server path.
                                10:20.02.079  0 FPS.dll  PackagePath = \\?\C:\Program Files (x86)\Common Files\enteo\RepositoryCache\system\pseudo\Ncp\
                                10:20.02.079  1 csmanext.dll  File package 'Ncp' is up to date in the cache in 'C:\Program Files (x86)\Common Files\enteo\RepositoryCache\system\pseudo\Ncp\'. No update needed.
                                10:20.02.079  2 FPS.dll  Closing the file package '\\?\C:\Program Files (x86)\Common Files\enteo\RepositoryCache\system\pseudo\Ncp\'.
                                10:20.02.079  2 FPS.dll  Closing the file package '\\?\UNC\A4DEPLOY\DSM$\'.


                                Logfile 1922:


                                10:20.13.345  0 csmanext.dll  Extension C:\Program Files (x86)\NetInst\magntext\csmanext.dll has version 7.3.2.3660
                                10:20.13.347  0 csmanext.dll  Calling Process is 'C:\Program Files (x86)\NetInst\NiInst32.exe'
                                10:20.13.347  0 csmanext.dll  Calling Process command line is 'NiInst32.exe /SERVICE /Trigger:Polling /NetworkAccessToken:1236'
                                10:20.13.347  0 csmanext.dll  Calling Process PID is 8612
                                10:20.13.347  0 csmanext.dll  Calling Thread TID is 7508
                                10:20.13.347  2 csmanext.dll  Received UpdateCheck request with binding ncalrpc:E6ZACHARY.
                                10:20.13.347  0 csmanext.dll  UpdateCheckDownload called with flags = 0x00000003
                                10:20.13.347  2 csmanext.dll  Flags entitle to the following actions:
                                10:20.13.347  2 csmanext.dll    Using cached result
                                10:20.13.347  2 csmanext.dll    Checking NCP
                                10:20.13.347  0 csmanext.dll  Attempting to get current location via ICDB
                                10:20.13.347  0 csmanext.dll  Retrieved location. Site is 66041, server is 66042, network throughput is 4102
                                10:20.13.349  1 csmanext.dll  Failed to parse for locale in parameter string '-t 4294967295' passed to CSM
                                10:20.13.349  0 csmanext.dll  The csactext timeout passed is infinite
                                10:20.13.349  0 csmanext.dll  Resolving server via ICDB
                                10:20.13.350  0 csmanext.dll  Resolving site via ICDB
                                10:20.13.355  1 csmanext.dll  Using FPS to download client binaries.
                                10:20.13.355  0 csmanext.dll  Querying ICDB for auto update enabled option
                                10:20.13.355  0 csmanext.dll  We now determine if a cached result within the last hour is there
                                10:20.13.356  1 csmanext.dll  Last update check was 23.5.2017 10:20:11 -> just checking NCP
                                10:20.13.356  2 csmanext.dll  Flags entitle to the following actions:
                                10:20.13.356  2 csmanext.dll    Checking NCP
                                10:20.13.356  2 csmanext.dll  Only NCP should be checked, we do this only if 5 minutes since the last check have elapsed
                                10:20.13.356  1 csmanext.dll  Last NCP update check was 23.5.2017 10:20:02 -> we do not check or update anything
                                10:20.13.356  0 csmanext.dll  Flags are zero, quitting
                                10:20.13.356  : End Of Logfile
                                • 13. Re: DSM Sync failed
                                  _Mel_ Master
                                  das erste logfile ist das interessante, nur kommt der interessante teil weiter unten.
                                  such mal nach
                                  Action 'Check desired state of NetInstall Full Client vs. current state' completed
                                  • 14. Re: DSM Sync failed
                                    konradBerlin Apprentice

                                    das erste logfile ist das interessante, nur kommt der interessante teil weiter unten.
                                    such mal nach
                                    Action 'Check desired state of NetInstall Full Client vs. current state' completed



                                    Fehlermeldung gefunden:
                                    11:14.40.810  1 FPS.dll  --------------- FpsOpenPseudoFilePackage finished ---------------
                                    11:14.40.810  1 FPS.dll 
                                    11:14.40.810  0 FPS.dll  'SSI\ClientInstaller\DSMClient.msi': File size: 29859840 bytes, date: 03.02.2017 - 23:44:48, version: 0.0.0.0
                                    11:14.40.811  0 FPS.dll  'SSI\ClientInstaller\DSMClient.msi': File size: 29859840 bytes, date: 03.02.2017 - 23:44:48, version: 0.0.0.0
                                    11:14.40.811  0 FPSClnt.dll  Package is requested as a system package.
                                    11:14.40.811  0 FPS.dll  Compressible = 0
                                    11:14.40.811  0 FPSClnt.dll  Preferring uncompressed transfer of package.
                                    11:14.40.811  0 FPS.dll  Package can be accessed from the cache directly.
                                    11:14.40.811  0 FPS.dll  Package needs to be copied into cache: no
                                    11:14.40.811  0 FPSClnt.dll  No cache needed. Returning server path.
                                    11:14.40.811  0 FPS.dll  PackagePath = \\?\C:\Program Files (x86)\Common Files\enteo\RepositoryCache\system\pseudo\ClientInstaller\
                                    11:14.40.811  1 csmanext.dll  File package 'ClientInstaller' is up to date in the cache in 'C:\Program Files (x86)\Common Files\enteo\RepositoryCache\system\pseudo\ClientInstaller\'. No update needed.
                                    11:14.40.811  2 FPS.dll  Closing the file package '\\?\C:\Program Files (x86)\Common Files\enteo\RepositoryCache\system\pseudo\ClientInstaller\'.
                                    11:14.40.811  2 FPS.dll  Closing the file package '\\?\UNC\A4DEPLOY\DSM$\'.
                                    11:14.40.811  0 nwcmclnt.dll  Logout Nwcm succeeded with SHA\service.dsm
                                    11:14.40.811  0 FPS.dll  Successfully logged out from remote resource.
                                    11:14.41.161  1 csmanext.dll  Installed DSM MSI Client version: 7.3.3188
                                    11:15.01.924  2 trustchk.dll  Validating digital signature of 'C:\Program Files (x86)\Common Files\enteo\RepositoryCache\system\pseudo\ClientInstaller\SSI\ClientInstaller\DSMClient.msi' failed after 100 retries with error code 5 (0xe001000e)
                                    11:15.01.924  E Warning (Module:mgmtagnt.exe, Severity:0x03): csmanext.dll  Untrusted MSI package: C:\Program Files (x86)\Common Files\enteo\RepositoryCache\system\pseudo\ClientInstaller\SSI\ClientInstaller\DSMClient.msi
                                    11:15.01.924  E Warning (Module:mgmtagnt.exe, Severity:0x03): csmanext.dll  Failed to update DSM MSI Client
                                    Access is denied. (0x00000005)
                                    11:15.01.969  E Warning (Module:mgmtagnt.exe, Severity:0x03): csmanext.dll  DSM Client Update (0x60080334)
                                    DSM Client Update (0x60080334)
                                    11:15.01.969  : End Of Logfile
                                    1 2 Previous Next