"Sccm 2012 error 1603" Software Distribution Fails

Sccm 2012 error 1603 by description is only a general windows installer msiexec fatal error code. Most of the people were marking this as a software bundle deployment. The exciting element was an app that was packaged toward us by a third party vendor,

Someone asked me a question with Sccm 2012 error 1603 r2 and failed packages. For all set, he tries to use there is the various one that forever turns a generic Sccm error message 0x643.
So this issue took my attention towards this tricky complex problem. When third parties develop an application, they try their best to work this application over all the systems but sometimes they fail to do so. so this application works on some system but not at all. So users write their error problem on their forums or website for the solution . also they try to post on social media. But trust me this all process take time to resolve. so I thought to give you brief information regarding Sccm 2012 1603 so you can solve these sort of error by yourself without extra help.

When a local admin account does login while runtime, the app would install without any fix. It would further fit install if there is no one is login. But, if a limited user or user without admin rights will log in, he can receive the Sccm 1603 error.”

I saw lots of successful installation of Sccm 2012, I discovered that maximum successful installations were from a Specific operating system which was (Win 7). The 1603 error installation coming from Microsoft Windows 8,10 or XP. So I decided to test this myself on these OS, on which people are facing Sccm 2012 error 1603.

After that, I studied at the application installer and Find out the way how this app was created in SCCM, I don"t know much about its developing because I don"t have its source code or other developing queries. I observe it with some useful tools about its structure of working. After too much research I finally find out that this installer has script transform which is using ISScript8 when you first install on your system.

ISScript8.Msi is a sort of MSI file connected with Line of Sight Vietnam produced by Infogrames for the Win OS. At this time when I was writing this article, its modern variant is ISScript8.Msi is 1.0.0.0.

The most common errors of MSI which are:

"ISScript8.Msi error."
"ISScript8.Msi is missing."
"ISScript8.Msi not found."
"ISScript8.Msi failed to load."
"Failed to register ISScript8.Msi."
"Runtime Error: ISScript8.Msi."
"Error loading ISScript8.Msi."

This error occurs while computer startup, the Software startup, or while attempting to practice a particular Action in your Operating system like file sharing, printing etc.

If You receive errors there is little but effective freeware software(https://www.solvusoft.com/en/files/error-missing-download/msi/windows/infogrames/line-of-sight-vietnam/isscript8-msi/). You can use them freely.

Now back to our topic, I talk to some professional tech experts about this Sccm 2012 error 1603. Most of them said that reference to DCOM InstallShield InstallDriver Identity properties being set incorrectly.

So I dig deep in it at the InstallShield InstallDriver Properties from DCOMCNFG. Please follow it below

Press Window +R to open run box and  type in (dcomcnfg)

[box type="info"] Select Component Services\Computers\My Computer\DCOM Config[/box]



Right click on InstallShield and Select Properties then Select the Identity tab.

here I selected interactive user. So by adjusting InstallShield identities to The Launching User, Now I can install successfully with low admin rights. If you don"t want to follow this setting or don"t find InstallShield into DCOM config. follow this article fatal error code 1603 quick heal how to give admin rights  to specific hard drive partition or folder.

ISStartup was still returning Sccm 2012 error 1603

Establishing a new MSI to present the data in ISScript11.msi passed the script engine to be connected both interactively, and used from SCCM, but some people are asking that some application still wouldn’t install.

After experimenting with modifying the setting in dcomcnfg, I understood that only killing the elements iDriver.exe_Interactive_Key_NT4 & iDriver.exe_Interactive_Key from new MSI would resolve the problem.

[box type="warning"] (fatal error )application might be unsafe. please contact your administrator[/box]

Sometimes While running MSI file by double-clicking on an operating system where the Software Distribution Fails, Sccm 2012 error 1603 occurs that the application might be unsafe. please contact your administrator to change user interface option for package basic.

I find the way to install MSI by double-clicking . to resolve Sccm 2012 error, use installation switch /QB b-basic on the command line when creating the application. this is instruction for developers while creating the new application for operating systems.

[box type="bio"] msiexec /i "abc.msi" /QB /norestart[/box]

 

Ok if you are still suffering from Sccm 2012 error 1603

Do it my manual way but you need to be careful because it"s a deep and effective method. Little misconfiguration can cause you big plenty. I assure you if You will follow this solution as I command, You will never be more victim regarding this Sccm error.

First, you have to Stop the Services named (SMS Agent Host Service),(CCMSetup service (if present). After that remove ccm directory, ccmsetup dir, ccmcache directory, smscfg.ini, in windows. And one more thing if there are windows\sms*.mif then also delete it.

The next task it to clean registry

[box type="info"] remove ccm keys situated in HKLM\software\Microsoft\ccm reg keys[/box]

[box type="info"] CCMSetup keys HKLM\software\Microsoft\CCMSETUP reg keys[/box]

[box type="info"] SMS Reg keys HKLM\software\Microsoft\SMS registry keys[/box]

ok let"s go to the WMI to remove from root

remove "SMS wmi namespace" which path is root\cimv2\sms WMI namespace and then also del root\ccm WMI namespace

the last operation is to delete automatically task schedules from config manager and this folder itself. this folder will be available under Microsoft.

i have created power shell script to do the above job . if you dont want to manually remove.

download script from this link fatal error 

And run it through power-shell . if you don"t know how to run power shell scripts . follow the https://ss64.com/ps/syntax-run.html

Final Steps:

[box type="bio"] run check disk command from CMD "CHKDSK /F " After checking disk restart. now open command prompt again and run this command in it "fsutil resource setautoreset true C:\" and restart again the system. ok, now you are good to go. install SCCM without any 1306 fatal error[/box]