PQR - Rotation Bot

[warlock2000]

Hmm no luck on that either. Even when I delete WoW-64 completely and run the launcher manually in 32-bit without it, I get the battlenet error on trying to login. Doing some more digging.

[Master34]

Hmm no luck on that either. Even when I delete WoW-64 completely and run the launcher manually in 32-bit without it, I get the battlenet error on trying to login. Doing some more digging.

same for me... im pretty sure you can log in 64 bit, like me...but when the game is in 32bit (84x) we got error 114... and we ****ed since pqr need 32 bit version of the game... any suggestions to fix that?

[jh16]

Hmm no luck on that either. Even when I delete WoW-64 completely and run the launcher manually in 32-bit without it, I get the battlenet error on trying to login. Doing some more digging.

Don't run the Launcher as it will replace your Wow-64.exe.

Just going to throw some ideas out.

Could your firewall be blocking your Wow.exe?

Might try flushing your DNS through command prompt. Bad DNS info could possibly be the problem. Here's the info needed to do this:

ipconfig /release
ipconfig /flushdns
ipconfig /renew

The first will break your network link, second will flush out your DNS, third will ask your router for a new IP address and you will be connected to your network again.

[wowd00d]

anyone else having issues with interrupts? Mine don't work anymore on mage or hunter since the patch. Using the default xhelper profile.

[warlock2000]

Going down the standard battlenet error checklist. I deleted both Blizzard Entertainment and Battle.net folders. No luck.

I'll check firewalls. There was a Windows update today, so maybe that's the culprit.

Next will be flushing the DNS.

[warlock2000]

Not a firewall problem. Not a DNS problem. I'm absolutely baffled. 64-bit works, 32-bit gives battlenet error. And yet for some people 32-bit is working. Blizzarrrrrrddddddddddd!

[kickmydog]

anyone else having issues with interrupts? Mine don't work anymore on mage or hunter since the patch. Using the default xhelper profile.

Hunter interrupt was changed. Go to my thread for the fix

[dre79]

Ive tried installing the latest .NET Framework and it still comes up with the same error. It says "Not all privileges or groups referenced are assigned to the caller'. Does anyone know what it means specifically?

Hi all,

Ive tried to use PQR but I get an Unhandled Exception error everytime. If I launch PQR before launching wow its fine, but as soon as I click launch wow, or if wow is already launched, the error comes up as follows:


See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): Not all privileges or groups referenced are assigned to the caller
at System.Diagnostics.Process.SetPrivilege(String privilegeName, Int32 attrib)
at System.Diagnostics.Process.EnterDebugMode()
at Magic.BlackMagic.Open(Int32 )
at Magic.BlackMagic.OpenProcessAndThread(Int32 )
at ...ctor(Int32 )
at .
.
()
at .
.
()
at .
.(Object , EventArgs )
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
PQR
Assembly Version: 2.2.4.0
Win32 Version: 2.2.4
CodeBase: file:///C:/Users/NETCOM-G6/Downloads/PQR.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
fasmdll_managed
Assembly Version: 1.0.3262.20709
Win32 Version:
CodeBase: file:///C:/Users/NETCOM-G6/AppData/Local/Temp/%7B4f1155fd-5df4-484f-a6cc-842079855c27%7D/fasmdll_managed.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
{2c374f33-1fdd-4811-bf32-e68eb2a37860}
Assembly Version: 0.0.0.0
Win32 Version: 2.2.4
CodeBase: file:///C:/Users/NETCOM-G6/Downloads/PQR.exe
----------------------------------------
msvcm90
Assembly Version: 9.0.30729.4926
Win32 Version: 9.00.30729.4926
CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_508ed732bcbc0e5a/msvcm90.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[Master34]

Don't run the Launcher as it will replace your Wow-64.exe.

Just going to throw some ideas out.

Could your firewall be blocking your Wow.exe?

Might try flushing your DNS through command prompt. Bad DNS info could possibly be the problem. Here's the info needed to do this:

ipconfig /release
ipconfig /flushdns
ipconfig /renew

The first will break your network link, second will flush out your DNS, third will ask your router for a new IP address and you will be connected to your network again.

First i want to thanks you to try to help us...i just did the ipconfig suggestion...and after that...click the new disable wow-64 button on pqr...done succesfully. So now the game start in X84 32 bit...i enter my email and password in the game...and i got error 114 again...only me and warlock2000 got this issues or what??

[warlock2000]

Master34 I believe I've found found it!

There's a thread in Blizzard technical support from 2hrs ago about the battlenet error #114 and anti-virus programs. Any anti-virus program you have that runs on the BitDefender engine will block 32-bit logins. I removed Malwarebytes from my computer and turned off all of my isp's built in protection tools. Then I deleted WoW.exe and Wow-64.exe, ran the launcher, and I was able to login in 32-bit.

Try this.

I'll try to isolate which one of the two programs I mentioned exactly was the one blocking the login (or maybe it was both!)

And thanks jh16 you were on the trail of the anti-virus thing

[jh16]

Master34 I believe I've found found it!

There's a thread in Blizzard technical support from 2hrs ago about the battlenet error #114 and anti-virus programs. Any anti-virus program you have that runs on the BitDefender engine will block 32-bit logins. I removed Malwarebytes from my computer and turned off all of my isp's built in protection tools. Then I deleted WoW.exe and Wow-64.exe, ran the launcher, and I was able to login in 32-bit.

Try this.

I'll try to isolate which one of the two programs I mentioned exactly was the one blocking the login (or maybe it was both!)

And thanks jh16 you were on the trail of the anti-virus thing

Haha, well it certainly sounded like something was blocking it. Good deal you were able to figure it out.

[Jettand]

Everytime I open PQR, my Microsoft Framework has an "Unhandled Exception", so I repair it and restart. I've tried re-installing it as well. This framework stuff keeps comming up every few days, any reason for this? Is there a fix for it? I can't even use PQR right now because of it.

[MACH9 WoW Services]

Has PQInterface been updated for 5.4?

[Ninjaderp]

PQInterface works just fine as it is, no need for an update as far as I know

[leinadz]

Hm i tried to use pqr but in pqinterface there is just written "2H Frost: running". When i attack a dummy, nothing happens. So does this have something to do with PQInterface or with the PQRBot itself? Because i updated it etc but it's not working