ASG RD Startup failure

[mertens79]

Hi Support,
 
We recently installed the new version of visionapp / asg remote desktop 2018.
 
Then I made a portable version (asg 2018 patch 5 with the option enabled for the connections for the database included) and placed that on a network share.
 
When I try to start it on a terminal server /  remote desktop server (windows 2008 r2) session as a “standard” user I get the message “connection could not be established”
When I logged in as a user with administrative right and then start the program It works, when I use then runas (from that administrative session) the program with the standard user credentials I get the same error.
 
For database/visionapp access I can use both (my standard and my administrative account) to start the program the only thing that’s not working is just that I start a rdp session with a standard account and can’t start asg, I need that administrative account to start asg correctly.
 
I also tried the asgrdelevated.exe file but I experience the same problem.
 
What log file can I check /  or settings to get this working?
 

[DevOma]

Sorry, forgot to answer you sooner...

The error message just tell me that you can't connect to the database server/instance with your current user - I think you have configured to "use integrated auth" so the Windows Account is used to authenticate against the SQL instance... if you have no permission you can't connect to the database...

Or is the problem only related to Patch5? We made some changes in the login - but I think it should not related to the SQL server login...

[pvasirani]

Sorry, forgot to answer you sooner...

The error message just tell me that you can't connect to the database server/instance with your current user - I think you have configured to "use integrated auth" so the Windows Account is used to authenticate against the SQL instance... if you have no permission you can't connect to the database...

Or is the problem only related to Patch5? We made some changes in the login - but I think it should not related to the SQL server login...

Hi

I have the same problem
 - The "Test Connection" in "Database environment" says "Connection Check Successful" (with integrated authentication)
 - The user can connect successful from another computer
 - The user that works fine with another computer don't work with this computer
 - The inline firewall show "test connection" call but don't show any call during the connection
 - The computer os is Win 7sp1 build 7601
 - The problem is present with ASG-RD 2017 and 2018 any version
 - The computer worked fine with VisionApp 2010-2015

[DevOma]

Did the user login to the Windows system with the same account? Both computers are joined to the same domain? Then it should work, because you can reach the database instance and if the user is the same it should be possible to connect to the database on both computers

[pvasirani]

Did the user login to the Windows system with the same account? Both computers are joined to the same domain? Then it should work, because you can reach the database instance and if the user is the same it should be possible to connect to the database on both computers

Yes, the account is the same, and both computers are joined to the same domain.

Considering what was reported before

  - why does the test work and not the connection?

  - why does the firewall record the test call while it does not record anything during the connection?

Thanks for the support

[DevOma]

Ok, there is a difference in just opening a connection for a specific database instance and calling a stored proc - I think it's related on the .NET framework implementation.

If you try a "OpenConnection" the sql server should answer if the request can pass to the specified database - but the connection is not really created because .NET uses a connection pool and decides itself when to create/close the connection. But if the code try to execute the Stored Proc "ConnectionTest" the connection should be created - and this can fail even if the "OpenConnection"-command did not fail - that's the reason why we call before any command an empty StoredProc just to see if the connection is really open/successful or not - if not we switch to OfflineMode :-)

[pvasirani]

Ok, there is a difference in just opening a connection for a specific database instance and calling a stored proc - I think it's related on the .NET framework implementation.

If you try a "OpenConnection" the sql server should answer if the request can pass to the specified database - but the connection is not really created because .NET uses a connection pool and decides itself when to create/close the connection. But if the code try to execute the Stored Proc "ConnectionTest" the connection should be created - and this can fail even if the "OpenConnection"-command did not fail - that's the reason why we call before any command an empty StoredProc just to see if the connection is really open/successful or not - if not we switch to OfflineMode :-)

Sorry, i don't understand if you want that i do something, and how, or if you explain how the software works.

Can you confirm that the minimum version of .NET is 4.0

Thanks

[DevOma]

The latest version requires .NET 4.6.2 - I just wanted to explain the difference of the function "Test Connection" and "Connect to an environment" - perhaps that should not be handled in different ways - I will add an issue to the ToDo-List that this will be fixed

[pvasirani]

The latest version requires .NET 4.6.2 - I just wanted to explain the difference of the function "Test Connection" and "Connect to an environment" - perhaps that should not be handled in different ways - I will add an issue to the ToDo-List that this will be fixed

The computer that have problem has Dot Net 4.7 installed

Thanks
Paolo