Steven
asked on
CRM 4 Import Data - import sits in System Job queue with "waiting" status
When using the Import Data function in CRM 4, the mappings and setting up the import is pretty straight forward. However, after submitting the Import - the job sits there with a "waiting" status. I can't force the job and no matter how long we wait, it never imports.
Also, when running ONE import, it creates THREE identical system jobs.
I am trying to import a pretty simple .csv with the following column headers:
CampaignName,MemberStatus, FirstName, LastName,C ompany,Pho ne,Email,T itle,
Record type: customer
crm.jpg
Also, when running ONE import, it creates THREE identical system jobs.
I am trying to import a pretty simple .csv with the following column headers:
CampaignName,MemberStatus,
Record type: customer
crm.jpg
ASKER
There are a ton of event logs. Here are two examples:
Error
MSCRMKeyGenerator
18949
Current active key (KeyType : CrmTicketKey) is expired. This can indicate that a key is not being regenerated properly. Current Active Key : CrmKey(Id:83acb6fb-9daf-dd 11-b0cb-00 221912222e , ScaleGroupId:00000000-0000 -0000-0000 -000000000 000, KeyType:CrmTicketKey, Expired:True, ValidOn:11/11/2008 03:08:16, ExpiresOn:11/13/2008 03:08:16, CreatedOn:11/11/2008 03:08:16, CreatedBy:NT AUTHORITY\NETWORK SERVICE. Key Setting :
Error
MSCRMKeyGenerator
18949
Current active key (KeyType : CrmTicketKey) is expired. This can indicate that a key is not being regenerated properly. Current Active Key : CrmKey(Id:83acb6fb-9daf-dd 11-b0cb-00 221912222e , ScaleGroupId:00000000-0000 -0000-0000 -000000000 000, KeyType:CrmTicketKey, Expired:True, ValidOn:11/11/2008 03:08:16, ExpiresOn:11/13/2008 03:08:16, CreatedOn:11/11/2008 03:08:16, CreatedBy:NT AUTHORITY\NETWORK SERVICE. Key Setting :
And yes, the async processing service is running
Error
MSCRMKeyGenerator
18949
Current active key (KeyType : CrmTicketKey) is expired. This can indicate that a key is not being regenerated properly. Current Active Key : CrmKey(Id:83acb6fb-9daf-dd
Error
MSCRMKeyGenerator
18949
Current active key (KeyType : CrmTicketKey) is expired. This can indicate that a key is not being regenerated properly. Current Active Key : CrmKey(Id:83acb6fb-9daf-dd
And yes, the async processing service is running
Do you have any event logs specifically regarding the CRM Async service.
If you've followed WilyGuys suggestion and checked the async service, two things spring to mind:
Check that the account running the async service has access to the database (normally you'd have an event log entry giving you a clue about this)
If your installed version of crm4 is an old one then you could run an uninstall/reinstall but allow the installer to update the install files. This has the trick of downloading all the latest patches and fixes prior to installation. You can then re-connect your installed version to your existing database and will have an updated crm4 install. This has fixed some workflow issues for me in the past..
If you've followed WilyGuys suggestion and checked the async service, two things spring to mind:
Check that the account running the async service has access to the database (normally you'd have an event log entry giving you a clue about this)
If your installed version of crm4 is an old one then you could run an uninstall/reinstall but allow the installer to update the install files. This has the trick of downloading all the latest patches and fixes prior to installation. You can then re-connect your installed version to your existing database and will have an updated crm4 install. This has fixed some workflow issues for me in the past..
Are you able to restart the Async Service?
As Jez asks, what are you running that as? (Network Service, Local System, domain user?)
Looks like it thinks Network Service.
Also, do an IISRESET -stop, then stop the service, then IISRESET -start and start the service.
You may have to delete the old import jobs as well and try to re-import.
As Jez asks, what are you running that as? (Network Service, Local System, domain user?)
Looks like it thinks Network Service.
Also, do an IISRESET -stop, then stop the service, then IISRESET -start and start the service.
You may have to delete the old import jobs as well and try to re-import.
ASKER
Async service is automatic running as Network Service.
I performed an IIS Reset as suggested and deleted the jobs that were hung.
I tried to do a reimport and again, three jobs are created with a "waiting" status.
I performed an IIS Reset as suggested and deleted the jobs that were hung.
I tried to do a reimport and again, three jobs are created with a "waiting" status.
http://support.microsoft.com/kb/950680/en-us
See if that works for you. Basically in looking at your history, you upgraded and may have even imported the 4.0 database. Very possible that this applies.
Workflow works in the background to do data duplication checking etc.
Do you have any plug-ins that might be trying to fire?
See if that works for you. Basically in looking at your history, you upgraded and may have even imported the 4.0 database. Very possible that this applies.
Workflow works in the background to do data duplication checking etc.
Do you have any plug-ins that might be trying to fire?
ASKER
Opened a case with Microsoft and after they looked at my issue it was suggested I try this: http://support.microsoft.com/kb/950416
I will give that KB a shot next week.
I will give that KB a shot next week.
Have you resolved this issue? I have the same issue and curious whether or not you solved it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
did all the recomanded steps still the same problem persists.
Is the Async service running?