Email-Manager, Error with Method FindRecord. Error Message = [DBNETLIB][ConnectionWrite (send()).]General network error

Hi everyone

we successfully used the Email-Manager in a SageCRM V2018 R3 Install to import Leads from a website (WebSite sends Email with values from a form) and it was working perfectly.

Around one week ago, the processing of the script suddenly stopped to work and is now throwing an SQL Error "[DBNETLIB][ConnectionWrite (send()).]General network error".

What is somehow strange is the fact that this error only shows up after the Method "FindRecord" is used. More exactly, as soon as the object returned from the method is queried (Either by checking if it is null or if EOF is false or trying to read a field of it).

Filling the lead with "static" values (Company Name from Email or just a string) is working ok and the lead gets created. Another strange thing is that the exact same script works without problems on a Test-Server with same OS, SQL, etc.

SageCRM itself is running with no problems.

So here my questions:

- Does anybody know what this SQL Error means ? Google tends to give me answers that it has something to do with network-problems ?

- Is there a way to debug the execution of the Email-Script, other than the debug-mode ?

- How exactly is the email manager connecting to the db and how could i simulate that to reproduce the error ? A small 32bit c# form based on dot.net 2.0 can execute the sql like 100 times in a row without showing any errors.

Any hints or tipps would be greatly appreciated 

Kind regards

Sacha

  • I would first find out what has changed because something has changed. Whether it is a configuration change on the SQL server, or a Windows update, but something has changed.

  • I could fix it, so just in case somebody else has this problem in the future ....

    - The password for the emailmanager ("EMPassword") was encrypted in the registry. After writing the password in the registry in clear text everything works again.

  • in reply to Sacha Woodtly

    Thanks for sharing the solution but did you work out why it suddenly stopped working?  As Vega pointed out, something must have changed.

  • in reply to Guy Cecil

    The test-server is a cloned image of the production server, so the password must have been originally stored in clear text and then later overwritten with an encrypted version (probably by entering the password in the admin-area). The system itself is not a fresh install but has been updated several times during the last years.

    Unfortunately i forgot to export the registry-key (text-export) before changing it manually to check for the last updated-date and to be able to compare this date with the date the errors started to show up.

    I checked with a fresh demo install and changing the password in SageCRM results in an encrypted string in the registry.

    Maybe the encryption method changed over the years and the email-manager gets confused when entering the password in the admin-area in sagecrm (i think i found some post on this forum that described a similar problem).