Registration failing on 1 of my clients machines, but that's it....?????
I've developed a runtime solution that I'm distributing and I purchased a solution license from you guys for this software. I've been distributing it without any problems until now.
I have 1 customer who purchased the solution and the SmartPlugin is giving him problems with registration.
I have a little script that checks the registration and if it's not registered, does so each time the application loads. I also have a script in the Scripts menu so if there seems to be a problem we can manually register it too.
This customer says it's working perfectly fine on his desktop, but he's installed it on his laptop and the plugin won't register. When he loads the program he gets the message about it not registering correctly. When I have him run the manual registration we're just getting a ? back instead of an error code.
The register script is very simple...
Set Variable $$reg, PHP_Register("solutionname", "companyname", "serialnumber")
If[$$reg = 0]
Show Custom Dialog["successful"]
Else
Show CustomDialog["failed....Error Code: " & $$reg
End If
Is that not correct? When I was testing I would change one of the values in my registration data and I would get an error code back just as expected.
Any ideas what's going on here? I'm stumped. He's the only this has happened to and the ? doesn't do anything for me.
Any information would be greatly appreciated. Thanks!
eh...
Sorry, I made the rookie mistake of not looking at other questions before posting this. Seems like others are having the same exact issue. One guy mentioned the .NET Framework 2.0 so I just sent my customer an email asking him if he's got that installed and if not to try it.
I do remember when I was using IntallShield to package an MSI installation it was returning some warnings about the .NET framework but I didn't want to let it make any changes to the .dll's or anything that FM runtime created for me. I'll run that again and check the logs to see if I can get any good info.
update
My customer has confirmed his machine nat .NET 1.1 on it. He's currently running Windows Update and he's going to get back with me.
success
Yup, he ran windows update and got his .NET updated and then the plugin registered fine for him.
So let me get this straight:
So let me get this straight: the plugin requires .NET 2.0, or if it's installed it needs to be version 2.0? Or is there another dependency for you that caused the problem? I've got the same problem and I'm wondering if this a general solution.
Cheers,
Darko.