INVALID DATA ERROR

CRITICAL

I have project which runs fine inside SC environment. When I deployed it to the server I get “Invalid data error”.
Tried to run it on XAMPP locally and get the same result. Not sure what is causing it but certainly not the error or bugs in my code. I get this error when starting project which is just a menu.
any ideas ? It seems that there is a bug in SC (btw. I just upgraded to latest version 2-3 times and had no chance to test it on deployment sever in the meantime so not sure when this started to happen).

Also when running first time on the server the Connection App should pop-up as usual asking me to configure connection string etc, but this doesn’t happen!
At this moment I’m completely stuck - cannot deploy and test.

Arthur

A quick guess… Maybe you need to check the deployed server for the characterset settings. The database and the filesystem characterset I mean.
So if you are on linux using utf-8 filesystem then you need to be aware of that and set it accordingly. But this is just a guess…

Thank for replying I will check this out but this should not be a case. When I run this App from SC it works OK. When I go through the deployment process is is not working. In all 3 scenarios I use the same connection and same database (another words when opening from SC I still use remote data from internet). I reinstalled SC to v8.1.50 but no change. I also did some testing. Created SAMPLES project from wizard. I just changed database to MySQL. When I run this locally on XAMPP it works fine. Something somewhere gets screwed up while creating a deployment ZIP file, but I have no idea how to trace it.

For testing I removed everything from XAMPP and deployed only 6 menu Apps (no forms grds etc.) and I get the same error.

BTW. What is the proper PHP version for SC v8.1.50 ???

Did some testing and looks like something got messed up in the latest SC update

When running site locally on WAMP[B] I get this

[ATTACH=CONFIG]n71601[/ATTACH][/B]

and when running on the remote server I get this

[ATTACH=CONFIG]n71602[/ATTACH]

menu_errors.png

menu_errors2.png

OK, now I should send a bill to NetMake for 12 hours of wasted time !
I had to look all my backup, HDs, CDs etc to find an older SC version (because some brainless person removed all older SC versions from NetMake server).
Finally found SC v8.1.20

REGENERATED CODE AND IT ALL WORKS FINE

what does it mean ? NetMake had screwed SC update again
and it is not a first time SC update damaged my project

I would like to ask what quality check is done before the update is released ? Of course one cannot predict and test all possible scenarios and bugs happen but just for cases like that all update versions should be available for download on the server and the fact that IT IS NOT AVAILABLE PISSES MY OFF REALLY BAD !
[ATTACH=CONFIG]n71609[/ATTACH]

So remember - in the future you might be pulling your hair of what have you screwed up in your project, but before you do this check what NM devs could screw up even before you did.
I have to pay a price of wasting almost 2 days to figure that out.

sc_8120_works.png

Sorry, you had to go through that Arthur.

Early on, I learned from the forum that new ScriptCase versions may break a project or an application. This happens with other develop tools as well, but when we consider maturity in software development and release management, I think that we can easily agree that ScriptCase is not that mature since there does not seem to be bug tracking or test suites that are executed before release, etc. In fact, I think that one best consider ScriptCase maturity wise (for software development) like children. They are creative and come come up with great ideas that are implemented in new versions, but one would not entrust them with responsibility, i.e. not trust a new version coming out.

Personally, I do not upgrade right away since there often is no pressing need to. After a release have been out for some time and/or it is a major upgrade to a new version with features that I really want to use in my application, I do a full backup of both the ScriptCase installation and my projects so both can be fully restored. I think Albert and others have strongly suggested this as well.

We can hope that at some point in the future, ScriptCase will attain critical mass as a company and be able to implement more quality assurance and testing as well as further improvements in their code base. Until then, I am happy to use the very feature rich ScriptCase tool, but will always take strong precautions when installing new versions.

Well we all make mistakes and create bugs. I understand that part - we are all DEVs. What I do not understand and what pisses me off is lack of common sense. We all know SC does break projects after update, so NetMake knows. Despite of that they refuse to publish older releases of SC for download. I wasted 2 hrous trying to find and reinstall sc v8.1.20 because some short visioned person did not consider one might need an older version.