Error using ole automation to send CDO Email in SQL Server 2000 -


I'm tearing my hair on this one lately (about a month or earlier) on our SQL 2000 server Some stored procedures have stopped sending email. We have several versions of the same stored work in different databases, all of which are broken at the same time (I think this is a bad design, but it is not that I What do I want to discuss) :))

stored type Procedures using eg automation to send Ole email. 

  EXEC @resultcode = sp_OACreate 'CDO.Message', @Imsg OUT EXEC @resultcode = sp_OASetProperty @iMsg, 'to', 'someguy@domain.com'   
 For any reason now  sp_OASetProperty 'to', 'From', 'Subject' or 'TextBody' is failing while setting the properties  @amjb is not zero, so do the construction Used to be. Apart from this sp_OASetProperty still works for some other properties:  
  EXEC @resultcode = sp_OASetProperty @iMsg, 'Configuration. Field ("http://schemas.microsoft.com/cdo/configuration/sendusing"). 'Value', '2' acec @ root code = sp_OASetProperty @imsg, 'configuration. Fields ("http://schemas.microsoft.com/cdo/configuration/smtpserver"). Value, 'smtp.domain.com'   
 The result code that comes back when sp_OASetProperty fails -2147220991 provides the following information using SP_OAGetErrorInfo Error: 0x80040201, Source: NULL, Description: The exception was generated at the 0xc0000005 address ...  
 Some other information that makes it very difficult to debug:  
     
  •  Only the Prod server, the test, the utility & Amp; amp; The developer machine is fine (and all are using the same SMTP server)  
  •  The stored procedures have not recently been changed, they have just broken one day (and we have not noticed for a while It is difficult to decide what other changes are.  
  •  I have written a quick dotet app and put it on the server to check email connectivity and it worked fine  
  •  I have my place Try to change "odsole70.dll" to file with the server one and it still worked fine, so I do not believe that it is a corrupt DLL  
  •  I put it here All possible combinations of information have been accelerated, but have no advantage    
     
     
     This The problem has been solved by restarting the SQL service that was detected that some changes were made to the Exchange server. This is probably only the issue of production Was seen as the test servers are rebooted more frequently.

Comments

Post a Comment