6.1.5 Module Loader - 404

[Frank_Con]

Hello,

I have a clean install of SugarCRM 6.1.5 on IIS 7.5 using MsSQL and it is working perfectly.

I now want to add a module and have gone to the module loader, clicked browse, selected my file (ZuckerReports_1.13a_module.zip) and clicked upload.

This then takes me to a page which says:

Server Error
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

Could anyone offer me some advice as to what might be wrong? I've not managed to find a solution through searching.

Thanks.

[Frank_Con]

I'm still trying to solve this issue and thought I'd add a little more information.

When loading "index.php?module=Administration&action=UpgradeWiz ard&view=module" (The module loader) the following is put into the sugarcrm logs file.

06/07/11 11:43:48 [2752][1][FATAL] HTTP Error: no data present after HTTP headers
06/07/11 11:43:48 [2752][1][FATAL] HTTP/1.1 100 Continue

HTTP/1.1 500 Internal Server Error
Server: nginx
Date: Tue, 07 Jun 2011 10:43:43 GMT
Content-Type: text/html
Connection: keep-alive
X-Application-Server: xxx.xxx.xxx.xxx
Content-Length: 0


06/07/11 11:43:49 [2752][1][FATAL] HTTP Error: no data present after HTTP headers
06/07/11 11:43:49 [2752][1][FATAL] HTTP/1.1 500 Internal Server Error
Server: nginx
Date: Tue, 07 Jun 2011 10:43:44 GMT
Content-Type: text/html
Connection: keep-alive
X-Application-Server: xxx.xxx.xxx.xxx
Content-Length: 0

No errors are logged when I click upload.

I'm going to continue trying to work this out but any advice would be welcomed.

Thanks.

---------------------

Edit: More info

I thought I would check the upgrade wizard and run the systems check to make sure there were no issues, it reported back as follows:

File Permissions: All Files Writable
Database Privileges: All Privileges Available
Detected Settings: All System Settings Requirements Satisfied

This is a good step for debugging for anyone trying to solve similar issues.

My search for a solution continues.

[Frank_Con]

After 2 days I've still not managed to solve this problem, here are a few things I've tried.

• Upgrading sugar using the inbuilt wizard to version 6.2 (upgrade worked perfectly) - Same issue.
• Installing both 6.1.5 and 6.2 from scratch - Same issue.
• Rebuilding the server - Same issue.

The server is being built using a standard 2008 r2 install, IIS 7.5, fastcgi, php then mssql express - No stack installers. I've not setup any additional software, 3rd party or otherwise - I'm not even using an accelerator in the newest install.

If anyone has any suggestions as to what else I can try I would be greatful! The install itself seems to work perfectly, all the modules work as expected, the upgrader worked perfectly without a single issue. It's just simply the module loader that's not working and this strange error appearing in the logs.

Also, does anyone have any idea why the sugarcrm.log file is saying "Server: nginx" in the error? I'm running a closed IIS server and have not setup a nginx server at any point. Is this something you would expect to see in the error logs?

Thanks as always,

[Frank_Con]

I finally managed to work out this error and solved my problems, huzzah.

The errors being put into the SugarCRM log file were not related and a big decoy in trying to find a solution.

Solution:

The 404 error was being caused by the misconfiguration of an IIS setting, I needed to increase the size of maxAllowedContentLength in my web.config file as by default in IIS 7 it is lower than I required.

I added the following:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.web>
<!-- maxRequestLength and requestLengthDiskThreshold is in Kilobytes-->
<httpRuntime maxRequestLength="204800"
requestLengthDiskThreshold="204800" />
</system.web>
<system.webServer>
<security>
<!-- maxAllowedContentLength is in Bytes not Kilobytes -->
<requestFiltering>
<requestLimits maxAllowedContentLength="204800000" />
</requestFiltering>
</security>
</system.webServer>
</configuration>

This problem caused a lot of annoyance but was simple enough in the end, hopefully this thread may save someone else the pain I went through.