Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 270 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
ERROR WHEN TRYING TO ACCESS CURRENT SESSIONS
andrew_rampton
Member Posts: 8
we have NAV 4.0 SP2 and have encountered a permanent problem when trying to access current sessions under file... database.... information...
the message we get is attached
can anyone help with a solution on this one ?
thanks
andrew
the message we get is attached
can anyone help with a solution on this one ?
thanks
andrew
0
Comments
I think you can check Waldo's blog or partnersource to find the related KB article
"Never memorize what you can easily find in a book".....Or Mibuso
My Blog
as a novice user and new to this forum can you explain further what you mean and perhaps give me a link to the article
regards
andrew
The work around is below. Just a tip if you actually type in the error message in google or mibuso you find the answer pretty quickly rather then asking.
WORKAROUND
Difference of two datetime columns caused overflow at runtime
Hi,
This error, occuring in the Sessions tab of the File Database Information window in NAV 4.00, will be solved in NAV 4.00 SP3. For the time being, you can apply the following workaround.
In SQL Server, NAV creates a view called “Session” in the NAV database. You can modify the definition of the view as followed:
Replace CASE WHEN SP.[cmd] = 'AWAITING COMMAND' THEN CAST(DATEDIFF(SECOND, SP.[last_batch], GETDATE()) AS BIGINT) * 1000 ELSE 0 END AS [Idle Time]
with CASE WHEN SP.[cmd] = 'AWAITING COMMAND' THEN CAST(0 AS BIGINT) ELSE 0 END AS [Idle Time]
Every time a new NAV database is created in SQL Server, the view needs to be modified manually unless NAV 4.00 SP3 is used.
in this case, you should contact your partner. You probably don't have the skills needed to fix this (its not just a case of knowing SQL, you need Navision knowledge as well). Playing with it in house could damage your system.
PS its odd that your partner did not inform you of this issue, since it has been known for a long time now. I would ask them what their procedures are for informing you of known bugs and fixes. Who knows what other problems your system may have.