There are at least two problems in the new standalone MSI setup package
sw_lic_full_installer.msi.
1) You use the same MSI GUID for the new installer and the old
mm_fl_sw_installer.msi, which makes it impossible to distinguish the currently
installed product. Also the setup of the new MSI does not work correctly if the
old package is installed. Please change the GUID!!!
2) It is impossible to deploy the MSI package to computers via SMS 2003 and
advanced security. The MSI package uses the users Application Data directory to
temporary store files. This directory and user settings do not exist in this
case! Please change the behavior to use the environment variable TEMP!
When you use SMS to deploy, you get the following error message:
"Error 1606. Could not access network location \Macromedia\Shockwave Player\."
I created two logfiles, one as interactively logged on user and one when SMS
tries to install the product:
User:
....
MSI (s) (04:20) [17:23:01:476]: Dir (target): Key: SWAImportExport , Object:
C:\Profile\xtras\download\MacromediaInc\SWAImportExport\
MSI (s) (04:20) [17:23:01:476]: Dir (target): Key: SoundImportExport , Object:
C:\Profile\xtras\download\MacromediaInc\SoundImportExport\
MSI (s) (04:20) [17:23:01:476]: Dir (target): Key: MPEG3ImportExport , Object:
C:\Profile\xtras\download\MacromediaInc\MPEG3ImportExport\
MSI (s) (04:20) [17:23:01:476]: Dir (target): Key: MixServices , Object:
C:\Profile\xtras\download\MacromediaInc\MixServices\
Action start 17:23:01: CostFinalize.
MSI (s) (04:20) [17:23:01:476]: Doing action: setPROFILE
Action ended 17:23:01: CostFinalize. Return value 1.
MSI (s) (04:20) [17:23:01:476]: PROPERTY CHANGE: Modifying PROFILE property.
Its current value is 'C:\Profile\'. Its new value: 'C:\Dokumente und
Einstellungen\ef1\Anwendungsdaten\Macromedia\Shockwave Player\'.
MSI (s) (04:20) [17:23:01:476]: PROPERTY CHANGE: Modifying dswMedia property.
Its current value is 'C:\Profile\dswMedia\'. Its new value: 'C:\Dokumente und
Einstellungen\ef1\Anwendungsdaten\Macromedia\Shockwave Player\dswMedia\'.
MSI (s) (04:20) [17:23:01:476]: PROPERTY CHANGE: Modifying Prefs property. Its
current value is 'C:\Profile\Prefs\'. Its new value: 'C:\Dokumente und
Einstellungen\ef1\Anwendungsdaten\Macromedia\Shockwave Player\Prefs\'.
MSI (s) (04:20) [17:23:01:476]: PROPERTY CHANGE: Modifying xtras property. Its
current value is 'C:\Profile\xtras\'. Its new value: 'C:\Dokumente und
Einstellungen\ef1\Anwendungsdaten\Macromedia\Shockwave Player\xtras\'.
MSI (s) (04:20) [17:23:01:476]: PROPERTY CHANGE: Modifying download property.
Its current value is 'C:\Profile\xtras\download\'. Its new value: 'C:\Dokumente
und Einstellungen\ef1\Anwendungsdaten\Macromedia\Shockwave
Player\xtras\download\'.
MSI (s) (04:20) [17:23:01:476]: PROPERTY CHANGE: Modifying MacromediaInc
property. Its current value is 'C:\Profile\xtras\download\MacromediaInc\'. Its
new value: 'C:\Dokumente und
Einstellungen\ef1\Anwendungsdaten\Macromedia\Shockwave
Player\xtras\download\MacromediaInc\'.
MSI (s) (04:20) [17:23:01:476]: PROPERTY CHANGE: Modifying XMLParser property.
Its current value is 'C:\Profile\xtras\download\MacromediaInc\XMLParser\'. Its
new value: 'C:\Dokumente und
Einstellungen\ef1\Anwendungsdaten\Macromedia\Shockwave
Player\xtras\download\MacromediaInc\XMLParser\'.
MSI (s) (04:20) [17:23:01:476]: PROPERTY CHANGE: Modifying SWAImportExport
property. Its current value is
'C:\Profile\xtras\download\MacromediaInc\SWAImportExport\'. Its new value:
'C:\Dokumente und Einstellungen\ef1\Anwendungsdaten\Macromedia\Shockwave
Player\xtras\download\MacromediaInc\SWAImportExport\'.
MSI (s) (04:20) [17:23:01:476]: PROPERTY CHANGE: Modifying SoundImportExport
property. Its current value is
'C:\Profile\xtras\download\MacromediaInc\SoundImportExport\'. Its new value:
'C:\Dokumente und Einstellungen\ef1\Anwendungsdaten\Macromedia\Shockwave
Player\xtras\download\MacromediaInc\SoundImportExport\'.
MSI (s) (04:20) [17:23:01:476]: PROPERTY CHANGE: Modifying MPEG3ImportExport
property. Its current value is
'C:\Profile\xtras\download\MacromediaInc\MPEG3ImportExport\'. Its new value:
'C:\Dokumente und Einstellungen\ef1\Anwendungsdaten\Macromedia\Shockwave
Player\xtras\download\MacromediaInc\MPEG3ImportExport\'.
MSI (s) (04:20) [17:23:01:476]: PROPERTY CHANGE: Modifying MixServices
property. Its current value is
'C:\Profile\xtras\download\MacromediaInc\MixServices\'. Its new value:
'C:\Dokumente und Einstellungen\ef1\Anwendungsdaten\Macromedia\Shockwave
Player\xtras\download\MacromediaInc\MixServices\'.
Action start 17:23:01: setPROFILE.
MSI (s) (04:20) [17:23:01:476]: Doing action: SetODBCFolders
Action ended 17:23:01: setPROFILE. Return value 1.
MSI (s) (04:20) [17:23:01:476]: Note: 1: 2262 2: ODBCDriver 3: -2147287038
MSI (s) (04:20) [17:23:01:476]: Note: 1: 2262 2: ODBCTranslator 3: -2147287038
....
SMS:
MSI (s) (50:6C) [17:52:46:270]: Dir (target): Key: SoundImportExport , Object:
C:\Profile\xtras\download\MacromediaInc\SoundImportExport\
MSI (s) (50:6C) [17:52:46:270]: Dir (target): Key: MPEG3ImportExport , Object:
C:\Profile\xtras\download\MacromediaInc\MPEG3ImportExport\
MSI (s) (50:6C) [17:52:46:270]: Dir (target): Key: MixServices , Object:
C:\Profile\xtras\download\MacromediaInc\MixServices\
Action start 17:52:46: CostFinalize.
MSI (s) (50:6C) [17:52:46:286]: Doing action: setPROFILE
Action ended 17:52:46: CostFinalize. Return value 1.
MSI (s) (50:6C) [17:52:46:286]: Note: 1: 1314 2: \Macromedia\Shockwave Player\
MSI (s) (50:6C) [17:52:46:286]: Note: 1: 1606 2: \Macromedia\Shockwave Player\
Action start 17:52:46: setPROFILE.
MSI (s) (50:6C) [17:52:46:286]: Product: Macromedia Shockwave Player -- Error
1606. Could not access network location \Macromedia\Shockwave Player\.
MSI (s) (50:6C) [17:52:46:286]: Note: 1: 1606 2: \Macromedia\Shockwave Player\
Error 1606. Could not access network location \Macromedia\Shockwave Player\.
MSI (s) (50:6C) [17:52:46:286]: Product: Macromedia Shockwave Player -- Error
1606. Could not access network location \Macromedia\Shockwave Player\.
Error 1606. Could not access network location \Macromedia\Shockwave Player\.
Action ended 17:52:46: setPROFILE. Return value 3.
Action ended 17:52:46: INSTALL. Return value 3.
I would be very appreciated, if you change this very quickly, since i am
unable to deploy the new versions to our 2.500+ clients!!!
Thank you very much!
Oliver
Thank you for contacting Macromedia Technical Support.
We understand that you are having issues installing Macromedia Shockwave
Player. It is possible there are settings in your Microsoft Active Directory
that is conflicting with the MSI installer. Other than the MSI installer that
is part of our player distribution e-mail, we suggest using the standalone
installer instead:
http://fpdownload.macromedia.com/get/shockwave/default/english/win95nt/10.1.0.01
1/Shockwave_Installer_Full.exe
Or you can try using the Flash-Shockwave MSI installer file below:
http://www.macromedia.com/go/fl_sw_installer
To test your Shockwave player plugin, please visit the link below:
http://www.macromedia.com/shockwave/welcome/
Please take note that there are a lot of factors that can affect the Shockwave
plugin. Again, we strongly suggest that you have the latest version of your
Internet browser installed as this usually fixes most plugin player related
issues.
We hope that you find the above information useful. Should you have further
concern, please feel free to contact us.
FYI - The combined installer installs FlashPlayer 7 with ShockwavePlayer 10.1,
but at least it didn't error out.
From Macromedia Support:
"...I did a little investigation and it turns out the 2 issues you pointed out
are indeed logged into the Director Bugbase which is good news!
The Director/Shockwave team has indicated that when they do another update of
the Shockwave Player they'll be able to resolve the first issue, but at this
time I don't have a specific date for that..."
So, at least they are working on it, but the new security problems with Flash
Player 7 should make them hurry!
BTW: Recently i had to setup a Win98 PC - got the same error :(
"The MSI contains a unusual Custom Action type 35 called: "setPROFILE". It is
used to set the Directory "PROFILE" to "[%APPDATA]\Macromedia\Shockwave
Player". We had some Problems with this Custom Action (Error 1603) so we
dropped this Custom Action from InstallExecuteSequence and rebuild it in
Directory Table and RemoveFile Table.
Wolfgang Zerzawy
CleverITS
www.cleverITS.com"
I have not tested this yet but it might be the answer to our problem.
I had come across this same issue with an SMS deployment of AutoCAD 2006 as it
contained the ShockWave installer as part of its install package. I had to
remove it completely from the install to get SMS 2003 to deploy AutoCAD 2006.
This info from the AppDeploy forum might do the trick. I am not totally
familiar with editing msi tables, but I will try it with ORCA and/or WISE
Package Studio and see if that works.
Good luck.
Yes, please do pass along your steps if you're successful.
1) edited the msi file with ORCA and removed the Custom Action 35 from the
CustomAction Table. (couldn't do it with WISE as there is a reference in the
original MSI in one of the merge modules that is looking for a directory on one
of the packager's PCs...so it errors out)
2) Installed the "edited" MSI on a clean test PC...went to
http://www.macromedia.com/shockwave/welcome/ in IE and Macromedia Shockwave
Player was working with version 10 showing up in the window.
3) uninstalled Shockwave. Installed Shockwave version 8 on a clean PC. Ran my
"edited" MSI...went to http://www.macromedia.com/shockwave/welcome/ in IE and
Macromedia Shockwave Player was working with version 10 showing up in the
window.
I am not sure what the custom action is refering to. It looks like it is
referncing a Windows environmental variable for C:\Documents &
Settings\%username%\Application Data\
This is a problem with SMS 2003 deployments as this version of SMS uses the
system account to install software and the system account does not have a
C:\Documents & Settings profile for Shockwave's MSI to write to...this leads to
the 1603 errors.
I tried to change the "Target" information for teh custom action to use
[%ALLUSERPROFILE]\Application Data\Macromedia\Shockwave Player\ but the MSI
still errored out.
I am going to use the "edited" version for deployment...if anyone figures out
how to edit the MSI as referenced by the posting at AppDeploy.com please post.
I couldn't see how to add the information in the CustomAction 35 entry into the
Directory and RemoveFile tables as Wolfgang stated.
Thanks,
Marc
I have got it to work OK now.
Using ORCA I created a Transform and changed the SetPROFILE custom action to
"[%TEMP]\Macromedia\Shockwave Player\". After this I no longer got 1606 error,
but one about user shell folders'26'. I recognised this from another MSI I was
playing with and realised that I needed to perform a per-machine installation,
so I added to the Property table, ALLUSERS=1
The installation then completed successfully.
Hope it helps someone.
On a side note for SMS 2003 users. If you are deploying the MSI with the /qn
switch to install with no user interface make sure you UNBLOCK the MSI file in
your package source directory and make sure it has propigated that way when
deployed to your DPs. If not, and it tries to run on an XP SP2 system it will
not install as it is waiting for the user to click OK to running the MSI.
To UNBLOCK a file, right click on the file, choose Properties, and then on the
General tab underneath the Advanced button if it has an UBLOCK button, click on
it to unblock the file.
Marc
I laughed my rear off when SMS 2003 changed the way things ran from a Domain
Account to the System Account--now, MS just has to convince thousands of
developers to change their installation routines, and, all will be well...<G>
Thanks
Larry
Can you please tell me where to I can get the msi file named
sw_lic_full_installer.msi?
I have the full executable and am not sure if there is a command line to
extract the MSI From. Also, do you know if this installer will install the
Yahoo Toolbar by default? I am not permitted to use this so I thought I'd ask.
Thanks very much.
Larry
1) edited the msi file with ORCA and removed the Custom Action 35 from the
CustomAction Table. (couldn't do it with WISE as there is a reference in the
original MSI in one of the merge modules that is looking for a directory on one
of the packager's PCs...so it errors out)
2) Installed the "edited" MSI on a clean test PC...went to \Application
Data\Macromedia\Shockwave Player\ but the MSI still errored out.
I am going to use the "edited" version for deployment...if anyone figures out
how to edit the MSI as referenced by the posting at AppDeploy.com please post.
I couldn't see how to add the information in the CustomAction 35 entry into the
Directory and RemoveFile tables as Wolfgang stated.
Thanks,
Marc
Using Marc's method I was able to correct the "Error 1606. Could not access
network location \Macromedia\Shockwave Player\."
issue. I was deploying with Windows Server 2003 AD to a test OU that
continually failed with several MsiInstaller and UserEnv errors. Removing
Custom Action 35 with the ORCA editor did the job straight away.
I also noticed that there was no Yahoo Toolbar after the install and no user
input required after logging in and invoking the player with our Shockwave
enabled training website.
All good news.
Thanks for the write up Marc.
-=J=-
I have read all the threads and tested all the recommendations and came up
with the following:
1. Used ORCA to open and edit the msi file and modified the
"setPROFILE" Custom Action type 35 from the CustomAction Table from
\Macromedia\Shockwave Player\ to \Macromedia\Shockwave Player\
2. Deployed the new msi via SMS 2003 with advanced security, to a clean
test PC and a Clean test PC with a previous version of the player installed.
3. Tested both PCs by going to
http://www.macromedia.com/shockwave/welcome using IE. The Shockwave 10 Player
worked.
Vic
Product: Macromedia Shockwave Player -- Error 1606. Could not access
network location \Macromedia\Shockwave Player\.
I have used ORCA to create a transform file and change the SetPROFILE
custom action to numerous different locations by changing the
environmental variable to either TEMP, AppDataFolder or
ALLUSERSPROFILE\Macromedia\Shockwave Player\ but every time I deploy it
I get the same 1606 error.
Have I missed something? Others appear to have got it work by making
this change yet I cannot :(
Help please!
Thanks,
Stephen.
The nearest means of accomplishing Macromedia's intended funtion is to edit
the MSI in Orca (search msdn.microsoft.com for orca). Find the CustomAction
table on the left, then the row with Action setPROFILE on the right. Change the
Target column from \Macromedia\Shockwave Player\ to \Macromedia\Shockwave
Player\. I don't know why Macromedia didn't do that to begin with. Anyway,
click save and your MSI is usable.
TO MACROMEDIA:
This is why MSDN says explicitly: "Developers must avoid authoring components
that place files into one of the User Profile folders. These files would not be
available to all users in multi-user situations and could cause the installer
to permanently view the component as requiring repair." ... or just break your
installer in this case. If you need this functionality, it should be authored
into the Shockwave executable, not its installer.
Also... when will Macromedia provide an MSI-based Shockwave installer for
plugin-based browsers like they have for Flash?
Thanks,
S
This works very well, although I don't know what the implications of using the
Temp directory are. We clean out our temp directories at logoff, is there
anything that gets stored in this folder that needs to be saved between logons?
Also, I should point out that according to the license agreement Macromedia
provides for redistribution, which if you have the MSI installer for Shockwave
10 you probably agreed to at some point, says the following:
(b) Restrictions.
Licensee?s right to use the license in Section 2(a) above is limited by the
following restrictions:
...
Licensee must use the installers provided by Macromedia AS IS and may not
modify or alter the way the files are installed without express written
permission from Macromedia.
It seems Macromedia needs to tell us this is an okay solution -or- fix the
problem, immediately.
I am very happy that there are so many people in the community, which are able
to help. If we have to fix the installer by ourselves, because Macromedia is
unable (or unwilling) to do it (they had 6 months by now!!!), then i can live
with that. I have given up on getting help from the offical Macromedia Support
- just getting silly automated E-Mails which will not help anybody.
So, thanks to all again!
Oliver
THANKS!
I haven't had this problem, but usually this is caused by the
ARPSYSTEMCOMPONENT property somehow getting set to 1 (or probably any true
value). Maybe check the property table of your MSI?
[q][i]Originally posted by: [b][b]JohnPenrose[/b][/b][/i]
[Q][I]Originally posted by: [B][B]mhurley13[/B][/B][/I]
Well here is what I have done so far:
1) edited the msi file with ORCA and removed the Custom Action 35 from the
CustomAction Table. (couldn't do it with WISE as there is a reference in the
original MSI in one of the merge modules that is looking for a directory on one
of the packager's PCs...so it errors out)
2) Installed the "edited" MSI on a clean test PC...went to
http://www.macromedia.com/shockwave/welcome/ in IE and Macromedia Shockwave
Player was working with version 10 showing up in the window.
3) uninstalled Shockwave. Installed Shockwave version 8 on a clean PC. Ran my
"edited" MSI...went to http://www.macromedia.com/shockwave/welcome/ in IE and
Macromedia Shockwave Player was working with version 10 showing up in the
window.
I am not sure what the custom action is refering to. It looks like it is
referncing a Windows environmental variable for C:\Documents &
Settings\%username%\Application Data\
This is a problem with SMS 2003 deployments as this version of SMS uses the
system account to install software and the system account does not have a
C:\Documents & Settings profile for Shockwave's MSI to write to...this leads to
the 1603 errors.
I tried to change the "Target" information for teh custom action to use
[%ALLUSERPROFILE]\Application Data\Macromedia\Shockwave Player\ but the MSI
still errored out.
I am going to use the "edited" version for deployment...if anyone figures out
how to edit the MSI as referenced by the posting at AppDeploy.com please post.
I couldn't see how to add the information in the CustomAction 35 entry into the
Directory and RemoveFile tables as Wolfgang stated.
Thanks,
Marc[/Q]
Using Marc's method I was able to correct the "Error 1606. Could not access
network location \Macromedia\Shockwave Player\."
issue. I was deploying with Windows Server 2003 AD to a test OU that
continually failed with several MsiInstaller and UserEnv errors. Removing
Custom Action 35 with the ORCA editor did the job straight away.
I also noticed that there was no Yahoo Toolbar after the install and no user
input required after logging in and invoking the player with our Shockwave
enabled training website.
All good news.
Thanks for the write up Marc.
-=J=-
[/q]
:smile;
Thanks Agian,
Mike
Thanks for the fix. This worked for me.
Thanks
thanks
George
I have got it to work OK now.
Using ORCA I created a Transform and changed the SetPROFILE custom action to
"[%TEMP]\Macromedia\Shockwave Player\". After this I no longer got 1606 error,
but one about user shell folders'26'. I recognised this from another MSI I was
playing with and realised that I needed to perform a per-machine installation,
so I added to the Property table, ALLUSERS=1
The installation then completed successfully.
Hope it helps someone.
Thought I'd add that I'm using ZenWorks 4 to run the MSI, but that uses the
SYSTEM user too, so I assume it would work the same in SMS.[/q]
great! this works..
thanks =)
I have got it to work OK now.
Using ORCA I created a Transform and changed the SetPROFILE custom action to
"[%TEMP]\Macromedia\Shockwave Player\". After this I no longer got 1606 error,
but one about user shell folders'26'. I recognised this from another MSI I was
playing with and realised that I needed to perform a per-machine installation,
so I added to the Property table, ALLUSERS=1
The installation then completed successfully.
Hope it helps someone.
Thought I'd add that I'm using ZenWorks 4 to run the MSI, but that uses the
SYSTEM user too, so I assume it would work the same in SMS.[/Q]
Worked for me, thanx a million
That's the my same trouble with SMS2003 And Macromedia Shockwave Player in my
website http://www.3rb0.com... if there is any fix updates plz tell me to
download it
Thanks For Time
Paul.
http://www.killerbyteit.co.uk/index.html
tomorrow's solutions, today.
Dominic
http://www.Apps-R-Us.com
Buy and Sell Facebook Applications and other Social Network apps!http://]
Turnkey social network applications!
http://www.bigbargainseekers.com - http://www.installing-ceramic-tile.com -
http://attractabundanceeasily.com/unlock-secret-to-law-of-attraction -
http://www.cure-your-acne.com
I am very happy that there are so many people in the community, which are able
to help. If we have to fix the installer by ourselves, because Macromedia is
unable (or unwilling) to do it (they had 6 months by now!!!), then i can live
with that. I have given up on getting help from the offical Macromedia Support
- just getting silly automated E-Mails which will not help anybody.
So, thanks to all again!
I have seen a few other people posting about problems with facebook, however
I've yet to come across a fix.
You might want to start a new thread about the problem, you may get more help
that way.
Thanks again.
[hr]
http://www.siteverdict.com/ | http://www.siteverdict.com/# |
http://www.siteverdict.com/all_sites | http://www.siteverdict.com/3D |
http://www.siteverdict.com/advertising |
could be a server problem
Many Thanks !
Mike
I've seen good examples at this http://www.hungryflix.com site.
I would really like to see the players improved and well performed. I must
admit that i find it hard to use them while my antivirus is running but i am
not sure that this is your problem :)
[q][i]Originally posted by: [b][b]cgreggo[/b][/b][/i]
:disgust;
[HR]Thank you for contacting Macromedia Technical Support.
We understand that you are having issues installing Macromedia Shockwave
Player. It is possible there are settings in your Microsoft Active Directory
that is conflicting with the MSI installer. Other than the MSI installer that
is part of our player distribution e-mail, we suggest using the standalone
installer instead:
http://fpdownload.macromedia.com/get/shockwave/default/english/win95nt/10.1.0.01
1/Shockwave_Installer_Full.exe
Or you can try using the Flash-Shockwave MSI installer file below:
http://www.macromedia.com/go/fl_sw_installer
To test your Shockwave player plugin, please visit the link below:
http://www.macromedia.com/shockwave/welcome/
Please take note that there are a lot of factors that can affect the Shockwave
plugin. Again, we strongly suggest that you have the latest version of your
Internet browser installed as this usually fixes most plugin player related
issues.
We hope that you find the above information useful. Should you have further
concern, please feel free to contact us.
[HR]FYI - The combined installer installs FlashPlayer 7 with ShockwavePlayer
10.1, but at least it didn't error out.[/q]
Thanks again.
==============================================================
http://www.free-ringtones-maker.com - http://www.tabledemamy.be -
http://www.b2gamers.com - http://www.az-music-lyrics.com -
http://www.rapidshare-search.co.uk - http://www.4credit.com -
http://www.freevideodownloadz.com - http://www.bibles-for-the-world.com
Thanks,
http://online.any.tohttp://www.arcadedistrict.com
Any help is appreciated,
J. Harris
yea, same here i also tried this and getting the same error :-(
Asonte
http://www.asonte.com
It been a long time i think i am the only one that have this promblem