From: Jiří Č. <ji...@ci...> - 2017-12-07 17:15:38
|
> For example, one instance run in user session (for ex. embedded > connection) > and second instance run as a service. That was original idea for hunting - disabling that somehow and then waiting where something breaks. I'm at least blindly trying to find some application doing this. Also sometimes the error pops up from "on connect" or "on begin transaction" trigger, not when attaching. Right now for example: At trigger 'DBCONNECT' line: 6, col: 3 ---> Database is probably already opened by another engine instance in another Windows session This trigger is only accessing MON$ATTACHMENTS. -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ |