Solved

SCCM 0x00000643

Posted on 2011-03-18
6
3,665 Views
Last Modified: 2013-11-21
When I run the following command in a task sequence, I get a 0x00000643 error on the client.

msiexec /i InstallBSR_v5.msi >>> of type Run Command Line with the source being a package.

I can run the command on the target machine manually and it works just fine.  I have tried running it as my Domain Admin account.

Does anyone have any ideas.

-Thomas
0
Comment
Question by:Cystixs
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
  • 2
6 Comments
 
LVL 14

Expert Comment

by:Abduljalil Abou Alzahab
ID: 35171304
Hello,

if you want to install software through task sequence, please first go and create pacakge for your applicaion -> copy to distribution point -> create a new program with the following command line:
msiexec /i InstallBSR_v5.msi /q

then edit task sequence and add "install software" at the end of your task sequence then select the package and program that you create

Notes:
1- It's important to go proprties of prgram -> Environment -> Run mode "Run with administrator rights", and in program can run choose "whether or not a user is loged in".
2- Go to prgram -> advanced -> choose "Suppress program notification" and Allow this program to be installed from install software task sequence without being advertised.

To know how to create package in software distribution:
http://technet.microsoft.com/en-us/library/bb693627.aspx
 
0
 

Expert Comment

by:jamie77777
ID: 35176407
Agree with a-Jaleel, the source should definitly be a self-contained packaged.

You should also advertise the software directly to a client to test, this will rule out the task sequence and make any other errors easier to troubleshoot, through advertisement logs/status on the client/server.

Would also advise changing your command line to be:
msiexec.exe /i InstallBSR_v5.msi ADDLOCAL=ALL /qn

This will get rid of all all user interaction and install all 'features' in the MSI.

0
 

Author Comment

by:Cystixs
ID: 35185051
I do about 3 to 4 deployments a day so I don't believe the issue is me creating packages and adverts.  The issue has something to do with that specific command line generating the error stated above.  Thanks for your suggesting on the command line changes Jamie77777; I did try that, but unfortunately it did not fix the issue.

The funny thing is that if I do this as a software installation via SCCM it works fine, just not as a task sequence.  I need it to be a task sequence because I need other things to be ran after the msi completes execution.
0
How Do You Stack Up Against Your Peers?

With today’s modern enterprise so dependent on digital infrastructures, the impact of major incidents has increased dramatically. Grab the report now to gain insight into how your organization ranks against your peers and learn best-in-class strategies to resolve incidents.

 

Expert Comment

by:jamie77777
ID: 35185705
It could be related to something else in the Task Sequence.  Have you tried deploying using a Task Sequence, with nothing else in the Task Sequence?
0
 
LVL 14

Accepted Solution

by:
Abduljalil Abou Alzahab earned 500 total points
ID: 35186806
If the deployment success without task sequece, that's mean package and command line are correct, I'm always deploying package with task sequence, the most important change in package before us it in task sequence is to configure:
1- It's important to go proprties of prgram -> Environment -> Run mode "Run with administrator rights", and in program can run choose "whether or not a user is loged in".
2- Go to prgram -> advanced -> choose "Suppress program notification" and Allow this program to be installed from install software task sequence without being advertised.

but if it fail too, can you please send to me smsts.log file on the client machine
for x86 c:\windows\system32\ccm\logs
for x64 c"\windiws\SysWOW64\ccm\logs
0
 

Author Closing Comment

by:Cystixs
ID: 35316131
Honestly, I didn't use these changes as we changed the program we were using to distribute the MSI and change the program we were distributing.  I do however appreciate you suggestions and your willingness to offer continued assistance in reference to the issue.

-Thomas
0

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

1. Boot PC and press F10, select storage options and change the compatibility from “AHCI” to “IDE”, save and exit 2. Boot PC and press F12 3. Upon PXE display of searching for DHCP server, press Pause break to obtain MAC address 3. Open Configu…
Know what services you can and cannot, should and should not combine on your server.
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question