Hi
It also happens on XP. At the moment for example, I have a machine where Cassini does not start on XP. I am leaving this machine in this state just in case I will need it because it is rare, but it happens.
I have also had problems on Server 2003 Operating systems.
How can I debug this? Event viewer shows me nothing on this machine.
I do not tell the customers to remove the original Cassini service that we package in our installation. I just tell them to download and install your webserver from Ultidev website. probably this install might add some Dll's or files that are missing? making our Cassini service start with no problems. This was my reasoning.
Then after they have download this, they are able to go to Our Cassini service instance and they are able to start it. After this step, the service starts and remains started, thanks to the Ultidev package.
This is the list of components we install:
1 - UltiDevCassinWebServer2.exe
2 - UltiDevCassinWebServer2a.exe
3 - UltiDevCassiniHttpRequestProcessor2.0.dll -- we add this dll to windows assembly folder
4 - UltiDevCassiniServerConfiguration.dll
5 - Interop.IWshRuntimeLibrary.dll
6 - Interop.NetFwTypeLib.dll
7 - UltiDevCassinWebServer2a.InstallState
8 - UltiDevCassinWebServer2a.exe.config
9 - CassiniMetabase.xml -- in Application data folder
* Cassini Service runs under Local System account
Thanks for your quick update on this.
Any help on this would be greatly appreciated.
Thanks and regards
Nicky