Solved

SCCM 0x00000643

Posted on 2011-03-18
6
3,586 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
  • 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
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 

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

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Citrix, Terminal Services, vmWare? 8 98
deploying a service to production environment 13 109
sccm importing drivers 4 45
Set Folder Permissions to Prevent Move and Delete 1 40
Problem Description: Actually I found the below issue with some customers after migration from SMS 2003 to SCCM 2007 and epically if they change site code, some clients may appear in the console with old site code, plus old sites still appearing …
Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found listed in my profile here: http:…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

820 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