SMS issues - code 30014 - Office deployment

SMS issues - code 30014 - Office deployment (Full Version)

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003

Message

alexandp -> SMS issues - code 30014 - Office deployment (7/4/2008 8:32:08 AM)
Hi, I'm trying to distribute a package of Office 2007 Standard. The desktop received the advertisement of the package and starts to download his content. After the download, when the desktop will starts to run the Setup.exe I received the follow error in Status Messages: The program for advertisement "XXXXX" failed ("XXXXX" - "Install"). A failure exit code of 30014 was returned. User context: NT AUTHORITY\SYSTEM Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. An exit code of 30014 is considered a failure. Solution: For more information on the exit code, refer to the documentation for the program you are distributing. Somebody knows what this code error 30014 refers? Tks!

chikymiky -> RE: SMS issues - code 30014 - Office deployment (7/8/2008 1:39:54 AM)
i am lloking for the same. please help

mp115 -> RE: SMS issues - code 30014 - Office deployment (7/8/2008 6:42:00 AM)
What does your install string look like?

alexandp -> RE: SMS issues - code 30014 - Office deployment (7/8/2008 10:11:57 AM)
i didn't find anything about this error yet... I'm looking in the Office 2007 product documentation now... Anybody knows it? Tks.

mp115 -> RE: SMS issues - code 30014 - Office deployment (7/8/2008 11:20:46 AM)
Once more, post the installation string that you're using,

alexandp -> RE: SMS issues - code 30014 - Office deployment (7/8/2008 12:27:45 PM)
I did the instalation manually using the command line: %SourcePatch%\Office2007_Standard\setup.exe When I try to install by SMS its returns the code error spoken above. I found a log of setup.exe that is: PERF: TickCount=334247640 Name=OBootStrapper::Run Description=Begin function Operating System version: 5.1.2600 Service Pack 2. Platform ID: 2 Running on a 32-bit operating system. Command line: "C:\WINDOWS\system32\CCM\Cache\D0100104.1.System\setup.exe" No command line arguments given Verify file signature in "C:\WINDOWS\system32\CCM\Cache\D0100104.1.System\setup.exe" Verify file signature in "C:\WINDOWS\system32\CCM\Cache\D0100104.1.System\Standard.WW\OSETUP.DLL" Using setup controller dll at [C:\WINDOWS\system32\CCM\Cache\D0100104.1.System\Standard.WW\OSETUP.DLL]. PERF: TickCount=334250453 Name=OBootStrapper::Run Description=Calling RunSetup Opening log file C:\DOCUME~1\BRCSAO~1\LOCALS~1\Temp\SetupExe(20080708115829FDC).log. ========================================================================= PERF: TickCount=334250453 Name=RunSetup Description=Begin function Catalyst execution began: 07/08/2008 11:58:29. Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [disabled] for the [InstallExecutionMode] Searching for updated versions of resource files under the 'updates' folder [C:\WINDOWS\system32\CCM\Cache\D0100104.1.System\updates]. Found [0] resource files under the update folder. Searching for default versions of resource files under the folder [C:\WINDOWS\system32\CCM\Cache\D0100104.1.System]. Resource File Manager : Found (CultureTag=en-US) resource file at [C:\WINDOWS\system32\CCM\Cache\D0100104.1.System\Office.en-us\OSETUPUI.DLL]. Found [1] resource files under the default folder. Resource File Manager : Current user's LCID is [1033]. Resource File Manager : Selecting resource file (File=C:\WINDOWS\system32\CCM\Cache\D0100104.1.System\Office.en-us\OSETUPUI.DLL) for CultureTag [en-US]. Running in [InstallExecutionMode]. Run from TEMP folder at [C:\DOCUME~1\BRCSAO~1\LOCALS~1\Temp\Setup00000fdc]. Loaded resource file [C:\DOCUME~1\BRCSAO~1\LOCALS~1\Temp\Setup00000fdc\OSETUPUI.DLL] (CultureTag=en-US). Loaded Dll : C:\WINDOWS\system32\CCM\Cache\D0100104.1.System\Standard.WW\OSETUP.DLL. Catalyst version is : 12.0.4518.1014 JobExecutionMode is InstallExecutionMode. LIS: start parsing setup xml LIS: finished parsing LIS package "{90120000-0016-0409-0000-0000000FF1CE}" LIS: start parsing setup xml LIS: finished parsing LIS package "{90120000-0115-0409-0000-0000000FF1CE}" LIS: start parsing setup xml LIS: finished parsing LIS package "{90120000-0116-0409-1000-0000000FF1CE}" LIS: start parsing setup xml LIS: finished parsing LIS package "{90120000-001A-0409-0000-0000000FF1CE}" LIS: start parsing setup xml LIS: finished parsing LIS package "{90120000-0018-0409-0000-0000000FF1CE}" LIS: start parsing setup xml LIS: finished parsing LIS package "{90120000-002C-0409-0000-0000000FF1CE}" LIS: start parsing setup xml LIS: finished parsing LIS package "{90120000-0010-0409-0000-0000000FF1CE}" LIS: start parsing setup xml LIS: finished parsing LIS package "{90120000-0010-0409-0000-0000000FF1CE}" Error: attempting to parse a setup.xml for an already parsed product Type: DuplicateDefinition. Catalyst execution finished: 07/08/2008 11:58:30. Return code: 30014. Exception caught: DuplicateDefinition. PERF: TickCount=334250843 Name=RunSetup Description=End function

mp115 -> RE: SMS issues - code 30014 - Office deployment (7/8/2008 4:51:09 PM)
Ok, so a manual install works fine, but when you use SMS to do it, it errors out? I google around for "Error: attempting to parse a setup.xml" and it came up with a few other 2007 products from MS that were having that same error. I'm reaching here, but could it be an issue with the XML parser on the machine or the files in the cached location "C:\DOCUME~1\BRCSAO~1\LOCALS~1\Temp\Setup00000fdc"? Try clearing out that cached temp folder and see if it does the same thing.

rbennett806 -> RE: SMS issues - code 30014 - Office deployment (7/8/2008 11:15:20 PM)
Are you including any sort of .MST or .XML file as an answer file for the installation? I don't use the Strandard Edition so I may be off base here... Do either one of these threads help? http://www.myitforum.com/forums/m_171506/mpage_1/key_Office%252C2007%252Csetup%252Eexe/tm.htm#171980 http://www.myitforum.com/forums/m_176658/mpage_1/key_Office%252C2007%252Csetup%252Eexe/tm.htm#176673

alexandp -> RE: SMS issues - code 30014 - Office deployment (7/10/2008 9:08:59 AM)
Hi, Right, a manual installation works fine. When I distribute the package by SMS.. returns the error code. I tried to clean the cache folder and I re-run the Advertisement but the error occured again. I'll try to install the same package executing the program from the distribution point.

alexandp -> RE: SMS issues - code 30014 - Office deployment (8/26/2008 9:51:00 AM)
Hi, This problem was solved when I did a new copy of source files used by Office 2007 instalation. Maybe a problem during the initial copy of source files to my DPs. So, if somebody has been this problem, try it. Tks for all.

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.4882813