PXE server stopped working

maeron · 01-24-2007, 09:01 AM

I get the following error message (more exaclty see included file):

The PXE Manager Service has not connected with the DS server yet.

I have reinstalled the PXE Manager and PXE server several times but still get this error.

Anyone seen this?

What to do ?

/Martin

maeron · 01-24-2007, 09:59 AM

I have now tried Altiris KB3724 and KB29527 and there no luck yet.

Same problem

/Martin

maeron · 01-24-2007, 10:10 AM

Is there something in the SQL database that does something with the PXE server?

/Martin

stanyb · 11-13-2007, 11:28 AM

Dear, I'm having the same issue at the moment.
Did you found a solution in your case?

thx, Stany.

Ethan · 11-13-2007, 11:35 AM

This isn't really a good solution, but we have this problem sporadically and the only ways I've been able to resolve it are to stop all PXE and DS services and restart them or to restart the machine.

stanyb · 11-13-2007, 11:55 AM

I already tried this but it didn't solve the problem.

Thx anyway.

Ethan · 11-14-2007, 10:55 AM

Have you tried opening the task manager, going to the processes tab and ending the pxemgr.exe process? You'll need to show processes from all users checked to see it most likely. Once that's done, try starting the PXE manager service manually and then opening the configuration utility.

stanyb · 11-15-2007, 04:51 AM

Tried but still the same; PXE config won't open, and services are started.

andykn · 11-15-2007, 06:12 AM

The theory is that you can only have one PXE Manager open at a time. So if you try and open a second copy of PXE Manager from another place, the second copy will not open.

I think that PXE Manager knows if anorther copy is open by looking in the PXEManager.ini file in the PXE folder of the express share.

It may be that a previous copy of PXE m,anager did not correctly write to this file to say it was closing. I'm afraid I don't know where or how this is written, but that would explain how the lock survives a reboot. There is a PXE.ini file too.

andykn · 11-15-2007, 06:16 AM

Quote:

Originally Posted by andykn

The theory is that you can only have one PXE Manager open at a time. So if you try and open a second copy of PXE Manager from another place, the second copy will not open.

I think that PXE Manager knows if anorther copy is open by looking in the PXEManager.ini file in the PXE folder of the express share.

It may be that a previous copy of PXE m,anager did not correctly write to this file to say it was closing. I'm afraid I don't know where or how this is written, but that would explain how the lock survives a reboot. There is a PXE.ini file too.

Although, having looked in PXEManager.ini, "CurrentLockHolder" would be a good bet. If you have no copies of PXE Manager open, delete the two CurrentLock... entires.

mack_jason · 07-23-2009, 12:57 PM

Did anyone find a resolution to this problem? I'm having the issue now and have read through all the KBs and tried what has been suggested and still no luck. I did have this up yesterday and resolved it by randomly stopping and starting services.

drinking12many · 07-23-2009, 03:47 PM

Ive seen this happen a couple different ways.

1. Changed IP address and the appropriate ini files werent updated(requires reboot) pxmanager, pxe, rpc, and default.cfg
2. Database permission error if its user specific
3. is if the service account isnt a server admin which will create the above database permission error unless you have adjusted your db permissions accordingly.

For us usually one of these fixes it.

mack_jason · 07-23-2009, 07:45 PM

I don't see how this could be possible but hay it's PXE. I resolved this issue by going to the PXEMANAGER.ini looking at the section that references the datastore and changing it from the UNC patch to the local path of D:\program files\altiris\deployment server\express\pxe (I think that's the right path)

Anywhay, after I changed this I was able to open the PXE boot disk creator.

drinking12many · 07-24-2009, 10:02 AM

Glad you solved it.

Pxe ties into the DB, there are entries for it in the tables and it also has to look into the DB to see if a machine is already on the DS etc thats why it can cause you probs.

Brandon · 07-24-2009, 11:06 AM

I may have to try that path change, but in my experience PXE has always failed. PXE is in need of a major update. This problem happens to tons of people so I don't know why Altiris can't seem to make a more reliable version.

mack_jason · 07-24-2009, 02:29 PM

I would also like to add that this is 6.8 SP2 so hopefully PXE is more stable in 6.9 SP2