Author Topic: repair failed to start (SOLVED) (Read 18874 times)

beelectronics · « **on:** March 18, 2015, 12:00:45 pm »

Repair failed to start 4 times.

tweaking_ras.exe in the files folder is used to run repairs under the system account, make sure your antivirus isn't blocking it.

System Event Log has:
Tweaking Run As System 0001 (thru 0004) service failed to start due to the following reason:
The service did not respond to a start or control request in a timely fashion

Windows Server 2003 R2 SP2 64 bit
all-in-one repair v3.0.0

started in clean mode
made sure AVG was disabled

Any help would be appreciated.

Shane · « **Reply #1 on:** March 18, 2015, 12:14:49 pm »

Even with AVG disabled it looks like it still blocked it, did you make sure to run the repairs in safe mode with networking?

Shane

beelectronics · « **Reply #2 on:** March 18, 2015, 12:30:23 pm »

Before my original post, I had just done a clean boot.

But, now I've also started in safe mode with networking. I still get the same error.

I noticed you always say safe mode with networking. Is networking required? That's one of the problems I'm trying to fix. Networking is not working on this machine. I was trying to reset the registry entries to see if that might help.

I may completely uninstall AVG and see if that helps at all.

Thanks
Ken

PS
In safe mode, I can't see all of the repair window due to the lower resolution. I made it work, but it was a pain.

Shane · « **Reply #3 on:** March 18, 2015, 12:41:08 pm »

The safe mode with networking is more for windows 8, all other OS's older than 8 can use just normal safe mode. The reason why is the repair windows 8 component store will download and use windows updates to replace missing files, so you need to be online.

None of the other repairs need internet access, so no worries there

Shane

beelectronics · « **Reply #4 on:** March 18, 2015, 12:49:16 pm »

I uninstalled avg.

Turned off all non-Microsoft stuff in msconfig.

Started in safe mode with networking.

I still get the same error.

ugh!

Shane · « **Reply #5 on:** March 18, 2015, 12:55:15 pm »

Im sorry, I totally missed that you are trying on Windows 2003 server.

I was answering 20+ posts and so for so dang reason I spaced the version of Windows you are on.

The repairs are not testing on Windows 2003 server, and it might be that the windows 2003 server may not allow the program to make the service. Server OS have a lot of differences from the workstations, so I wouldnt recommend running the repairs on 2003.

What problems are you trying to fix on 2003?

Shane

beelectronics · « **Reply #6 on:** March 18, 2015, 01:41:58 pm »

I can't ping any nodes on the network. I can ping myself, but all others I get a destination not reachable.

Cable is plugged in and I get link lights on both sides.
Tried different port on the switch.
Tried different NIC.
ran netsh winsock reset and netsh int ip reset c:reset.log

The scariest of all...
If I try to browse the network in File Explorer, I get that I don't have access to the domain. But, this machine is the domain server!!

I had one drive of a mirrored pair go out and replaced it. When I restarted, I got this problem. The mirror resynced successfully.

I'm at a loss as to what happened or how to fix it.

If you can think of something to help, it would be much appreciated.

Shane · « **Reply #7 on:** March 18, 2015, 03:28:27 pm »

Ok try this, grab my technicians toolbox
http://www.tweaking.com/content/page/tweaking_com_technicians_toolbox.html

Direct download is here
http://www.tweaking.com/files/setups/tweaking.com_technicians_toolbox_setup.exe

(I havent tested this on 2003, but far as I know I am not using any APIs that are not in 2003 R2)

Open the program and go to network tools and then IP Address Scanner.

have it scan the network and let me know if ti works, should be fast. It is sending a ping to the Ip range and does them all at once so normally it takes about 3 or 4 secs to finish.

Let me know if it returns any results or not.

Shane

beelectronics · « **Reply #8 on:** March 19, 2015, 12:40:18 pm »

I can't get back to the server today.

But, I did try pinging several devices before. All I got was destination host unreachable except when I pinged the server's own address. That one pinged fine. That's why I tried the cable and a different port on the switch.

I'm stumped right now.

Shane · « **Reply #9 on:** March 19, 2015, 05:10:52 pm »

Thats why I want to try the toolbox and see if it works, it uses a different API and so if it works and the ping in cmd.exe doesnt then that gives me an idea where to start looking. But if the toolbox also fails using the api then that tells me it is most likly something corrupt with the network registry keys, which if that is the case then totally yanking the network card and drivers out of device manager, running all the network reset commands and rebooting should get windows to write those registry keys fresh again.

Of course "should" is the magic word lol

Shane

beelectronics · « **Reply #10 on:** March 20, 2015, 12:05:59 pm »

