PXE-E53 No boot filename received

  • Thread starter Thread starter notagirrafe
  • Start date Start date
N

notagirrafe

I started receiving this when trying to boot a PXE client after doing some
long overdue updates on the server (SP2 primarily).

I found that the service "Remote Installation" service BINLSVC (tcpsvcs.exe)
was not running, but when I try to start it it fails withe Error 127:The
specified proceedure could not be found. In teh event log it is error 7023
from "Service Control Manager". Checking properties, the .exe is in place as
expected.

I'm at a loss as to what to check next and would appreciate any advice (oh
and I did restart the server - twice) and run a full Sophos anti-virus scan.

Any ideas would be appreciated.

Dave
 
Howdie!

notagirrafe schrieb:
> I started receiving this when trying to boot a PXE client after doing some
> long overdue updates on the server (SP2 primarily).
>
> I found that the service "Remote Installation" service BINLSVC (tcpsvcs.exe)
> was not running, but when I try to start it it fails withe Error 127:The
> specified proceedure could not be found. In teh event log it is error 7023
> from "Service Control Manager". Checking properties, the .exe is in place as
> expected.

In Windows Server 2003 SP2, RIS got replaced by its successor, WDS
(Windows Deployment Services). WDS was added under
"Start->Settings->Control Panel" - so if you start the wizard and run
through it and afterwards set the (legacy RIS-)BINLSVC to stop and only
run manually, things should be working again.

cheers,

Florian
--
Microsoft MVP - Windows Server - Group Policy.
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
 
Thanks for this Florian.

You are of course correct and that is my problem, now all I need to do is
get WDS to work.

Thanks again.


"Florian Frommherz [MVP]" wrote:

> Howdie!
>
> notagirrafe schrieb:
> > I started receiving this when trying to boot a PXE client after doing some
> > long overdue updates on the server (SP2 primarily).
> >
> > I found that the service "Remote Installation" service BINLSVC (tcpsvcs.exe)
> > was not running, but when I try to start it it fails withe Error 127:The
> > specified proceedure could not be found. In teh event log it is error 7023
> > from "Service Control Manager". Checking properties, the .exe is in place as
> > expected.
>
> In Windows Server 2003 SP2, RIS got replaced by its successor, WDS
> (Windows Deployment Services). WDS was added under
> "Start->Settings->Control Panel" - so if you start the wizard and run
> through it and afterwards set the (legacy RIS-)BINLSVC to stop and only
> run manually, things should be working again.
>
> cheers,
>
> Florian
> --
> Microsoft MVP - Windows Server - Group Policy.
> eMail: prename [at] frickelsoft [dot] net.
> blog: http://www.frickelsoft.net/blog.
>
 
Hate beating a dead horse....It was dead when I got here I swear!
I did run the WDS Manually.
It worked.... We moved (changed IP schemes)..
Getting the error again.
Added the TFTP in the DHCP scope options did not help.
Was not sure what the bootfile should be in the DHCP scope... I did Binsl.
Still getting error.
Any Ideas?

"notagirrafe" wrote:

> Thanks for this Florian.
>
> You are of course correct and that is my problem, now all I need to do is
> get WDS to work.
>
> Thanks again.
>
>
> "Florian Frommherz [MVP]" wrote:
>
> > Howdie!
> >
> > notagirrafe schrieb:
> > > I started receiving this when trying to boot a PXE client after doing some
> > > long overdue updates on the server (SP2 primarily).
> > >
> > > I found that the service "Remote Installation" service BINLSVC (tcpsvcs.exe)
> > > was not running, but when I try to start it it fails withe Error 127:The
> > > specified proceedure could not be found. In teh event log it is error 7023
> > > from "Service Control Manager". Checking properties, the .exe is in place as
> > > expected.
> >
> > In Windows Server 2003 SP2, RIS got replaced by its successor, WDS
> > (Windows Deployment Services). WDS was added under
> > "Start->Settings->Control Panel" - so if you start the wizard and run
> > through it and afterwards set the (legacy RIS-)BINLSVC to stop and only
> > run manually, things should be working again.
> >
> > cheers,
> >
> > Florian
> > --
> > Microsoft MVP - Windows Server - Group Policy.
> > eMail: prename [at] frickelsoft [dot] net.
> > blog: http://www.frickelsoft.net/blog.
> >
 
Back
Top