This discussion is archived
10 Replies Latest reply: Mar 4, 2013 8:53 AM by Trey RSS

Could not create an object of type 'CDO.Message'

Trey Explorer
Currently Being Moderated
we started seeing this error in our ProdikcCommon event logs at about 8AM on 2/12 on our GSM Server. Any idea what could be causing it?
As a result users are not receiving email notifications from GSM.


2/15/2013 11:04:11 AM     Error     0     Could not send email message: Recipients: randall.allison@tyson.com; Subject: An action must be performed on Sourcing Approval XXX (Sourcing Review)
2/15/2013 11:04:11 AM     Error     0     Could not send email message: Recipients: randall.allison@tyson.com; Subject: An action must be performed on Sourcing Approval XXX) (Sourcing Review)
2/15/2013 11:04:11 AM     Error     0     System.Web.HttpException: Could not create an object of type 'CDO.Message'. Please verify that the current platform configuration supports SMTP mail. at System.Web.Mail.SmtpMail.LateBoundAccessHelper.get_LateBoundType() at System.Web.Mail.SmtpMail.CdoSysHelper.Send(MailMessage message) at System.Web.Mail.SmtpMail.Send(MailMessage message) at Xeno.Prodika.Services.Email.EmailService.MessageHandler()

Its this pattern of these 3 msgs every time it doesnt work.
  • 1. Re: Could not create an object of type 'CDO.Message'
    dmccall Newbie
    Currently Being Moderated
    Should we go ahead and open an SR for this?
  • 2. Re: Could not create an object of type 'CDO.Message'
    Matt J Journeyer
    Currently Being Moderated
    This seems like a Microsoft issue, not a PLM4P issue. i did a quick search and came up with this kb article as a starting point, http://support.microsoft.com/kb/910360.

    a few things to check:
    - in environmentvariables.config, is the value for Prodika.From.EmailAddress a valid email address?
    - were any changes recently made to the app server? updates applied?
    - were any changes recently made to the email server?

    thanks,

    -M
  • 3. Re: Could not create an object of type 'CDO.Message'
    Trey Explorer
    Currently Being Moderated
    We tried an IIS Reset, but that didnt help.
    I somewhat agree that it seems to be an MS issue. However, why is it only Sourcing Approval noticification emails? All other notifications from GSM on this server are working fine.

    - in environmentvariables.config, is the value for Prodika.From.EmailAddress a valid email address? This was the first thing we checked as it was the first thing we saw in google too. config hasnt changed
    - were any changes recently made to the app server? updates applied? We have had no MS updates since 11/13/12 on this server.
    - were any changes recently made to the email server? I havnt asked about the email server thinking if that was it all emails would be foobared.

    I guess we will try a server reboot this Sunday during maint window.
    Let me know if you think of anything else please.
    --Trey                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               
  • 4. Re: Could not create an object of type 'CDO.Message'
    Chris1 Newbie
    Currently Being Moderated
    We just had the same issue over the weekend, ironically. The cause was that our prodikaadmin account was locked.
  • 5. Re: Could not create an object of type 'CDO.Message'
    Trey Explorer
    Currently Being Moderated
    It was just your Sourcing Approval emails notifications?
    When you say prodikaadmin was locked, what do you mean? Locked in Active Directory or UGM?

    We use LDAP so we have an LDAP-ProdikaAdmin account, but its not locked. Im able to login to the PLM4P with it.
    And the SetupAsstistant uses a service account.

    I see LDAP-Prodikaadmin and prodikaadmin accounts in UGM. Im not aware of any config that uses prodikaadmin...
  • 6. Re: Could not create an object of type 'CDO.Message'
    Chris1 Newbie
    Currently Being Moderated
    Trey -

    It was actually only for NPD notifications. We also have LDAP integration (to active directory), so we have a prodikaadmin account in active directory on our domain. When this gets locked it causes all sorts of issues, but it does not seem to be the case for you since you can still log in with it.
  • 7. Re: Could not create an object of type 'CDO.Message'
    Chris1 Newbie
    Currently Being Moderated
    Trey -

    It seems like the prodikaadmin account being locked was not the cause after all as we had more notification failures later today. We were able to recycle NPD and it appears that has corrected the issue. Sorry for the confusion.
  • 8. Re: Could not create an object of type 'CDO.Message'
    Chris1 Newbie
    Currently Being Moderated
    We found that this happens after we restart the NPD application pool. We have been restarting it twice a week because the connection pool fills up.
  • 9. Re: Could not create an object of type 'CDO.Message'
    Trey Explorer
    Currently Being Moderated
    Well, Sunday during maint window we scheduled a reboot of the server.
    Today Sourcing Approval notification emails are working again.
    Wheeeeee!!!!!!
  • 10. Re: Could not create an object of type 'CDO.Message'
    Trey Explorer
    Currently Being Moderated
    Update: On Sunday all GSM notifications email started failing with this error, not just Sourcing Approvals.

    So we followed the instructions for Method 1 & 2 listed here: http://support.microsoft.com/kb/910360#appliesto
    Then restarted the SMTP Email that is under ASP.NET in the IIS manager.

    After that emails started sending again.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points