I received the following error while trying to migrate my profiles:

An HTTP error 500 occurred. /test/batch?id=75&op=do

Comments

BetaTheta’s picture

BetaTheta commented

Investigated it, all the fields are created, however no actual content has been created. Furthermore, if I try to migrate profiles again using the same content type, it just created the fields again. So now I have two 'first name' fields, two 'last name' fields etc.

BetaTheta’s picture

BetaTheta commented

I tried deleting all the profile content types and trying again. It kinda worked. It created 3 profiles, but then I got the same error again.

BetaTheta’s picture

BetaTheta commented
Title: An HTTP error 500 occurred. /batch?id=75&op=do » An error occurred. /test/batch?id=99&op=do (no information available).

So I talked to my server. They increased the cpu limit from 60 seconds to 180 seconds. The http 500 error stopped appearing. Also, it seemed like more profiles were being created. Now 8 profiles are created before it stops.

And basically it's on 'initializing' for a minut, then it shows 'creating profile field about_me'. About_me is the last profile field on my website. The progress bar also shows 50% is complete and then it gives the error.

karens’s picture

karens commented

There are two steps in the processing, creating the fields and then populating them with values from the profile fields. It is succeeding on the first step, where you see the 50% it means 50% of the two processes have completed. It is getting stuck in the second process, creating the values. That step is creating one new profile node in each pass. If you are timing out there, it takes more than your server's timeout settings to create a single node. I don't know what else is going on in your system, but apparently you have some expensive processing done by one or more modules during node creation. You should easily be able to create a node in 30 seconds in a plain vanilla system setup.

It sounds like increasing the cpu time fixed the problem, but I can't be sure that's what you're saying. But if you're still not finishing, even with a higher timeout setting, you may need to figure out what modules you have installed that are slowing down the creation of the nodes and maybe turn them off while you do the import. There are many modules that jump in and do their own processing when a node is created, and it looks like you may have some module(s) that are slowing things down.

Also, as you already found, you can't just keep re-running the process or you will get more and more fields added each time. You need to do a backup before you start and then start over from the backup each time.

karens’s picture

karens commented

Especially, be sure you don't have modules that are doing things like sending an email out when your nodes are created. That could clobber your system.

BetaTheta’s picture

BetaTheta commented

Thanks for your help! I disabled a lot of my modules and it worked!

karens’s picture

karens commented
Status: Active » Fixed

So I think this is fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

bryancasler’s picture

bryancasler commented

I disabled all but the bare minimum files needed to make this happen, yet I am still getting. "An HTTP error 500 occurred. /batch?id=4&op=do" I have my site hosted on Rackspace Cloud Sites, so I'm not sure if being on a virtual host is creating a problem. Anyone else still having this problem besides me?

strick’s picture

strick commented

I had this problem while trying to rebuild content access permissions: /?q=batch id=42&op=do Everytime I got the 500 error, I just reload the page, and eventually got it to finish...

sivarani’s picture

sivarani commented

I too got the same error. Its working fine in localserver but in live its not working its show the An HTTP error 501 occurred. /batch?id=47 &op=do Error. In content management am trying to promote some 20 records in front end, that time am getting this issue

bradallenfisher’s picture

bradallenfisher commented

This has to do with a couple settings in your php.ini file.
Most probably it is regarding memory_limit which should be set relative to the size of the feed. I have a feed pulling in 9000 records from a csv file and i needed to set my memory_limit = 256
That is crazy high, but it worked.
The other culprit could be
max_execution_time. If you don't have shell access or are using a VPS of some sort these flags can be altered by requesting a service ticket from your provider.