Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

ICM 7.5 - Campaign manager has crapped out and will not restart

I completed a simple Dialogic test of the dialer ports early yesterday afternoon in which I then checked my campaign skill group config because I could not get an agent reserved so I added my Dialed Number, Saved, Disabled the campaign then re-enabled it to force the update.  Checked CM and the process window is gone.  We're running 7.5(8).  I've already attempted to cycle the logger processes then rebooted because the process would still not come up.   Anyone come across this before?

We only have 30 ports and I only tested the first 2 channels.  Attached are the

5 REPLIES
Green

Re: ICM 7.5 - Campaign manager has crapped out and will not rest

Examine the .ems file for the Node Manager - nm_xxx.ems - in the la\logfiles directory. See if it is supplying the correct arguments and perhaps indicating what the problem may be.

Regards,

Geoff

New Member

Re: ICM 7.5 - Campaign manager has crapped out and will not rest

Thanks Geoff.  I'll take a look.  Are you coming to Verizon (Richardson) to teach us anything new?

New Member

Re: ICM 7.5 - Campaign manager has crapped out and will not rest

The campaign manager looks like crashes due to invalid object. Did anything change?

23:56:33 la-CampaignManager Trace: Unable to Update the Personal Callback Table; Error Message: 
23:56:33 la-CampaignManager Trace: Invalid object name 'Personal_Callback_List'.

23:56:33 la-CampaignManager Trace: Table will likely be created shortly
23:56:33 la-CampaignManager Trace: Connected to Blended Agent private database
23:56:33 la-CampaignManager Trace: Created DoNotCall interface object
23:56:33 la-CampaignManager Trace: Registry Value [CallbackTimeLimit] = [15]
23:56:33 la-CampaignManager Trace: Registry Value [UnknownCallStatusResetTime] = [60]
23:56:33 la-CampaignManager Trace: Registry Value [MinimumCallsForHitRate] = [30]
23:56:33 la-CampaignManager Trace: Registry Value [TimeToResetDailyStats] = [00:30]
23:56:33 la-CampaignManager Trace: Registry Value [RescheduleCallbacks] = [1]
23:56:33 la-CampaignManager Trace: Registry Value [PersonalCallbackMode] = [1]
23:56:33 la-CampaignManager Trace: Registry Value [PersonalCallbackTimeToRetryBusy] = [1]
23:56:33 la-CampaignManager Trace: Registry Value [PersonalCallbackTimeToRetryNoAnswer] = [20]
23:56:33 la-CampaignManager Trace: Registry Value [PersonalCallbackTimeToRetryReservation] = [1]
23:56:33 la-CampaignManager Trace: Registry Value [PersonalCallbackMaxAttemptsDefault] = [5]
23:56:33 la-CampaignManager Trace: Registry Value [PersonalCallbackTimeToCheckForRecords] = [1]
23:56:33 la-CampaignManager Trace: Registry Value [PersonalCallbackDaysToPurgeOldRecords] = [5]
23:56:33 la-CampaignManager Trace: Registry Value [PersonalCallbackRecordsToCache] = [20]
23:56:33 la-CampaignManager Trace: Registry Value [PersonalCallbackCallNoAnswerRingLimit] = [4]
23:56:33 la-CampaignManager Trace: Registry Value [PersonalCallbackSaturdayAllowed] = [0]
23:56:33 la-CampaignManager Trace: Registry Value [PersonalCallbackSundayAllowed] = [0]
23:56:33 la-CampaignManager Trace: Registry Value [PendingOverRetryEnabled] = [0]
23:56:33 la-CampaignManager Trace: Registry Value [DialerDetailEnabled] = [1]
23:56:33 la-CampaignManager Trace: Registry Value [DialerDetailBufferSize] = [20]
23:56:33 la-CampaignManager Trace: Registry Value [DialerDetailBufferTimeout] = [5]
23:56:33 la-CampaignManager Trace: Creating Personal_Callback_List
23:56:33 la-CampaignManager Fail: Error: Database table [Personal_Callback_List] could not be created, Error [There is already an object named 'PK_PersonalCallbackListID' in the database.
Could not create constraint. See previous errors.
]
23:56:33 la-CampaignManager Trace: CExceptionHandlerEx::GenerateMiniDump -- A Mini Dump File is available at logfiles\CampaignManager.exe_20100415235633304.mdmp
23:56:33 la-CampaignManager Unhandled Exception: Exception code: 80000003 BREAKPOINT

Fault address:  7C822577 01:00021577 C:\WINDOWS\system32\ntdll.dll

Registers:

EAX:00000000

EBX:77E68540

ECX:7FFDF000

EDX:0049C8D8

ESI:0012E800

EDI:7C82F34F

CS:EIP:001B:7C822577

SS:ESP:0023:0012DB04  EBP:00000001

DS:0023  ES:0023  FS:003B  GS:0000

Flags:00000246

Call stack:

Address   Frame

7C822577  00000001  DbgBreakPoint+0

New Member

Re: ICM 7.5 - Campaign manager has crapped out and will not rest

I had checked the personal callback at one time in the campaign and then unchecked it because we're not using it.  How would I get rid of the invalid object and get CM restarted is the question?

New Member

Re: ICM 7.5 - Campaign manager has crapped out and will not rest

Campaign manager is supposed to create the personal call back table the first time it runs. I would either try to enable personal call back to see if the issue will go away or drop the personal call back table and restart campaign manager. Or open a TAC case since the processes should document an error and gracefully shutdown, not crash the way this one is doing.

873
Views
0
Helpful
5
Replies
CreatePlease to create content