1 Topic by Alliance.Ace.Pilot (edited by Alliance.Ace.Pilot 2007-10-03 01:36:52)

  • Registered: 2007-09-28
  • Posts: 45

Topic: PB:IMPORTANT:RESTRICTION

I'm getting kicked from any 1.1 server I join within minutes as a result of this error:

PB:IMPORTANT:RESTRICTION:: Service Communication error - failed to initialize PNKBSTRB.EXE

I ran PBsvc and confirmed that there were exceptions in my firewall for both.

All punkbuster versions are up to date.

I checked Windows services and verified that Punkbuster A and Punkbuster B load automatically and both services were already started.

I ran FS 1.1 and again got:

PB:IMPORTANT:RESTRICTION:: Service Communication error - failed to initialize PNKBSTRB.EXE

So I checked services and Punkbuster B was gone.

I ran PBsvc again and confirmed everything was good to go.

Started FS 1.1 and quickly alt tabbed to services and refreshed the list to discover Punkbuster B was gone.

For some reason when I load FS1.1 the Punkbuster B not only stops but disappears all together from my Services list as though it were never there..


Imperial Sabotage?     Maybe...

Sith Mind Trick?     Perhaps...


REALLY stinkin frustrating?!?     Indeed.

http://static1.filefront.com/images/personal/s/SpaceEvents/95453/ebkphqyboc.thumb250.jpg
  • Markus
  • Markus
  • FirstStrike Tester
  • Offline
  • From: Zwolle [NL]
  • Registered: 2006-01-02
  • Posts: 1,299

Re: PB:IMPORTANT:RESTRICTION

using PBsvc.exe uninstall pb.
then install it again with the same PBsev.exe
pressing reinstall doesnt work to good with PB.
also if search for "pnkbstr" you wil find more then one A or B.exe. to be on the save side, put them all in your firewall exception list

Beta: Latin for "still doesn't work".
http://www.anime-planet.com/images/users/signatures/SirMarkus.jpg

Markus's Website

  • Registered: 2007-09-28
  • Posts: 45

Re: PB:IMPORTANT:RESTRICTION

Thanks... I've been at this problem for hours now and it's got me stumped.

Somehow installing Patch 1.1 didn't jive with my PunkBuster. 

Consequently, I'm having the same problem with regular BF 2142. 

I've read probably a dozen forum posts about this exact same problem one of which was about 15 pages and included the longest Hijack This log I've ever seen... 

I don't know.  Basically pnkbstrb just goes kerplunk and disappears no matter what I've tried.  I even made sure all the relevant registry entries were removed manually.  Clean uninstall (using multiple techniques) reboot and then a clean install (using multiple combinations as well i.e. using pbsetup first and selecting BF2142, updating then running PBsvc etc....)

Long story short - it's not working. lol

http://static1.filefront.com/images/personal/s/SpaceEvents/95453/ebkphqyboc.thumb250.jpg

4 Reply by Alliance.Ace.Pilot (edited by Alliance.Ace.Pilot 2007-10-03 05:22:13)

  • Registered: 2007-09-28
  • Posts: 45

Re: PB:IMPORTANT:RESTRICTION

Just got this out of a pnkbstr log as a result of the search on pnkbstr...

PnkBstrB.exe does not contain a valid certificate; Load denied.

The plot thickens...

http://static1.filefront.com/images/personal/s/SpaceEvents/95453/ebkphqyboc.thumb250.jpg
  • Markus
  • Markus
  • FirstStrike Tester
  • Offline
  • From: Zwolle [NL]
  • Registered: 2006-01-02
  • Posts: 1,299

Re: PB:IMPORTANT:RESTRICTION

hmm then i would suggest sending a mail to the PB support team, cause im at a loss here

Beta: Latin for "still doesn't work".
http://www.anime-planet.com/images/users/signatures/SirMarkus.jpg

Markus's Website

  • Registered: 2006-10-10
  • Posts: 333

Re: PB:IMPORTANT:RESTRICTION

Most likely you are trying to join a server which hasn't patched to version 1.1 yet. Try the BOC server. They have patched and you should be fine. Regarding the other servers, you will have to wait untill they are patched.

www.roguetribe.com
http://i2.photobucket.com/albums/y41/JimWalker_TAW/JimWalker_Sig.jpg

<RT> Jimwalker-NL's Website

  • Registered: 2007-09-28
  • Posts: 87

Re: PB:IMPORTANT:RESTRICTION

Also, do as others said and delete the PB files, run PBSetup.exe, and then make sure to do a system restart.   I had the same issue last weekend with PB and those are the steps that actually cleared it up for me.  The restart may be critical, as I did everything but restart and it didn't work.  However, after the restart it was fine and has been since.

http://www.bloodycompany.net/images/firststrikesig.jpg

Bloedig_Vader's Website