Benutzer mit den meisten Antworten
Error 87 - advertise program with a task

Frage
-
Hello,
i have an annoying problem. In our network we use a SCCM 2007 R2 Server to deploy software. We use tasks to deploy the software to be more flexible. normally all software which is advertised, installs smooth. But sometimes we get an error 87, independent of the software which is advertised. The advertisement restarts every 15 minutes. I deleted the membership of the CLient from the Collection which had the advertisement with the error, but nothing happened. Just as well new advertisements dont function. The only way i could resolve the error is, to create a new guid for the client. But that could not be a good solution, because this error appears from time to time on different clients.
I have attached the sccm log for this error. I hope someone can help me.
thanking you in anticipation.
Executing program in Admin context execmgr 15.11.2010 11:32:03 4884 (0x1314)
Execution Manager timer has been fired. execmgr 15.11.2010 11:32:03 4564 (0x11D4)
Execution Request for package FFM001CA program * state change from Running to NotifyExecution execmgr 15.11.2010 11:32:03 4884 (0x1314)
Executing program as a task sequence. execmgr 15.11.2010 11:32:03 4884 (0x1314)
Successfully prepared command line "C:\WINNT\system32\CCM\TSLauncher.exe" execmgr 15.11.2010 11:32:03 4884 (0x1314)
Command line = "C:\WINNT\system32\CCM\TSLauncher.exe", Working Directory = C:\WINNT\system32\ execmgr 15.11.2010 11:32:03 4884 (0x1314)
Created Process for the passed command line execmgr 15.11.2010 11:32:03 4884 (0x1314)
Raising event:
[SMS_CodePage(850), SMS_LocaleID(1031)]
instance of SoftDistProgramStartedEvent
{
AdvertisementId = "FFM201D2";
ClientID = "GUID:8890461D-A175-4947-A014-82B5433ECE1E";
CommandLine = "\"C:\\WINNT\\system32\\CCM\\TSLauncher.exe\"";
DateTime = "20101115103203.645000+000";
MachineName = "xxx";
PackageName = "FFM001CA";
ProcessID = 392;
ProgramName = "*";
SiteCode = "FFM";
ThreadID = 4884;
UserContext = "NT-AUTORITÄT\\SYSTEM";
WorkingDirectory = "C:\\WINNT\\system32\\";
};
execmgr 15.11.2010 11:32:03 4884 (0x1314)
Raised Program Started Event for Ad:FFM201D2, Package:FFM001CA, Program: * execmgr 15.11.2010 11:32:03 4884 (0x1314)
Program exit code 87 execmgr 15.11.2010 11:32:04 4564 (0x11D4)
Looking for MIF file to get program status execmgr 15.11.2010 11:32:04 4564 (0x11D4)
Script for Package:FFM001CA, Program: * failed with exit code 87 execmgr 15.11.2010 11:32:04 4564 (0x11D4)
Raising event:
[SMS_CodePage(850), SMS_LocaleID(1031)]
instance of SoftDistWarningProgramErrorEvent
{
AdvertisementId = "FFM201D2";
ClientID = "GUID:8890461D-A175-4947-A014-82B5433ECE1E";
DateTime = "20101115103204.083000+000";
ExitCode = "87";
MachineName = "xxx";
PackageName = "FFM001CA";
ProcessID = 392;
ProgramName = "*";
SiteCode = "FFM";
ThreadID = 4564;
UserContext = "NT-AUTORITÄT\\SYSTEM";
};
execmgr 15.11.2010 11:32:04 4564 (0x11D4)
Raised Program Error Event for Ad:FFM201D2, Package:FFM001CA, Program: * execmgr 15.11.2010 11:32:04 4564 (0x11D4)
Execution is complete for program *. The exit code is 87, the execution status is FailureRetry execmgr 15.11.2010 11:32:04 3908 (0x0F44)
Non fatal execution error 0x80008100 encountered for program * execmgr 15.11.2010 11:32:04 3908 (0x0F44)
Program * has been tried 1 times, will retry later execmgr 15.11.2010 11:32:04 3908 (0x0F44)
Execution Request for package FFM001CA program * state change from Running to WaitingRetry execmgr 15.11.2010 11:32:04 3908 (0x0F44)
Antworten
-
Probiere mal folgendes: stoppe den ConfigMgr Client, entferne die SMS-Zertifikate auf dem Client und starte den Client wieder. ClientIDManagerStartUp.log beobachten, warten bis der Client registriert ist, Policies aktualisieren, TS nochmal starten.
- Als Antwort vorgeschlagen TorstenMMVP, Editor Dienstag, 23. November 2010 14:45
- Als Antwort markiert Andrei TalmaciuModerator Dienstag, 30. November 2010 12:49
Alle Antworten
-
Ist denn bei dem Program auch sicher "Allow this program to be installed from the Install Software task sequence without being advertised" ausgewählt (http://technet.microsoft.com/en-us/library/bb680380.aspx)? Dem würde natürlich entgegensprechen, dass es bei Clients mit neuer GUID dann funktioniert. Was steht denn noch im smsts.log?
-
Danke schonmal für die schnelle Antwort. Ja die Einstellung Allow this program to be installed from the Install Software task sequence without being advertised ist gesetzt. Nachfolgend ein Auszug aus dem smsts.log:
Successfully finalized logs to SMS client log directory from C:\WINNT\system32\CCM\Logs TSManager 08.10.2010 11:56:14 8064 (0x1F80)
Resuming SMS Components TSManager 08.10.2010 11:56:14 8064 (0x1F80)
Waiting for CcmExec service to be fully operational TSManager 08.10.2010 11:56:14 8064 (0x1F80)
CcmExec service is up and fully operational TSManager 08.10.2010 11:56:14 8064 (0x1F80)
Resume for CCM component SoftwareDistribution requested TSManager 08.10.2010 11:56:14 8064 (0x1F80)
Attempting to release request using {A4E5AAAA-2A09-4115-BE9B-02DB167209C5} TSManager 08.10.2010 11:56:14 8064 (0x1F80)
ReleaseRequest succeeded TSManager 08.10.2010 11:56:14 8064 (0x1F80)
Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\SoftwareUpdates. Error code 0x80070002 TSManager 08.10.2010 11:56:14 8064 (0x1F80)
Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\System Health Agent. Error code 0x80070002 TSManager 08.10.2010 11:56:14 8064 (0x1F80)
Stopping Task Sequence Manager service TSManager 08.10.2010 11:56:14 8064 (0x1F80)
Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created TSLauncher 12.11.2010 15:17:36 2716 (0x0A9C)
Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created TSLauncher 12.11.2010 15:17:36 2716 (0x0A9C)
GetPrivateProfileString() failed to get SMS Client GUID from file. Code 0x00000000 TSLauncher 12.11.2010 15:17:36 2716 (0x0A9C)
Error getting package location and access account information. Code 0x80070057 TSLauncher 12.11.2010 15:17:36 2716 (0x0A9C)
Error initializing TS environment. Code 0x80070057 TSLauncher 12.11.2010 15:17:36 2716 (0x0A9C)
Task sequence launcher advertisement failed!. Code 0x80070057 TSLauncher 12.11.2010 15:17:36 2716 (0x0A9C)
Successfully finalized logs to SMS client log directory from C:\WINNT\system32\CCM\Logs TSLauncher 12.11.2010 15:17:36 2716 (0x0A9C)
Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Active Request Handle. Error code 0x80070002 TSLauncher 12.11.2010 15:17:36 2716 (0x0A9C)
Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002 TSLauncher 12.11.2010 15:17:36 2716 (0x0A9C)
Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created TSLauncher 12.11.2010 15:20:33 5016 (0x1398)
Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created TSLauncher 12.11.2010 15:20:33 5016 (0x1398)
GetPrivateProfileString() failed to get SMS Client GUID from file. Code 0x00000000 TSLauncher 12.11.2010 15:20:33 5016 (0x1398)
Error getting package location and access account information. Code 0x80070057 TSLauncher 12.11.2010 15:20:33 5016 (0x1398)
Error initializing TS environment. Code 0x80070057 TSLauncher 12.11.2010 15:20:33 5016 (0x1398)
Task sequence launcher advertisement failed!. Code 0x80070057 TSLauncher 12.11.2010 15:20:33 5016 (0x1398)
Successfully finalized logs to SMS client log directory from C:\WINNT\system32\CCM\Logs TSLauncher 12.11.2010 15:20:33 5016 (0x1398)
Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Active Request Handle. Error code 0x80070002 TSLauncher 12.11.2010 15:20:33 5016 (0x1398)
Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002 TSLauncher 12.11.2010 15:20:33 5016 (0x1398)
Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created TSLauncher 12.11.2010 15:22:02 5468 (0x155C)
Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created TSLauncher 12.11.2010 15:22:02 5468 (0x155C)
GetPrivateProfileString() failed to get SMS Client GUID from file. Code 0x00000000 TSLauncher 12.11.2010 15:22:02 5468 (0x155C) -
Ist's native oder mixed mode?
Hat denn die Client Registration laut ClientIDManagerStartup.log funktioniert?
Wegen "failed to get SMS Client GUID from file" würde ich mal in %windir%\smscfg.ini schauen, ob dort die GUID vorhanden ist (ist aber nur eine Vermutung). -
Die Client Registrierung hat laut Log funktioniert. In der smscfg.ini ist auch die GUID vorhanden. Was passiert denn genau, wenn ein Task ausgeführt wird und ein Programm installiert wird? Wird ein MIF FIle erzeugt? Ich habe in verdacht, das unser Antivirus beim Installationsvorgang in die quere gekommen ist und es so zu einem undefinierten Zustand kommt, andem es nicht mehr vor und zurück geht. Wo kann man den Status der Programminstallation einsehen? Kann man diesen eventuell wieder zurücksetzen?
RegTask - Executing registration task synchronously. ClientIDManagerStartup 12.11.2010 14:34:42 4572 (0x11DC)
Read SMBIOS (encoded): 3500560054003200340034004A00 ClientIDManagerStartup 12.11.2010 14:34:42 4572 (0x11DC)
Evaluated SMBIOS (encoded): 3500560054003200340034004A00 ClientIDManagerStartup 12.11.2010 14:34:42 4572 (0x11DC)
No SMBIOS Changed ClientIDManagerStartup 12.11.2010 14:34:42 4572 (0x11DC)
SMBIOS unchanged ClientIDManagerStartup 12.11.2010 14:34:42 4572 (0x11DC)
SID unchanged ClientIDManagerStartup 12.11.2010 14:34:42 4572 (0x11DC)
HWID unchanged ClientIDManagerStartup 12.11.2010 14:34:42 4572 (0x11DC)
RegTask: Initial backoff interval: 1 minutes ClientIDManagerStartup 12.11.2010 14:34:43 4572 (0x11DC)
RegTask: Reset backoff interval: 257 minutes ClientIDManagerStartup 12.11.2010 14:34:43 4572 (0x11DC)
GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE ClientIDManagerStartup 12.11.2010 14:34:44 4572 (0x11DC)
Computed HardwareID=2:36B7A1F98D2B6447F76C44E85F634EFFB0075E5B
Win32_SystemEnclosure.SerialNumber=xxxx
Win32_SystemEnclosure.SMBIOSAssetTag=
Win32_BaseBoard.SerialNumber=..CN736048BF002K.
Win32_BIOS.SerialNumber=5VT244J
Win32_NetworkAdapterConfiguration.MACAddress=00:21:9B:1D:E1:36 ClientIDManagerStartup 12.11.2010 14:34:44 4572 (0x11DC)
RegTask: Client is not registered. Sending registration request... ClientIDManagerStartup 12.11.2010 14:34:44 4572 (0x11DC)
RegTask: Client is registered. ClientIDManagerStartup 12.11.2010 14:34:45 4572 (0x11DC)
RegTask: Client is registered. Exiting. ClientIDManagerStartup 12.11.2010 14:34:45 4572 (0x11DC)
Read SMBIOS (encoded): 3500560054003200340034004A00 ClientIDManagerStartup 12.11.2010 14:34:45 4572 (0x11DC)
Evaluated SMBIOS (encoded): 3500560054003200340034004A00 ClientIDManagerStartup 12.11.2010 14:34:45 4572 (0x11DC)
No SMBIOS Changed ClientIDManagerStartup 12.11.2010 14:34:45 4572 (0x11DC)
SMBIOS unchanged ClientIDManagerStartup 12.11.2010 14:34:45 4572 (0x11DC)
SID unchanged ClientIDManagerStartup 12.11.2010 14:34:45 4572 (0x11DC)
HWID unchanged ClientIDManagerStartup 12.11.2010 14:34:45 4572 (0x11DC)
Client settings prohibit local GUID generation, no smsid will be (re)generated. ClientIDManagerStartup 12.11.2010 14:34:45 4572 (0x11DC)
Smsid is missing but (re)generation is disabled. ClientIDManagerStartup 12.11.2010 14:34:45 4572 (0x11DC)
RegTask - Executing registration task synchronously. ClientIDManagerStartup 12.11.2010 15:27:48 3536 (0x0DD0)
Read SMBIOS (encoded): 3500560054003200340034004A00 ClientIDManagerStartup 12.11.2010 15:27:48 3536 (0x0DD0)
Evaluated SMBIOS (encoded): 3500560054003200340034004A00 ClientIDManagerStartup 12.11.2010 15:27:48 3536 (0x0DD0)
No SMBIOS Changed ClientIDManagerStartup 12.11.2010 15:27:48 3536 (0x0DD0)
SMBIOS unchanged ClientIDManagerStartup 12.11.2010 15:27:48 3536 (0x0DD0)
SID unchanged ClientIDManagerStartup 12.11.2010 15:27:48 3536 (0x0DD0)
HWID unchanged ClientIDManagerStartup 12.11.2010 15:27:48 3536 (0x0DD0)
RegTask: Initial backoff interval: 1 minutes ClientIDManagerStartup 12.11.2010 15:27:49 3536 (0x0DD0)
RegTask: Reset backoff interval: 257 minutes ClientIDManagerStartup 12.11.2010 15:27:49 3536 (0x0DD0)
GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE ClientIDManagerStartup 12.11.2010 15:27:49 3536 (0x0DD0)
Computed HardwareID=2:36B7A1F98D2B6447F76C44E85F634EFFB0075E5B
Win32_SystemEnclosure.SerialNumber=xxxxWin32_SystemEnclosure.SMBIOSAssetTag=
Win32_BaseBoard.SerialNumber=..CN736048BF002K.
Win32_BIOS.SerialNumber=5VT244J
Win32_NetworkAdapterConfiguration.MACAddress=00:21:9B:1D:E1:36 ClientIDManagerStartup 12.11.2010 15:27:49 3536 (0x0DD0)
RegTask: Client is not registered. Sending registration request... ClientIDManagerStartup 12.11.2010 15:27:49 3536 (0x0DD0)
RegTask: Client is registered. ClientIDManagerStartup 12.11.2010 15:27:50 3536 (0x0DD0)
RegTask: Client is registered. Exiting. ClientIDManagerStartup 12.11.2010 15:27:50 3536 (0x0DD0)
Read SMBIOS (encoded): 3500560054003200340034004A00 ClientIDManagerStartup 12.11.2010 15:27:50 4924 (0x133C)
Evaluated SMBIOS (encoded): 3500560054003200340034004A00 ClientIDManagerStartup 12.11.2010 15:27:50 4924 (0x133C)
No SMBIOS Changed ClientIDManagerStartup 12.11.2010 15:27:50 4924 (0x133C)
SMBIOS unchanged ClientIDManagerStartup 12.11.2010 15:27:50 4924 (0x133C)
SID unchanged ClientIDManagerStartup 12.11.2010 15:27:50 4924 (0x133C)
HWID unchanged ClientIDManagerStartup 12.11.2010 15:27:50 4924 (0x133C)
Client settings prohibit local GUID generation, no smsid will be (re)generated. ClientIDManagerStartup 12.11.2010 15:27:50 4924 (0x133C)
Smsid is missing but (re)generation is disabled. ClientIDManagerStartup 12.11.2010 15:27:50 4924 (0x133C)
RegTask - Executing registration task synchronously. ClientIDManagerStartup 12.11.2010 15:40:05 4492 (0x118C)
Read SMBIOS (encoded): 3500560054003200340034004A00 ClientIDManagerStartup 12.11.2010 15:40:05 4492 (0x118C)
Evaluated SMBIOS (encoded): 3500560054003200340034004A00 ClientIDManagerStartup 12.11.2010 15:40:05 4492 (0x118C)
No SMBIOS Changed ClientIDManagerStartup 12.11.2010 15:40:05 4492 (0x118C)
SMBIOS unchanged ClientIDManagerStartup 12.11.2010 15:40:05 4492 (0x118C)
SID unchanged ClientIDManagerStartup 12.11.2010 15:40:05 4492 (0x118C)
HWID unchanged ClientIDManagerStartup 12.11.2010 15:40:05 4492 (0x118C)
RegTask: Initial backoff interval: 1 minutes ClientIDManagerStartup 12.11.2010 15:40:06 4492 (0x118C)
RegTask: Reset backoff interval: 257 minutes ClientIDManagerStartup 12.11.2010 15:40:06 4492 (0x118C)
GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE ClientIDManagerStartup 12.11.2010 15:40:06 4492 (0x118C)
Computed HardwareID=2:36B7A1F98D2B6447F76C44E85F634EFFB0075E5B
Win32_SystemEnclosure.SerialNumber=xxxx Win32_SystemEnclosure.SMBIOSAssetTag=
Win32_BaseBoard.SerialNumber=..CN736048BF002K.
Win32_BIOS.SerialNumber=5VT244J
Win32_NetworkAdapterConfiguration.MACAddress=00:21:9B:1D:E1:36 ClientIDManagerStartup 12.11.2010 15:40:06 4492 (0x118C)
RegTask: Client is not registered. Sending registration request... ClientIDManagerStartup 12.11.2010 15:40:06 4492 (0x118C)
RegTask: Client is registered. ClientIDManagerStartup 12.11.2010 15:40:07 4492 (0x118C)
RegTask: Client is registered. Exiting. ClientIDManagerStartup 12.11.2010 15:40:07 4492 (0x118C)
Read SMBIOS (encoded): 3500560054003200340034004A00 ClientIDManagerStartup 12.11.2010 15:40:07 5332 (0x14D4)
Evaluated SMBIOS (encoded): 3500560054003200340034004A00 ClientIDManagerStartup 12.11.2010 15:40:07 5332 (0x14D4)
No SMBIOS Changed ClientIDManagerStartup 12.11.2010 15:40:07 5332 (0x14D4)
SMBIOS unchanged ClientIDManagerStartup 12.11.2010 15:40:07 5332 (0x14D4)
SID unchanged ClientIDManagerStartup 12.11.2010 15:40:07 5332 (0x14D4)
HWID unchanged ClientIDManagerStartup 12.11.2010 15:40:07 5332 (0x14D4)
Client settings prohibit local GUID generation, no smsid will be (re)generated. ClientIDManagerStartup 12.11.2010 15:40:07 5332 (0x14D4)
Smsid is missing but (re)generation is disabled. ClientIDManagerStartup 12.11.2010 15:40:07 5332 (0x14D4) -
Probiere mal folgendes: stoppe den ConfigMgr Client, entferne die SMS-Zertifikate auf dem Client und starte den Client wieder. ClientIDManagerStartUp.log beobachten, warten bis der Client registriert ist, Policies aktualisieren, TS nochmal starten.
- Als Antwort vorgeschlagen TorstenMMVP, Editor Dienstag, 23. November 2010 14:45
- Als Antwort markiert Andrei TalmaciuModerator Dienstag, 30. November 2010 12:49
-
Die SMS Zertifikate auf dem Client mit dem Fehler habe ich gelöscht. Daraufhin wurde in SCCM eine neue GUID erzeugt und das Problem ist damit vorerst behoben. Das Problem ist allerdings, dass dieses Phänomen öfters an unterschiedlichen Clients auftritt. Wie kann so ein Problem entstehen? Wie ist der genaue Vorgang auf dem Client beim Ankündigen einer Task? Kann ein Antivierenprogramm eventuell den Ankündigungsvorgang stören?
-
Gute Frage(n), die aber über die Möglichkeiten eines Forums hinaus gehen. Ich kann Dir leider auch keinen Grund für das Fehlschlagen nennen. Anti-Virus kann ich mir nicht direkt vorstellen, ausschliessen möchte ich es aber trotzdem nicht.
-