Hello all. I have an issue with a deployed application on our network with GPO. Basically, this is a shared application (french corrector). We push the setup with gpo, it creates link on every computer, no local file are really installed on the client.

Sorry if I can't provide real error, they are in french and would be kinda useless.

Event log error is

Can't access installation source. Verify that you have access.

Now everything on share/security side is ok. A security group in which I included the computer machine has right.

I enabled logging for Windows Installer. Here is what I have:


MSI (s) (B8:CC) [11:44:56:109]: SOURCEMGMT: Media is enabled for product.
MSI (s) (B8:CC) [11:44:56:109]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (B8:CC) [11:44:56:109]: SOURCEMGMT: Processing net source list.
MSI (s) (B8:CC) [11:44:56:109]: SOURCEMGMT: Trying source \\server\shares$\Antidote\.
MSI (s) (B8:CC) [11:44:56:578]: Note: 1: 2303 2: 5 3: \\server\shares$\
MSI (s) (B8:CC) [11:44:56:593]: Note: 1: 2303 2: 5 3: \\server\shares$\
MSI (s) (B8:CC) [11:44:56:593]: Note: 1: 1325 2: Antidote_RX.msi
MSI (s) (B8:CC) [11:44:56:593]: Note: 1: 1706 2: -2147483647 3: Antidote_RX.msi
MSI (s) (B8:CC) [11:44:56:593]: SOURCEMGMT: Processing media source list.
MSI (s) (B8:CC) [11:44:57:718]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (B8:CC) [11:44:57:718]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (B8:CC) [11:44:57:718]: Note: 1: 1706 2: -2147483647 3: Antidote_RX.msi
MSI (s) (B8:CC) [11:44:57:718]: SOURCEMGMT: Processing URL source list.
MSI (s) (B8:CC) [11:44:57:718]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (B8:CC) [11:44:57:718]: Note: 1: 1706 2: -2147483647 3: Antidote_RX.msi
MSI (s) (B8:CC) [11:44:57:718]: Note: 1: 1706 2: 3: Antidote_RX.msi
MSI (s) (B8:CC) [11:44:57:734]: SOURCEMGMT: Failed to resolve source
MSI (s) (B8:CC) [11:44:57:734]: MainEngineThread is returning 1612


I've been looking on forums and I found that thread

http://itninja.com/question/anybody-using-afaria-5.0803&mpage=1&key=SOURCEMGMT&#34892

It looks like it's the same error.

Anyone has any clue on this?
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity

Answers

0
Qucik update on this. Assigning the same software distribution to users instead or computer works.
Answered 05/14/2009 by: wd40
Orange Senior Belt

Please log in to comment
0
I suspect that the machines don't have access to that share whereas, presumably, your users do.

As an experiment, assign permissions (share and/or file system, depending on how your environment is set up) for a test machine and re-test.
Answered 05/14/2009 by: VBScab
Red Belt

Please log in to comment
0
Well I just gave read access to Domain Computer, and still I have the error.

I managed to get some monitoring with filemon

15:09:09 System:8 FASTIO_MDL_READ D:\Logiciels\Antidote\Antidote_RX.msi FAILURE Offset: 0 Length: 32768
15:09:09 System:8 FASTIO_READ D:\Logiciels\Antidote\Antidote_RX.msi FAILURE Offset: 0 Length: 32768

Did some googling, but could'nt find anything interesting.

Any idea?
Answered 05/14/2009 by: wd40
Orange Senior Belt

Please log in to comment
0
Try commenting-out the 'ResolveSource' action via a transform if this is a vendor MSI or directly in the MSI if it's "yours".
Answered 05/14/2009 by: VBScab
Red Belt

Please log in to comment
0
It's a vendor MSI. I now think the problem is server side. I did the same installation on another server, and it worked fine... Incoming headache...
Answered 05/19/2009 by: wd40
Orange Senior Belt

Please log in to comment