Re: Unable to move & flush the messages

chkt1 · ‎11-22-2004

Hi,

MSM 1.4.0.32, Unity 4.04

I am unable to move the "read" only messages to deleted item folder after x days and then flush the message. I get the following message in the log file.

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

Cisco Unity Message Store Manager Version 1.4.0.32

MSMConsole Init: 04/11/03 16:14:01

UNITYREACH\Administrator

CMsmDataHelper::GetAttribute(_AVSTR_TASKNAME) failed - Code: 0x80004005. Method: CTaskView::DisplayTasks(). [TaskView.cpp::216]

CMsmDataHelper::GetAttribute(_AVSTR_WARNLIMIT) failed - Code: 0x80004005. Method: CScriptView::MessageFilterProperties(). [ScriptView.cpp::182]

CMsmDataHelper::GetAttribute(_AVSTR_SENDLIMIT) failed - Code: 0x80004005. Method: CScriptView::MessageFilterProperties(). [ScriptView.cpp::188]

CMsmDataHelper::GetAttribute(_AVSTR_SENDRECEIVELIMIT) failed - Code: 0x80004005. Method: CScriptView::MessageFilterProperties(). [ScriptView.cpp::194]

CMsmDataHelper::GetAttribute(_AVSTR_TASKNAME) failed - Code: 0x80004005. Method: CTaskView::DisplayTasks(). [TaskView.cpp::216]

m_pCurrentNode NULL - Code: 0x80004005. Method: CMsmDataHelper::OpenNode(). [MsmDataHelper.cpp::519]

TAvKeyedCollection::Next() failed - Code: 0x80004005. Method: CSelectSqlObject::GetNextID(). [SelectSqlObject.cpp::244]

CMemberView::AddSqlObjectDlg() failed - Code: 0x80004005. Method: CSplitter::AddSqlObjectDlg(). [Splitter.cpp::191]

m_pCurrentNode NULL - Code: 0x80004005. Method: CMsmDataHelper::OpenNode(). [MsmDataHelper.cpp::519]

CMsmDataHelper::GetAttribute(_AVSTR_TASKNAME) failed - Code: 0x80004005. Method: CTaskView::DisplayTasks(). [TaskView.cpp::216]

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

Any idea? Thanks for help!

k.wiebe · ‎11-22-2004

Does this happen with every agent or just one? If you create a new, test agent, even with just a single subscriber, does this still occur?

If need be, we can get the MSM data file, msmdata.xml, and take a look at why MSM is unhappy.

chkt1 · ‎11-23-2004

Hi Kenneth,

Same result occured for both cases.

I have got the msmdata.xml, MsmScriptOutput_ENU and ST6UNST files.

Thanks

k.wiebe · ‎11-23-2004

OK, your msmdata.xml file looks fine. The logs you included in your original post were from the MSM console operation, MsmConsoleDiag.log. Are you having problems during script configuration, or is the actual script failing when it runs?

If the script is failing when it runs, are you scheduling it to run at a particular time or are you choosing the "run now" option?

If the script is failing when it runs, there are other logs that will be far more helpful to us. For example, for your agent called "General Staff", there should be a file called something like 'General_Staf_InboxToDeleted_0411223_093516.msmf.log'. The file name includes the name of the agent, the type of script being run, and the date and time of the script run attempt. There may also be an associated .xml file.

If the failure is actually within the MSM console while you're configuring scripts or agents, can you describe exactly what happens?

Thanks,

-Ken

chkt1 · ‎11-23-2004

I have setup two actions only.

1)Move Messages from Inbox to Deleted Items Folder

2)Flush Messages from Deleted Items Folder

remark: I have not enable deleted items folder in COS, I don't know if it is related.

Normally, I need to setup to move the read messages to deleted item folder after x days and flush them all.

In my testing environment, I have setup a testing agent that configure the options to move the read messages to deleted item folder after 1 day and flush them all. Two scripts should run at midnight everyday.

For example, I had 2 new plus 3 saved messages. All messages aged 1 days or more. However, the logs showed nothing to move and deleted for that mailbox....

Do I miss anything? Please advise.

Thanks

k.wiebe · ‎11-24-2004

Sounds like you've configured things properly. Gather up the log files from one of the midnight runs and I'll take a look.

chkt1 · ‎11-28-2004

I have reinstall the MSM, and now seems able to move and delete the VM.

Thanks for your help.