Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Not able to login Orion web-console

Hi Friends,

We are not able to login Orion web-console and getting session time out error while trying to login.Every two days i am getting this error.Can anyone please help me.

Find more posts tagged with

Accepted answers

All comments

kiruthika2331

Hi Friends,

"Transaction log space full" can cause web-console login issue in solarwinds Orion?.

sum_giais

Do you know if it’s the issue? Where did you get lead to that - just curious.

If your transaction log is full it will cause all sorts of grief for you in your environment, logging in may be the least of the issues. Basically it will cause the database to seize up.

I’ve always used the following sql query to check my transaction log space.

DBCC SQLPERF(logspace)

Below is a link to Microsoft Docs that can provide some other ways to get that info.

https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-db-log-info-transact-sql?view=sql-server-ver15

Hope this helps

shuth

If your transaction log is full, that can block you from logging in with domain accounts.

The database can't update with the domain details and will block login. You should be able to log in with local Orion accounts but the transaction log full is a more serious issue that you should investigate (as @sum_giais said).

If you're using FULL recovery model for the database, you should be backing up the database frequently to reduce the size of the transaction log.

kiruthika2331

Hi All,

Thanks for your consideration and reply.

Please let me know if anything needs to be done from Orion side for this transaction log or database team needs to take care of it?

shuth

The database team will need to fix it but you will need to determine what is causing the log to fill up. The SQL team should be able to help on that front as well.
It could be any number of reasons:
- ran out of disk space on the drive hosting the transaction log because it's too small
- a massive query that creates transaction log issues
- "Full" recovery model database that is not being backed up often enough
etc