Hi,
I use Sunjammer Dll for controlling access to Windows services:
http://nsis.sourceforge.net/How_do_I_start/stop/create/remove/check_a_service
However there seems to be compatability issues with Windows 2003 Server
Any ideas??
Nniol
Windows 2003 Server & Services
13 posts
Dll HTML Link
http://nsis.sourceforge.net/How_do_I_start/stop/create/remove/check_a_service
http://nsis.sourceforge.net/How_do_I_start/stop/create/remove/check_a_service
nsis.sourceforge.net/How_do_I_start/stop/create/remove/check_a_service
Untick "Automatically parse URLs" when you post and the URLs will not be hidden.
As for the problem itself, what exactly do you mean by compatability issues and do the other solutions exhibit the same behavior?
As for the problem itself, what exactly do you mean by compatability issues and do the other solutions exhibit the same behavior?
With some versions of WIndows 2003 Server it works, and with others it doesn't......
But only on 2003, just wondering if Microsoft have changed their code or something
NNiol
But only on 2003, just wondering if Microsoft have changed their code or something
NNiol
And what exactly do you mean by not working? Is the service created but not started? Does it crash when creating the service? Does it set the wrong name? And what about the other available solutions for service creation?
it is querying whether a service exists...
On all other computer it returns that the service installed by installer A is there, but on Windows 2003 the same servie returns not present
On all other computer it returns that the service installed by installer A is there, but on Windows 2003 the same servie returns not present
Nniol, I can't help you unless you start giving me some more details. What is querying whether a service exists? What about other methods of service creation?
The problem is within the DLL, the DLL runs fine and doesn't crash it just returns a wrong result...
The service is started and running. The call from within NSIS is:
services::IsServiceInstalled "$ServiceKeyName"
Where $ServiceKeyname is
StrCpy $ServiceKeyName "Office Document Server"
ON all other servers this works fine and returns Yes if installed and no otherwise, however on Windows 2003 it no even if the service is there.
The service is started and running. The call from within NSIS is:
services::IsServiceInstalled "$ServiceKeyName"
Where $ServiceKeyname is
StrCpy $ServiceKeyName "Office Document Server"
ON all other servers this works fine and returns Yes if installed and no otherwise, however on Windows 2003 it no even if the service is there.
And how is the service created?
From a Windows executable
something like
ODSServer.exe -install
something like
ODSServer.exe -install
Are you sure it doesn't use another name on Windows 2003 or different set of privileges? It's possible, though unlikely, that it refuses the query privilege from some users.
OK...
Will ask the App. Devs about this,
Thank you
Will ask the App. Devs about this,
Thank you