hey all,
Here's the problem:
i created an msi package. I want to assign that msi to workstations in a certain OU. The installation fails everytime. Error: "

Event ID: 102
User: NT AUTHORITY\SYSTEM
Computer: THINKCENTRE2
Description:
The install of application SBClient524 from policy sbclient failed. The error was The installation source for this product is not available. Verify that the source exists and that you can access it. . "

Now, the tricky part is that im sure the path is correct: "\\nas\public\packages\product\sbclient542.msi"
If i type in that address in the workstation's explorer, it will take me to the correct folder/file.
Moreover, if i assign the same msi file to 'user' as opposed to 'computer' fotr that OU, the installation works like a charm.

TIA for all your help,

Adam
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
User: NT AUTHORITY\SYSTEM

If this is the account installing the MSI it will have no network rights. You either have to set up a null session share on the server which is a security risk or use a different account to install the MSI.
Answered 08/26/2004 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
Thanks kkaminsk...

Can ya tell me how can i use a different account to install an msi?
Thanks

~a
Answered 08/26/2004 by: sawczukx
Yellow Belt

Please log in to comment
0
If you want to call it from a script then you can use the runas command.
Answered 08/26/2004 by: cdupuis
Third Degree Green Belt

Please log in to comment
0
Hi,
Is it the only software that gets this error message when assign it to a workstation?
Answered 09/10/2004 by: plourenco
Senior Yellow Belt

Please log in to comment
0
Hi!

I had the same thing.
I was working on a contract and accepted the location for the MSI repository as given to me.

Turns out it was on a NT4 Server (member server) in an AD Domain (mixed mode)

What OS is the server that is hosting the packages share?
NT will not provide Kerberos Authentication to the workstation thereby making application installation of an assigned nature impossible.

Hope that helps!


Mike
Answered 09/10/2004 by: kirkpatrick
Yellow Belt

Please log in to comment
0
in addition to what kirkpatrick is saying, the same is true if the install files reside on a clustered share. i read up on a "fix" for the clustered share issue but it seemed really involved and risky.

-drew
Answered 09/10/2004 by: peart75
Senior Yellow Belt

Please log in to comment
0
Can ya tell me how can i use a different account to install an msi?
Thanks


Well I missed this one by a long time but here are some suggestions. If you want to use a different account you would have to publish the MSI to a user instead of a machine. That is what I am assuming by looking at the eventlog entry.

Also I got a 102 error when I installed a per machine install of a Canon driver that used InstallShield Script V7. The MSI could not make a successful DCOM call to the InstallShield Script Driver. So I guess in short turn on all the MSI logging so that you might see the real reason the 102 error is happening.
Answered 09/13/2004 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity