SalesForce.com Import - Very Weird

[redwolf3]

Hey Guys-
So, I just recently installed SugarCRM on our Windows 2K3 server. We are running Apache 2.0.49, PHP 5.1.4, MySQL 5.0.22, and SugarCRM 4.5.1.

The individual who will be using SugarCRM has been using SalesForce.com for a little over a year now, but doesn't use it nearly enough to warrant the monthly fees. He has about 2400 contacts and about 900 accounts.

I tried 5 times to import the Contacts using FireFox 2.0.0.2. Things seemed fine up until Step 4 (when it goes from the Step 3, Importing data ..... screen to the actual results). On FF it hung every time on this step and never proceeded. I even tried a smaller list of about 500, no avail.

I then loaded up IE 6.0, and attempted an import on the same 500 or so entries. This time, success. It imported and everything seemed ok. GREAT! I then attempted to import the remaining 1900 contacts. Here's where things got weird. After I uploaded the file and should have been taken to the "Match Columns" page, I got a "Page Cannot Be Found" error. Weird enough. I then decided to check the MySQL Database.

In checking the MySQL database, the number of accounts and contacts are constantly bouncing up and down. Contacts go from a low of about 300 to a high of about 600 and then back down again. I have restarted the server, removed the account privileges to the MySQL account for the DB, and none of it seems to help. I'm thinking that somehow there are transactions stuck in queue, but I can't seem to find a way to cancel or kill them. In addition, the system does not appear to be under load, it is idling happily at 1 - 2% CPU usage with no noticeable hit in MySQL.

Has anyone else had a problem like this? Since there really wasn't any data in the system, I could completely delete the DB and reset everything, but I need to do the SF.com merge and I don't want to get put back in this same position.

Any help would be greatly appreciated. Thanks.

[redwolf3]

So, a little more information. I killed the DB tonight because after 10 hours, the number of rows were still unstable in both the "Accounts" and "Contacts" tables. I then wiped the whole schema and did a fresh re-install. I repeated the import process and got the same results. The number of rows in each table constantly varies up and down by about 200-300. And every other attempt to upload and integrate records fails with no warning or reason.

Any thoughts anybody? Is there a better (more stable) version to use as opposed to 4.5.1?

[ruchida]

What is the execution time and max_memory set in php.ini?

[redwolf3]

execution time is set to 5 minutes (300 seconds) and max_memory is set to 128M right now.

[ruchida]

Is there any apache or sugarcrm log file?

There may be many reasons why you can not import them.

Date format issue?
http://www.sugarcrm.com/forums/showthread.php?t=19325

Memory issue?
http://www.sugarcrm.com/forums/showthread.php?t=19142
http://www.sugarcrm.com/forums/showthread.php?t=6750
http://www.sugarcrm.com/forums/showthread.php?t=6341

[redwolf3]

It looks like memory is still the issue. As of right now I have the memory set at 128M, I will bump it up to 1GB temporarily and see if that helps.

What really concerns me though is that, if I check in MySQL for the number of records, the number keeps fluctuating up and down. Not sure if this is because there are 1/2 finished transactions in the queue, or if it doesn't actually check the number of records, but rather "Guesses" how many based on the size? Even when this is going on, the number of records SugarCRM reports stays consistent, I just don't like it when something like this happens and I have no rational explanation (and it doesn't clear itself after 8+ hours of running).

[redwolf3]

*edit*

Posted a bunch more, but I figured out the problem, and it does have to do with dates.

Basically, the post talked about how with MS SQL, the import function worked, but not with MySQL. It turns out, MS SQL is able to recover from improperly formatted dates, but MySQL cannot?

Also, I definitely think the documentation needs to make it evident that SQL Server 2005 is the ONLY version that the MS SQL version works with. I spent 2 hours getting it up and all working nicely, just to find out I couldn't look at the second page on worth of results. And there is no explicit requirement for SQL Server 2005 anywhere on the main page. You have to dig deep to find it.

Oh well, such is life, and this is still a very nice app for free.