You’re offline. This is a read only version of the page.
714
Hi Team,
We are using Navision 2009R2 Web Service for one of our client in house portal. Now customer complaint our portal is too slow and time out. I wrote simple app(c#) to read item record and get back response time. After that i create new database on their server and restore the database on new database. New database has only 4 users. I lunch my test tool to get response time. Response time is 31ms for one record. 100 times i open at same time. Response is between 31~36 and all are keep response. I thought their database having issue and never maintain. I plan to create new database and restore their include user. I tested again with my test tool. This time response is become too high 46ms~62ms. And no more response if i open more than 5 app. Again,i drop all user and add only 4 user. This time response is become 31ms again and no time out and keep going if i open 100 times at same time . So What is related between Web Service and Window Login. I can't figure it out.
But they are using different domain user to access the navision. Can it be issue on Web Service?
SQL Version 2005 SP3
NAV 2009R2 (3 Tier installation)
OS 2003R2
Regards,
Yukon
*This post is locked for comments
I have the same question (0)
hi,
only some suggestions.
Calling NAV Webservices a lot of response time is spend by authentication; try to authenticate using NTLM instead of Kerberos and force TCP protocol.
if you are using Kerberos with Kerberos tickets, check trusted delegation &SPN (duplicated, lost etc.); try to reset kerberos tickets (with purge)
NAV WS Standard Trace
You can try to activate diagnostic tracing for Web Services to identify bottlenecks
blogs.msdn.com/.../enabling-diagnostic-tracing-for-dynamics-nav-web-services.aspx
Try to install last NAV 2009R2 builds, some bugs have been resolved about WS Authentication
blogs.technet.com/.../microsoft-dynamics-nav-2009-r2-fixes.aspx
Share
Report
All responses (
Answers (
