I just got my brand new Philips SRM7500 remote today and got an ugly surprice when I tried to install the software . . . I can't!! I'm running Vista Home Premium (32-bit) and when I'm trying to install the "MediaControl" software I get these error messages:
Registration of ”MediaControl” failed: execution of ”net start MediaControl” returned 2
Error 1904. Module C:Program Files\Philips\MediaControl\4.0.5.8\LMRegister.dll failed to register. HRESULT -2147467259. Contact your support personnel.
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action OnInstall, location: ...\LMControl.exe, command: LMService.install VIEWRN= VersionInfoURL=http://update.homecontrol.philips.com:8080/update/srm75...
I tried to install the software on a machine running XP without any problems, so I contacted Philips and they just gave me a link to a newer software. It didn't solve my problem. Does anyone know how I can install the software?
Jeff - Moderator:Right click on the installer and choose "Run as administrator"
Thanks, but I have tried this, and it doesn't work. Same problem. I don't understand it. There's no problem installing on a XP machine, but it will not install on my Vista Home Premium machine. The installer should work on Vista.
Do you have UAC (user account control) enabled? If so try disabling it to do the install and then turn it back on afterwards.
Thanks for all the advice guys. I've tried them all now and it still doesn't work. The compatability mode and disabling UAC didn't make any difference. Neither did installing Microsoft Visual C Redistributable Package SP1. :(
The Philips SRM7500 is Vista compatible so I don't understand why it woun't install. I'm sure it's not the installer that's causing the problem, so it must be my system. It's almost a clean install, not more than a month old. I'll try on another Vista machine later today to see if it's a Vista problem.
There are no doubt other things going wrong with this install but the error message Registration of ”MediaControl” failed: execution of ”net start MediaControl” returned 2 seems to suggest that the MediaControl service cannot be started. The command 'net start' is used to start Windows services.
Do you have a Media Control service listed in services?
Do Philips offer any support at all for this software?
stepfaul: There are no doubt other things going wrong with this install but the error message Registration of ”MediaControl” failed: execution of ”net start MediaControl” returned 2 seems to suggest that the MediaControl service cannot be started. The command 'net start' is used to start Windows services. Do you have a Media Control service listed in services? Do Philips offer any support at all for this software?
I don't have a Media Control listed in services.
I have contacted Philips to get support. They only gave me a link to a never version of the MediaControl software. The same problem occurs with the never software. The supporter said that the remote should run in Vista without any problems . . . that may be so, but how am I supposed to use the remote when I can't install the driver? I've emailed Philips support yesterday with the error messages enclosed, but I haven't heard from them yet.
I hope you hear from Philips soon, in and amongst the install files do you have a file with the extension .msi? You could try browsing to this file, right clicking the file and then selecting the repair option, this should repair the current install.
If admin rights are an issue try running the command line box up as administrator and then browsing to the .msi file via the command line and doing a repair from there.
If you are running an .msi file from the command line there are a shed load of command line options available to help you troubleshoot the install -
------------------------------------------------------------------------------------------------
Windows ® Installer. V 3.01.4000.1823
msiexec /Option <Required Parameter> [Optional Parameter]
Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]
---------------------------------------------------------------------------------------------------------------
To install an .msi package from the command line follow this syntax - MSIEXEC /qb /i c:\netfx.msi
You will see that the /qb and /i are switches which are explained above and the c:\netfx.msi is the actual msi file in this instance.
The install file is a single .exe file.
I just tried to install the software on another Vista machine (Ultimate), and the same problem occurs here. It can't be true that I'm the only one experiencing difficulties installing the Philips SRM7500 remote on a Vista system - and now on two different computers. I really hope Philips has a solution. No problems installing on my XP laptop.
When you click on the single .exe file the contents are probably extracted to a temp directory, it is in this temp directory that you may find the install files such as .msi etc.
I have no more advice I am afraid other than to just double check that permissions and rights restrictions are not the cause of your problem. You are probably logged on with an administrator account by default with your XP install so permissions would never normally be a problem but with Vista the case is different and it may be that the install does not have permissions to create such things as new services or to write to registry locations.
I have to say that I encountered a similar problem with the latest Tom Tom software, I tried everything to get it to install on two Vista boxes and could not get it to work, I then tried installing the software on an XP machine and all was fine and dandy, in this example though permissions were not an issue.
stepfaul: When you click on the single .exe file the contents are probably extracted to a temp directory, it is in this temp directory that you may find the install files such as .msi etc. I have no more advice I am afraid other than to just double check that permissions and rights restrictions are not the cause of your problem. You are probably logged on with an administrator account by default with your XP install so permissions would never normally be a problem but with Vista the case is different and it may be that the install does not have permissions to create such things as new services or to write to registry locations. I have to say that I encountered a similar problem with the latest Tom Tom software, I tried everything to get it to install on two Vista boxes and could not get it to work, I then tried installing the software on an XP machine and all was fine and dandy, in this example though permissions were not an issue.
I enabled and logged in the Administrator user account, and the same problem here. How do I ensure that I (and the install program) have alle the right permissions?
If you have enabled and logged in with the administrator account then permissions should not be an issue.
Did you install this software at the very start with administrative rights on both Vista boxes? If not then as a last ditch attempt I would use system restore to restore your Vista machine to a point before you installed the Philips software and then try and install the software again whilst logged on as adminstrator. Failing that you will need to speak to Philips support again.
Thanks stepfaul . . . a system restore didn't solve it :(
I'll have to contact Philips support again.