How to Debug "Failed to Retrieve Data" When Deploying Custom Module

[vcomp]

I've had great success building custom modules. Then I made the mistake of naming a module by the same name that I used in a different package. Now I many problems and each time I attempt to deploy the module I receive an error message "Failed to Retrieve Data".

Can any one suggest how to identify what's causing the "Failed to Retrieve Data" problem. I'm using Version 5.5.0 (Build 6653) on Windows.

Thanks,

Vic

[christianknoll]

get a proper development environment (we use partially ZEND and some of our developers use pure eclipse with the PHP plugin) and debug it.

christian.

I've had great success building custom modules. Then I made the mistake of naming a module by the same name that I used in a different package. Now I many problems and each time I attempt to deploy the module I receive an error message "Failed to Retrieve Data".

Can any one suggest how to identify what's causing the "Failed to Retrieve Data" problem. I'm using Version 5.5.0 (Build 6653) on Windows.

Thanks,

Vic

[vcomp]

Agreed, your solution is the mother of all hammers for my nail. I'm hoping there is a less heavy handed method such as log files, etc.

Thanks,

Vic

[davidboris]

Hi,

If I have understood your problem well, I would suggest, you have already deployed the module from module builder(though it was not good), then remove the wrong module from module builder and create a fresh one.

[vcomp]

Yes, I deployed many times successfully. Afterward, I created a new package. Within that package I created a new module with the same name as one in the original package. That's when my problems started. I haven't been able to deploy the original package since that time.

Thanks,

Vic

[ngchieu]

I met this problem too

In my case it turn out that my package is too big so that PHP cannot process the scripts within 30 seconds

By default, after 30 second, if the scripts is not finished then PHP stop process them and throw an error.

Just add this line to PHP.ini to solve the problem.

max_execution_time = 120 (or some bigger number)

After 2 weeks digging the Internet, checked all proposed solutions, a lot of my hair has gone for this problem

[andopes]

Depending on Sugar version it takes some time to deploy a package.
I suggest you to publish and install through Module Loader, it is pretty safer.

Regards