7.1 DSN Change

Usage and Config Platform
1

(imported topic written by SystemAdmin)

Hello,

It appears that my upgrade from 7.0.7.96 to 7.1 - the upgrade changed my system dsn (upgrade done through console fixlet). It was always bes_enterprise and now it is listed as only bes_.

The workstations that have the console installed are still pointing to bes_enterprise. I couldn’t figure out why my action regenerator died after the upgrade - until I did some verification and found the dsn suddenly different. When I changed the dns in the regenerator config - it started working again.

Since the upgrade - every few days the server needs a reboot - as no one can no longer login anymore - or actions come back with “not reported” - even though the agents report in timely - and there have been a few other strange occurences. Any idea what the implications for the change in dsn could mean and should it be changed back? Should I call this one into support?

Thanks!

Mike

2

(imported comment written by BenKus)

Hey Mike,

That is interesting and we haven’t heard of any reports of any of these issues… I would go ahead and contact support and see if they can figure it out…

Ben

3

(imported comment written by SystemAdmin)

Thanks Ben!

Yea - that is a strange one. I am not 100% certain that came about with the 7.1 update - or if happened prior. I had been having strange db connection issues prior to that - and really slow action deployments. But the regenerator stopped exactly the day of the update (as it has to point to the dsn) - so my guess is that name changed happened recently. I’ll shoot this over to support. Thanks.

Mike