Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

Cleanup Logins job fails

Archive

Last Post by Roquefort 4 years ago

6 Posts

2 Users

0 Reactions

201 Views

RSS

Roquefort

(@roquefort)

Posts: 3

Active Member

Topic starter

In looking through the event log on our SQL server, I noticed that there is a job that runs every minute which fails and therefore logs an error message. The job is "Cleanup Logins" which executes dbo.Login_proc. How can I troubleshoot to find out why this job fails every time?

Posted : September 3, 2020 7:03 am

acantu

(@acantu)

Posts: 722

Prominent Member

If it is Microsoft SQL, you should be able to go to the Job History and see the details of why the job failed.

Posted : September 3, 2020 7:19 am

Roquefort

(@roquefort)

Posts: 3

Active Member

Topic starter

Okay. In looking at the MSSQL Job History, I see that it tells me that "The login_proc procedure is already running on this database."

So, is the proc not finishing cleanly and simply stuck rendering subsequent attempts to execute it as failures?
How do I clean this up so I do not get an error every minute?

Posted : September 3, 2020 7:36 am

acantu

(@acantu)

Posts: 722

Prominent Member

May have gotten stuck. If you right-click on the Job, and select "Stop Job" see if that stops it. Then try running it again, and see if it completes.

Posted : September 3, 2020 7:39 am

acantu

(@acantu)

Posts: 722

Prominent Member

You can also go to "Job Activity Monitor" to see more details.

Posted : September 3, 2020 7:40 am

Roquefort

(@roquefort)

Posts: 3

Active Member

Topic starter

Attempt to stop the job failed because the job is not running.

I'm not a programmer, but I can see that the login_proc has code built in that prevents it from executing if it is already running. That code is tripping every time it is run.

It is executing sp_getapplock which is apparently returning a result that is < 0 causing it to error out. However, when I execute sp_releaseapplock, I get an error indicating that it cannot release the application lock because it is not currently held.

Posted : September 3, 2020 8:20 am

Forum Jump:

Share:

24 Forums
9,942 Topics
39.9 K Posts
1 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0