What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Help please.

I have the same problem. All prerequisites installed, turned off antivirus and firewall.
 
Please download and try the Beta. The Release version is not updated for 1.3.0 yet.
 
This is happening with latest Beta. For me Beta is working fine on my VM. However, I'm moving my bots to my host OS and that is where this exception occurs.
 
ExiledExile said:
This is happening with latest Beta. For me Beta is working fine on my VM. However, I'm moving my bots to my host OS and that is where this exception occurs.
Click to expand...

Is a log file generated at all? What OS is your host?

You're downloading a clean copy of the Beta, and not using any loaders or running any other software that is meant to interact with EB before you actually launch EB, correct?

I don't know of any reason for that exception, unless something is modifying EB at runtime. If it's working on the VM, but not your host OS, that's rather odd, but you'd have to compare what's running to know if something is affecting EB.
 
Yes, log is generated buy is empty (0 bytes size).
OS is Windows 7 Professional with latest updates.
I'm using ExilebuddyBETA 0.1.2931.970, new fresh copy, not using any loaders, disabled antivirus. I have installed everything (.NET 4.5.1, all VC runtimes)

If I run new fresh copy it happens after selecting Default profile, entering key into Login Window and pressing Login button. Then on next run it crashes right after selecting Default profile since key is already stored in the config files.

I even tried reinstalling/repairing .NET 4.5.1 but it didn't help.
 
Right now, the only thing I can suggest to you guys is try reinstalling your OS and see if that fixes the issue. I believe there's something running in the background (that you might not know about) that is affecting EB.

That message box was added Oct. 16th to catch that exception and prevent it from taking down the bot. The actual login code there has been the same since April, and didn't change recently.

The bot's login code is from Buddyauth, which is what we use for all our bots, so if there was a specific issue with that, everyone would be affected, or we'd have a lot more reports on a consistent basis (like session invalid issues).

If you have a key from us, that you can see in BuddyAuth, please reinstall your host OS, run the Buddy Dependency Wizard, redl/update PoE, and try running the bot again. I'm pretty sure the issue will be fixed then.
 
Are there any specific ports required to be open or services running for Exilebuddy to work?
 
You must log in or register to reply here.
Back
Top