General Category > General Discussion
eSellerate error - 25007 machine mismatch
devgrp:
You guys a driving me crazy with all these anti piracy safe guards. First I install GSX on a brand new clean install of windows 10. Coualt loads up but nothing happens when I try to bring up gsx or when I click on any of the menu. I turn off my AV and reinstall and it works, so I did a flight from MDPP to KIAD and landed fine. I exit fsx and install a few scenery from Vidan Design. I start fsx back up and I get eSellerate error - 25007 machine mismatch error and have to verify activation for gsx and all my fsdt and FB sceneries.
What is this all about? I'm using up all my activations when they were already activated. What could have triggered a reactivation when all I did was install a few sceneries
virtuali:
--- Quote from: devgrp on August 04, 2015, 05:54:31 am ---You guys a driving me crazy with all these anti piracy safe guards. First I install GSX on a brand new clean install of windows 10. Coualt loads up but nothing happens when I try to bring up gsx or when I click on any of the menu.
--- End quote ---
And what THIS has *anything* to do with piracy ?
--- Quote ---I turn off my AV and reinstall and it works
--- End quote ---
THIS was the problem, instead. Your antivirus, instead, is driving you crazy with its faulty heuristic logic and it's mistakenly identifying a legit program as a virus, so it's the antivirus that is clearly bugged.
We made EVERYTHING on our part to be compliant with the latest anti-false positive standards. In another thread, you say you are using the GSX Beta, and this has a feature called "Taggant" standard:
https://standards.ieee.org/news/2011/icsg_software.html
That allows executables digitally signed in a certain way, to be considered safe. Provided your antivirus recognizes this. As you can see, it's an IEEE standard that has been published in 2011, so there was plenty of time for antivirus vendors to support it to fix false-positive alerts. We added it to our executables as soon as it was commercially available so, we made everything we can (supporting Taggant is not free) to prevent false positives, now it's the antivirus vendors turn to do their part to make their products more reliable.
--- Quote ---, so I did a flight from MDPP to KIAD and landed fine. I exit fsx and install a few scenery from Vidan Design. I start fsx back up and I get eSellerate error - 25007 machine mismatch error and have to verify activation for gsx and all my fsdt and FB sceneries.
--- End quote ---
According to your own report, you installed GSX "on a brand new clean install of windows 10", so it's absolutely NORMAL this would trigger an activation confirmation. We explained this countless of times: the ONLY time you need a reactivation, is when:
- You change a major hardware component
OR
- You reinstall Windows from scratch.
So, there's nothing unexpected here. You simply have to confirm your activation, what's the problem ? It's not as if you reinstall Windows from scratch every day, I hope...
--- Quote ---I'm using up all my activations when they were already activated.
--- End quote ---
You used all your activation because you forgot to use the "Deactivate" feature before updating your system. And you forgot this for 5 times. You cannot fault the system, if you always forget to use one of its best feature at your disposal to NEVER end up with no activations left:
http://www.fsdreamteam.com/forum/index.php/topic,4082.0.html
This feature has been available in all our products since 2011. It's strongly suggested you use it.
HOWEVER, that doesn't mean you cannot reactivate anymore. It simply means you must contact us asking for a manual reactivation. The Deactivate feature was supposed so you DO NOT have to contact us, and reactivate right away without waiting for an answer.
--- Quote ---What could have triggered a reactivation when all I did was install a few sceneries
--- End quote ---
You clean-reinstalled Windows, THIS is what caused a reactivation. OF COURSE, according to your report, if GSX wasn't working at that time, because the antivirus blocked the program from running, it's normal you wouldn't get any reactivation notification, when the programs weren't running, but only when they started to work again.
And, it's not as if the activation is checked constantly, there's a bit of grace period, so it's not strange you were notified a bit later, instead of immediately after you reinstalled Windows.
devgrp:
Dude did yo read my post? Yes I did a clean install of windows on the 29th of july and activated all my sceneries. Everything was fine. I did a flight to KIAD and all the buildings were there and even GSX worked. The first time GSX didnt work, like I mentioned in the other thread so I closed FSX then restarted.
Started at MDPP and GSX finally decide to work. Flew to KIAD and landed. Buildings and GSX works. I close FSX and installed 3 new scenery from Vidan Design. Started back up fsx to check out the new sceneries and I get the error. Now my question is how is this possible. 3 hrs before it worked and no activation error, then I close FSX and start it back up and I get activation error. If you bothered to read my post you would see that I didnt reinstall windows after the flight so nothing changed.
As far as AV goes, I'm using the default Windows defender in windows 10. I did exactly what you suggested when installing all fsdt and FB sceneries. Turn of AV and have my AV excluded coualt, bglmanx and the entire fsdt folder in fsx. This is beta software so you may want to listen to your customers when they report problems. I never had these problems with the previous version
virtuali:
--- Quote from: devgrp on August 04, 2015, 10:27:47 am ---Dude did yo read my post?
--- End quote ---
Obviously yes, I wonder if you read mine, instead.
--- Quote ---Yes I did a clean install of windows on the 29th of july and activated all my sceneries. Everything was fine. I did a flight to KIAD and all the buildings were there and even GSX worked. The first time GSX didnt work, like I mentioned in the other thread so I closed FSX then restarted.
--- End quote ---
GSX was working, but since THERE IS some grace time (as I've said, it's not that it checks for activations every minute...), it didn't triggered an activation check in this (brief) time it was working.
--- Quote ---Started at MDPP and GSX finally decide to work. Flew to KIAD and landed. Buildings and GSX works. I close FSX and installed 3 new scenery from Vidan Design. Started back up fsx to check out the new sceneries and I get the error. Now my question is how is this possible. 3 hrs before it worked and no activation error, then I close FSX and start it back up and I get activation error.
--- End quote ---
I already explained why this is possible. It's not as if the activation is checked every single time (which is obviously BEST for you), the checked simply happened later, on the next FSX restart after the program finally decided to make a check (and it was fully working), the fact you seem to associated it with an install of other sceneries doesn't have anything to do with it, it was just an FSX restart.
--- Quote --- If you bothered to read my post you would see that I didn't reinstall windows after the flight so nothing changed.
--- End quote ---
If you bothered to read my post entirely, especially the part which I repeated here about the program not checking constantly, you would have know why this might have happened.
It's ALSO possible that, even for you "nothing changed", Windows itself, which was installed very recently, was still in the act of configuring itself and made some updates in the meantime, which might have triggered a new reactivation which, again, you will notice ONLY when you restart FSX. SOME Windows updates, especially if they act on some drivers like the IDE/SATA or the network drivers, might trigger a reactivation.
--- Quote ---As far as AV goes, I'm using the default Windows defender in windows 10. I did exactly what you suggested when installing all fsdt and FB sceneries. Turn of AV and have my AV excluded coualt, bglmanx and the entire fsdt folder in fsx.
--- End quote ---
I'm using the Windows 10 default defender too, but I haven't got any problems with the modules. But I haven't reinstalled it from scratch, I only updated Windows 8, so it kept my previous antivirus exclusions that I set with Windows 8.
--- Quote ---This is beta software so you may want to listen to your customers when they report problems. I never had these problems with the previous version
--- End quote ---
If you are referring to the activation request, this doesn't have anything to do with the Beta. We don't do ANY hardware check directly. We don't even KNOW, exactly, how it works.
It's done entirely by the Esellerate .DLL, which hasn't changed since 2007, and the actual reactivation message you see on screen is made by the Addon Manager, which is the SAME file as it's the regular version, the only things changes in the Beta are Couatl and the GSX code.
If, instead, you are referring to the problem with the antivirus, which doesn't happen here (but as I've said, I already had all the needed file excluded from the previous Windows installation), if there's a difference in the Beta, is that it should be LESS affected by false-positives, because its uses the Taggant system, while the regular version didn't.
devgrp:
So you are basically telling me that when I install a scenery and put in my serial number its not activated right away? because this has never happened on any version of windows or gsx I've had. I've had gsx and a few FB and fsdt airports and I've never gotten that error before and I've had them for a couple years now. All these problems started when I install the beta. And for the record its wasnt just GSX asking for reactivation, it was all my FB and fsdt sceneries.
I just dont believe that installing gsx and all the sceneries since the 7/29 and now 8/3 thats when they decided to be activated, when the activation window popped up and ask me if I want the scenery to be activated and told me that the serials were back up. Now mind you I'm not a idiot when it comes to computers. I have a BS in computer science so I know what I'm doing. You just seem to think your "beta" program doesnt have bugs. After all its beta. Instead you blame AV software from MS who has tons of programmers working for them. Its safe to say that since I'm not the only one have this problem, its your program thats the problem which you need to fix
Navigation
[0] Message Index
[#] Next page
Go to full version