I
I
Ilya Pushkin2021-09-29 09:44:20
1C
Ilya Pushkin, 2021-09-29 09:44:20

Why did a separate terminal user stop connecting to 1s 7.7 SQL?

Please, I ask you to do without the obvious recommendation to upgrade to 8.3, this work is in progress

. There are 2 servers 2008 r2, one acts as a domain controller and the second MS SQL server as a terminal, where only 1C 7.7 is launched.
There is a problem - some terminal users can easily connect to the database and work in 1C, and in some the connection to SQL was lost. When opening the database, an invitation to enter a password opens, but after that the connection to the database is not established. At the same time, port 1433 telnets and other users from the same machine come in.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
H
hint000, 2021-09-29
@hint000

and some lost connection with SQL
Why do you think the connection to SQL was lost? In this case, there would be no password prompt.
Another question.
some terminal users can easily connect
Check, is it about Windows users or is it about 1C users?
Go to the terminal server as a "problem" user, and try to go to 1C under a different (not problematic) user.
Third question. I don't remember, in 7.7 there was a log, the same as in 8.*? If it was, then look at the log entries at the time of unsuccessful login attempts.
The fourth question. I don’t remember, in 7.7 there was a miraculous (correcting the most mysterious glitches) procedure for deleting the cache in the user profile?

A
Alexander Prokhorovich, 2021-09-29
@alexgp13

Try to close all sessions, delete the .lck lock files and check the rights to the 1C folders of problem users - most likely, one of the problem users does not have enough rights and because of it, access is broken for all subsequent ones.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question