Hi everyone,
We have this customer who has an issue with the notification alerts. Long story short, we were able to reproduce this bug (which dates back to 2009 since I found http://www.symantec.com/docs/TECH71391 with exactly the same workaround as http://www.symantec.com/docs/TECH215522 and http://www.symantec.com/docs/TECH200949) in our lab.
Lab and Customer environment as follows:
- DLO Server
- W2K8 R2 x64
- DLO 7.5 SP1 x64
- MTA being used for notifications is an Office 365 Account (with stunnel for SSL/TLS purposes).Notifications are working properly.
We have done the following:
- Create virtual environment for LAB with snapshotting (to be able to rollback). Virtual environment is an AD, Firewall/Router, DLO Server and a DLO client (Windows 7 based).
- Install stunnel for TLS/SSL proxy for Office365 or Google Apps.
- Install DLO 7.5 SP1 x64 with the default configurations (with the provided SQL 2008 SP1 x86 database) with all roles and configure it. Test notifications.
- Configure DLO with Admin Console.
- Deploy an Agent.
In this scenario, notifications comes according to TECH71391 / TECH 215522 / TECH200949. We followed the articles to the letter with no success.
We did a rollback and done the following:
- RollBack
- Install SQL Server 2008 R2 SP1 Express x64 edition (according to TECH215522 the cause is the difference with SQL being x86 and the OS x64) with a DLO named instance. Named pipes were enabled.
- Install stunnel for TLS/SSL proxy for Office365 or Google Apps.
- Install DLO 7.5 SP1 x64 pointing the database to the installed DLO instance with all roles and configure it. Test notifications.
- Configure DLO with Admin Console.
- Deploy an Agent.
Again, no success. Alert notifications are still coming exactly as the above scenario.
Downgrading to x86 is not an option because the solution will be coexisting with other applications.
Please let us know about your experience. Out customer and us are deeply concerned about this bug / defect being discovered / identified in 2009 and still haven't found a way to fix it permanently.
Regards,
Marco Tafur
