Answer the question
In order to leave comments, you need to log in
Flies license 1C?
Good afternoon, colleagues.
There is a server 1C.
Activated a license for it, and a license for the Nth number of users.
Starts up, works.
Then, about once a day, when starting 1C, an error about the absence of a license crashes. After restarting the agent-1C server, the error disappears and everything works further. What could be the problem?
Thank you!
Answer the question
In order to leave comments, you need to log in
If at the moment when the message about the absence of a license appears, you have other users who continue to work in the program, then this means that the license does NOT crash, but the number of connections has been exhausted.
Most likely, the problem is that when you exit the program, the license is not released and another license is used when you log in again. And so on until all N licenses are exhausted. Restarting the 1c agent helps to reset all occupied licenses. There can be many reasons, if, for example, RDP is used, then there are problems with the printing process. As a solution, you can reduce the termination timeout and add the problematic process to the list of automatically terminated when the terminal session ends. More details are here , but the problem may be elsewhere.
The license is tied to the parameters of the hardware on which it is installed, i.e. if there are any deviations of the parameters recorded at the time of registration, the license thinks that this is a different computer.
Here are the conclusions.
The problem could be in a dozen different places. There are few details in your question, starting from the lack of which particular license is swearing - server or client.
Perhaps it really is - licenses (client) end, and a message is issued. After restarting the server, all sessions fall and the licenses are released again, which is logical.
Let's get more details - how many users, how many sessions, what message, what is written in the log on the "Details" button after the absence message appears, and so on.
Similar problem. All that was done the day before was to expand the hard drive by 100 GB. NOT changed, but expanded. And only the web client is crying, you go in as usual and there are no problems. Users watched 25 out of 50 are busy only, so this is unlikely to be the reason (although maybe I don’t know what). Looked in the console of administration of servers.
Restarting the agent helps without problems, as does rebooting the entire server. But something is problematic and it’s not right to overload something there in the morning every time. If you have any ideas what else to see and how I will be very happy to help.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question