I've installed the CF10 beta with IIS 5.1 on Windows XP Pro. The CF10 Application Server service will not start.
Is there anything I can do? Or is this by design?
Thanks.
Carl,
Trying to start CF from the command line yielded this error message:
"This application failed to start because msvcr71.dll was not found. Re-installing the application may fix this problem."
I've even tried formatting the drive, reinstalling Windows and CF, but I still can't start the service.
Any other suggestions? I'm going to try to run it as a standalone server and hopefully that'll do it.
Thanks.
Same exact thing happened to me. I installed CF10 beta on a 32-bit Windows 7 Guest OS inside of MS Virtual PC 2007 sp1 and the CF application service would not start. I ran the cfstat.bat file directly from a command prompt and received the same exact warning: MSVCR71.dll could not be found. I did a Google search for MSVCR71.dll and it brought me to: http://www.addictivetips.com/windows-tips/fix-msvcp71-dll-and-msvcr71- dll-missing-error-in-windows-7/
I downloaded the dll and placed it in the Windows\System32 folder. I then went to services and started the CF Application server. I then completed setting up my CF10 beta installation without any additional issues.
Same exact thing happened to me. I installed CF10 beta on a 32-bit Windows 7 Guest OS inside of MS Virtual PC 2007 sp1 and the CF application service would not start. I ran the cfstat.bat file directly from a command prompt and received the same exact warning: MSVCR71.dll could not be found. I did a Google search for MSVCR71.dll and it brought me to: http://www.addictivetips.com/windows-tips/fix-msvcp71-dll-and-msvcr71- dll-missing-error-in-windows-7/
I downloaded the dll and placed it in the Windows\System32 folder. I then went to services and started the CF Application server. I then completed setting up my CF10 beta installation without any additional issues.
I wanted to confirm that the same held true for Windows Server 2003 32 bit. I got the same error and placing the dll in the error message in the Windows\System32 folder worked. It started up just fine.
HTH someone.
North America
Europe, Middle East and Africa
Asia Pacific