Scheduler MailboxProcessor Setup Issues
Hi,
We appear to be having difficulties configuring the MailboxProcessor plugin.
We use Exchange server for our emails and apparently this poses a problem because we don't have a POP server. (Forgive me if I don't use the terminology correctly)
Our external emails come through our ISP to the Exchange server.
Can it be true that at no point do our emails go through any POP protocol?
If so, how do we setup the MailboxProcessor to work?
Please explain as simply as possible because I have to first understand it and then try and pass it on to the person doing the install.
Its taken over 3 weeks to get Scheduler installed just so we can use the MailboxProcessor and then when it came time to configure the MP this issue comes up! Surely it can't be this hard? I am starting to lose my patience!
RDunlop
· 1 |
|
Tuesday, October 21, 2008, 5:15:43 AM |
0
|
You just need to ask your exhange server admin to enable POP. |
||||
|
0
|
Could someone who has installed this perhaps give me an estimate of how much time it should take to install the Scheduler, turn on POP and enable and configure this code please?
|
||||
|
0
|
1 day is more than enough. |
||||
|
0
|
Thanks for the reply. Well, we still can't seem to get the Mailbox Processor working. I'm told that POP is enabled and working and I've now been supplied the config file and error log by the SA so hopefully someone can help! Here is the relevant bit from the config file: <MailboxProcessor Here is the error log from after starting the scheduler service (it is running as the Local System account) Event Type: Failure Audit COMPNAME application log: Event Type: Error Can anyone help please? Thanks in advance! |
||||
|
0
|
You seem to have a few issues:
|
||||
|
0
|
Thanks, I've forwarded that to the relevant people here, will let you know if they have any further issues/questions. |
||||
|
0
|
Ok, we've apparently updated the config file and now have a new error message. |
||||
|
0
|
Make sure that the componentID setting in the config file is a valid id of a component for your project. As for deleting the issues, you will have to do this via sql, I suggest you create a table with all the issue ids to delete (say issuestodelete) then run the following SQL: DELETE FROM geminiissuehistory where issueid in (SELECT issueid FROM issuestodelete) DELETE FROM geminiissuecomponents where issueid in (SELECT issueid FROM issuestodelete) DELETE FROM geminiissueattachments where issueid in (SELECT issueid FROM issuestodelete) DELETE FROM geminiissuecomments where issueid in (SELECT issueid FROM issuestodelete) DELETE FROM geminiissuelinks where issueid in (SELECT issueid FROM issuestodelete) DELETE FROM geminiissuelinks where otherissueid in (SELECT issueid FROM issuestodelete) DELETE FROM geminiissueresources where issueid in (SELECT issueid FROM issuestodelete) DELETE FROM geminiissuevotes where issueid in (SELECT issueid FROM issuestodelete) DELETE FROM geminiwatchissues where issueid in (SELECT issueid FROM issuestodelete) DELETE FROM geminiissuealerts where issueid in (SELECT issueid FROM issuestodelete) DELETE FROM gemini_issues where issueid in (SELECT issueid FROM issuestodelete) |
||||
|
0
|
Awesome thanks heaps! |
||||
|
0
|
While I'm tidying up the database, regarding the 2k+ issues, any ideas on why they have logged multiple times from one email and why all the links on them are blue/purple instead of green? |
||||
|
0
|
The reason why this is now working is because you have set a proper component id. If you set delete messages to false it should work as expected now. The promblem was that you have had emails that were not processed fully becuase of the exception so the mailbox kept trying to process them. At the moment you can not set the assignment of an issue. However, you could customise the code to do this quite easily. The source is downloadable for commerical license holder via the client portal. As for the issue with the links in the issue, can you send a screen capture of both so we can understand? send it to support at countersoft dot com with a reference to this thread. |
||||
|
0
|
Thanks very much, we will set it back to false now! |
||||
|
0
|
Yes, feel free to add it to our list: http://gemini.countersoft.com
|
||||
|
0
|
Thanks for the query, it worked great, except we found we had to add a line: DELETE FROM gemini_affectedversions where issueid in (SELECT issueid FROM issuestodelete) |
||||
|