TDeliverQuarantineThread.Execute Error | 
 
    Post Reply  
   | 
  
| Author | |
   
   ebzed  
   
   Newbie  
   Joined: 10 November 2006 Location: Israel Status: Offline Points: 19  | 
  
   
      Post Options
    
        Thanks(0)
      Quote   Reply
   
     Topic: TDeliverQuarantineThread.Execute ErrorPosted: 23 February 2015 at 10:13am  | 
 
| 
   
    
   Hello, 
   
  Just upgrade to latest version and also from 32bit to 64Bit, I keep seeing all the time Exception Occurred during TDeliverQuarantineThread.Execute: Provider Cannot be found - It may not properly installed  We dont use Quarantine at all... Please advice.  | 
 |
![]()  | 
 |
   
   LogSat  
   
   Admin Group  
   Joined: 25 January 2005 Location: United States Status: Offline Points: 4106  | 
  
   
      Post Options
    
        Thanks(0)
      Quote   Reply
   
     Posted: 23 February 2015 at 10:51am | 
 
| 
   
    
   
ebzed, 
   
  If you switched from the 32bit to the 64bit version of SpamFilter, depending on how you constructed the connection string to the database, you may need to use the 64-bit ODBC administrator to create a new DSN for the database. This is because if you previously used the 32-bit ODBC administrator for the 32bit version of SpamFilter, then that 32bit entry won't be visible to the 64bit environment. If this is not the issue, can you please  zip us the following so we can take a look: 
 If the zipped file is over 8MB in size, please try to upload the file to our repository at: https://cloud.logsat.com/public.php?service=files&t=ec1a5cd65f702ae7d9cacfe951fe063a I'll provide the password in a separate PM.  | 
 |
![]()  | 
 |
   
   ebzed  
   
   Newbie  
   Joined: 10 November 2006 Location: Israel Status: Offline Points: 19  | 
  
   
      Post Options
    
        Thanks(0)
      Quote   Reply
   
     Posted: 23 February 2015 at 1:56pm | 
 
| 
   
    
   Thanks Roberto, 
   
  I Actually found the issue,  As mentioned we do not use Quarantine, But we had an old string set in the configuration file, on the 32Bit we never saw any warning, but on the 64Bit we started to see them, Removing the connection string from the .ini file solved the problem... Thanks, Eran.  | 
 |
![]()  | 
 |
    Post Reply  
   | 
  |
|       
  
  Tweet   	
    | 
 
| Forum Jump | Forum Permissions  ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum  | 
 
This page was generated in 0.094 seconds.
 
 
 
 
 
 
 Topic Options
   
 Post Options
 Thanks(0)
 

   