Computer works, but no video

**GeorgeB** · 04-16-2013, 01:58 PM

Originally Posted by Nutmeg

I still saying its the ram. How many video inputs does it have on the computer?

Just one. However, I dont think I was giving the server enough time to boot up, because the others took a several minutes, before I saw anything on the monitors.

**Nutmeg** · 04-16-2013, 03:23 PM

Yes, servers can take up to anywhere from 3 to 5 mins to boot up.

**GeorgeB** · 04-16-2013, 05:11 PM

Originally Posted by Nutmeg

Yes, servers can take up to anywhere from 3 to 5 mins to boot up.

I found out the hard way lol.

Just wish I knew how serious the little error was that I seen on every one of them lol

**AuburnEwaste** · 04-16-2013, 07:00 PM

What error are you getting? Servers will freak out about little things, like not having the correct number of fans connected.

**GeorgeB** · 04-16-2013, 07:30 PM

Right before going into Windows Server 2003, they all say "At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details" Is this a major issue, or something to be easily fixed by someone with more tech knowledge then myself?

Full article at Scrap Metal Forum: http://www.scrapmetalforum.com/day-l...#ixzz2QfjcRLP6

**AuburnEwaste** · 04-16-2013, 07:58 PM

These are software issues and should not be a big deal. Most of the time if you can at least get it to boot to the BIOS you are in good shape.

**ITBoneyard** · 04-16-2013, 10:31 PM

Unless you have the server in the EXACT configuration that it was in prior to removal, you'll get those error messages as it tries to find those components that used to be attached to it. Unless there are fatal errors being reported at boot, you are usually good to go.

**Bear** · 04-16-2013, 11:16 PM

most likely it isn't locating the network it's been programmed to tag in to

**GeorgeB** · 04-16-2013, 11:53 PM

Originally Posted by AuburnEwaste

These are software issues and should not be a big deal. Most of the time if you can at least get it to boot to the BIOS you are in good shape.

Originally Posted by ITBoneyard

Unless you have the server in the EXACT configuration that it was in prior to removal, you'll get those error messages as it tries to find those components that used to be attached to it. Unless there are fatal errors being reported at boot, you are usually good to go.

Originally Posted by Bear

most likely it isn't locating the network it's been programmed to tag in to

Thanks everyone. That will give me some leveraging power, if they try and under cut the deal for that reason.

**drozenski** · 04-17-2013, 12:52 AM

Originally Posted by GeorgeB

Right before going into Windows Server 2003, they all say "At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details" Is this a major issue, or something to be easily fixed by someone with my tech knowledge then myself?

Full article at Scrap Metal Forum: http://www.scrapmetalforum.com/day-l...#ixzz2QfjcRLP6

This is not a major issue. It can be any number of non critical services. Find out what service didnt run.

**GeorgeB** · 04-17-2013, 08:14 AM

Originally Posted by drozenski

This is not a major issue. It can be any number of non critical services. Find out what service didnt run.

No offense, but that is probably like a walk in the park for you, and like brain surgery for me lol.

If it was a regular computer, that would be different, but this is the first time, I have ever dealt with servers. I am just glad, they are small.

Although, I do have 3 or 4 of the long rectangular ones that goes in the big server towers. Problem is, I have no way of testing them.