Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Newbie: Weird service problem 1

Status
Not open for further replies.

Stevehewitt

IS-IT--Management
Jun 7, 2001
2,075
GB
Hello everyone!

Firstly, please bare with me. I'm very new to ISA server so if the answer is staring me in the face don't be suprised!!! ;-)

ISA server was running fine for the first week after installation. For no apparent reason, the ISA Server control service (SCS) won't start, yet all other related services (e.g. firewall, proxy etc.) will start fine. When I try to manually start SCS I get the following:

Windows could not start [SCS] control on local machine. blah blah blah (look in event log, contact vendor) ...service-specific error code 278540.

Event log just repeats the above message.

From then onwards users couldn't surf the net, and if I tried to restart any other ISA related services they just stopped as SCS wasn't running. The interesting bit is that if I stop Routing and Remote Access Service, I can start SCS with no problems, and then turn routing back on. When I turn RRAS back on the SCS stops again with no error (unless I try to restart)

PLEASE help me. I can't find it in the MS KB or any help files.

Many Thanks, Steve Hewitt
Systems Manager
 
Steve,

did you ever got any solution, or did you find out what it caused?

paul
 
Hi,

I don't really know. I've tried playing with the services such as ICS and the other ISA services and its sort of gone away. Just playing with it. I thought that ISA was a NAT gateway - maybe it is, but it seems to be acting and using a ICS service!!!

Any ideas? Steve Hewitt
Systems Manager
 
Well, this error is repeatable, so I am going to test it on another box to see if has the same behaviour. After configuring the ISA server as VPN server (client requests), the RRAS service is started. Then when I would restart the ISA control, I would get the 278540 error and this in the application log:

-----
Microsoft ISA Server Control Service failed to start because the operating system service Routing and Remote Access is already running. To fix this problem use ISA Server setup to reinstall ISA.
-----

Some other entries in the app log showed it has to with NAT. I am going to ask on the MS forum about this issue. BTW stopping RRAS, starting ISA and then starting RRAS again works, but this is ridiculous.

paul

 
The problem is that when you once install RRAS (and I even disabled it later!) and after that ISA, the depency of the RRAS service is not adjusted, even when yo use the wizards. First should start ISA, then RRAS. On you can find a script to adjust depedency automaticly.
 
Hi Paul,
I followed your advice using script to obtain the correct dependancy, but I'm going on having problems, in particular
i have always to stop RRAS service to let 'ISA firewalling' start and then (even if ISA allow rules are OK) I can "ping" only my LAT interface and not my external interface even if ISA has been shut down.
With or without RRAS i have to insert my WAN interface into LAT network to ping my interface even if ISA services are not working.

Do you know what is happening ?

Thank you in advance

Regards
 
Steve,

I had this problem this morning after our server had to be restarted. I found that the RRAS service mysteriously forgot it was supposed to depend on the ISA Server Control service.

The only thing that has changed on this server was I installed the H.323 Gatekeeper a few days ago, and in doing so, was required to insert the ISA CD.

To manually correct this problem, first check what the current dependencies are, by opening the Services MMC console, double-click on the Routing and Remote Access service, clicking on the Dependencies tab, if you do not see Microsoft ISA Server Control you'll need to follow the steps below.

Start REGEDT32, look in HKEY_LOCAL_MACHINE tree pane, expand SYSTEM, CurrentControlSet, Services and then RemoteAccess.

Double-click on DependOnService in the data pane (if you don't see the data pane, select View / Tree and Data from the menu).

A Multi-String Editor window should appear, insert the line isactrl above RpcSS, then click OK.

Verify that the changes have been made by opening the Services MMC console again and checking on the Dependencies tab, Microsoft ISA Server Control should now appear on the list.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top