I ran technician's toolkit and the only IP to respond was the server's own.

So, I did like you mentioned in your post: uninstalled the NIC (can't physically remove it, it's integral to the MB), ran netsh int ip reset and netsh winsock reset again, rebooted.

It got a DHCP address!! But that just lasted long enough to get the address.

As soon as I noticed the correct address, I tried pinging the router and got the destination unreachable message again. Tried releasing and renewing the IP address but it failed.

(FYI since this is a server and a DC, the IP is normally static. It just reverted to DHCP when I uninstalled everything.)

Thanks for your continued help.

Shane · « **Reply #11 on:** March 20, 2015, 12:14:29 pm »

I am heading out for the weekend, taking my 10 year old to the observatory, so I wont respond till monday.

But before I go I wanted to reply

Check the event viewer and see if anything is logged about the network, any errors or anything.

Check the services and make sure the server and workstation services are running. Also make sure the firewall is off, on a server it is normally off, if you like it on lets turn it off for testing.

I have been on servers where the server firewall would stop a lot of things even when it was set to allow them through.

I know there are some other services that need to be running for the network to work like normal, lanman and others, I just cant think of all of them at this moment.

Also, just to cover all the bases, if you have another network card you can use just as a test, install one and see how it does. That would at least confirm if the onboard nic and the drivers are good or not. If it happens to a totally different nic and drivers then we can mark that off the list as a possible cause

Basically at this point it is a process of elimination

Shane

beelectronics · « **Reply #12 on:** March 20, 2015, 12:31:04 pm »

I installed a USB wireless card and that acted the same way. I'll check more and report back.

Have a great weekend! Spend as much time with your kids as you can! I remember those days and wish I had been more available.

Shane · « **Reply #13 on:** March 23, 2015, 01:46:19 pm »

How has the testing gone so far?

Shane

beelectronics · « **Reply #14 on:** March 24, 2015, 09:11:33 am »

I'm happy to report I fixed the network problem.

As you probably know, there is a hack that will allow you to uninstall the TCP/IP protocol. And, by uninstalling and reinstalling TCP/IP, all the associated registry keys are rebuilt. So, I did that and now my network seems to be working okay.

Thanks for all your help and your great products!

I hope you had a wonderful weekend with your son!

Ken

Shane · « **Reply #15 on:** March 24, 2015, 03:04:12 pm »

Good to hear

So it was registry keys that needed to be rebuild.

What process did you do? Reason why I ask is I want to replicate it.

I will load up vmware, have windows in it running, yank tcp/ip, then take a registry snap shot, then reinstall tcp/ip and do another reg snap shot and then look for the changes.

That way I can find what it added, removed, changed and see if any of it is able to put into a automated repair

Shane

beelectronics · « **Reply #16 on:** March 25, 2015, 08:32:56 am »

Quote

1.Restart the domain controller.
2.When the BIOS information appears, press F8.
3.Select Directory Services Restore Mode, and then press ENTER.
4.Use the Directory Services Restore Mode password to log on.
5.Click Start, and then click Run.
6.In the Open box, type regedit, and then click OK.
7.Locate the following registry subkeys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

8.Right-click each key, and then click Delete.
9.Click Yes to confirm the deletion of each key.
10.Close Regedit.
11.Locate the Nettcpip.inf file in %winroot%\inf, and then open the file in Notepad.
12.Locate the [MS_TCPIP.PrimaryInstall] section.
13.Edit the Characteristics = 0xa0 entry and replace 0xa0 with 0x80.
14.Save the file, and then exit Notepad.
15.In Control Panel, double-click Network Connections, right-click Local Area Connection, and then select Properties.
16.On the General tab, click Install, select Protocol, and then click Add.
17.In the Select Network Protocols window, click Have Disk.
18.In the Copy manufacturer's files from: text box, type c:\windows\inf, and then click OK.
19.Select Internet Protocol (TCP/IP), and then click OK.

Note This step will return you to the Local Area Connection Properties screen, but now the Uninstall button is available.
20.Select Internet Protocol (TCP/IP), click Uninstall, and then click Yes.
21.Restart your computer, and then select Directory Services Restore Mode as mentioned in steps 2 - 4.
22.In Control Panel, double-click Network Connections, right-click Local Area Connection, and then select Properties.
23.On the General tab, click Install, select Protocol, and then click Add.
24.In the Select Network Protocols window, click Have Disk.
25.In the Copy Manufacturer's files from text box, type c:\windows\inf, and then click OK.
26.Select Internet Protocol (TCP/IP), and then click OK.
27.Restart your computer.

On non-server OS's you can ignore the part about going into Directory Services Restore Mode. Everything else is the same.

HTH
Ken