Modulebuilder fails to deploy in 6.0.1

[ldebaets]

I was buildiing a custom package of about 5 modules. I was building them one at a time and deploying them. When I got to the 4th or 5th module, the modulebuilder failed to deploy and a pop-up was generated with the message saing the package failed to install and there was an internal error. I had the sugarcrm logs on in DEBUG mode and there was no evidence of what could be the problem--no errors were reported. I removed the last module thinking it was the problem. The other ones still appear, I can create them, view them, without problems though I removed their inter-relationships in fear this was the problem. I thought the modulebuilder chocked on the amount of data it had to generate.

Is there a limit to the number of modules or relationships in a custom package being deployed in the modulebuilder? Am I exceeding some internal limit in the community edition modulebuilder?
Would it be best to have a couple of modules per package rather than putting them all into one?
(It takes a tremendous amount of time to rebuild the modules every time I have to start-over. Help would be appreciated.)
Thank you in advance.

[Angel]

I just ran into a similar scenario. The Module Builder acts a bit odd when the Module Loader is unable to find all of the installed module files, etc.

I don't know if this will help you, but in my case, the problem was that I had multiple entries in the Module Loader that corresponded to modules whose files were no longer accessible/present. Once I cleaned that up, my Module Builder worked flawlessly and I got past that same error you are getting.

[ldebaets]

I noticed the extra resource requirements for MySQL and PHP Scripts going into version 6.0.1 were needed to be made. It seems to have solved my problems.
Angel, thanks for the information. I will keep this in mind for the future.

Leonard