Error retrieving record. This record may be deleted or you may not be authorized to..

[Marcokid]

My Sugarcrm hosting server was recently replaced with a new one with top-of-the-line hardware.
The operation should have been completeley transparent to the users. No software change was foreseen, just hardware change.

After this change I got the following error in a custom module, created with Module Builder, every time I push the "Create" button:

Error retrieving record. This record may be deleted or you may not be authorized to view it.

I was logged as administrator so the problem shouldn't be related to privileges.

I can access all the module's data without problems using DetailView, ListView and Editview. The problem seems restricted just to Create.

Moreover the problem occurs only on one module message while I have no problem with all the other standard or custom modules.

My installation is:
SugarCE Version 5.5.0 (Build 6653)
Linux
Apache
PHP Version 5.2.9
MySQL: 5.0.91mm-log
Version protocol: 10

I looked through the Sugarcrm error log but it didn't help.

I have no idea what I can do to debug this problem.

Any help or suggestion would be greatly appreciated.

Thanks!

[Marcokid]

I did a quick repair of the module but the problem remains.
When trying to create a new record I receive the same error message:
Error retrieving record. This record may be deleted or you may not be authorized to view it.

I have also tried to restore the module's db table using several previous backups but even this did dot solve the problem. All the other modules work fairly well.

The final (and last I think) possibility will be to restore the whole database.
Before doing that I would like to check which Sugar module is responsible for that error message.

However I would need a little help from more experienced SugarCRM people to debug this problem.

[Marcokid]

I was able to solve the problem by myself: it was due to a recent modification in my custom view.edit.php (wrong test that triggered a Sugar die).
Unfortunately the coincidence with the hardware upgrade event led me initially in the wrong direction.
Now everything works well. Sorry for having posted it but I was really worried about this problem.