Skip to content


SmartView timeout crashes GP

doncarver asked 9 years ago
I'm trying-out SmartView 2010 (11.0.41) with Dynamics GP 2010r2.  When SV times-out on a search, it crashes and brings down the entire GP app.  Quicker searches on the same oject (Financials>Account Transactions) work OK.

The same search in SmartList takes the same or longer time to process, but it doesn't time-out, and it does return the few rows expected.

I didn't see anything meaningful using the GP Support Debugging Tool.

Please help; looking forward to purchasing and using SmartView successfully,
Best Answer
Nicole answered 9 years ago
SmartView should be using the SQL Query timeout settings. It shouldn’t be timing itself out. If you run a SQL Trace with the errors turned on, do you see the timeout there? The Account Transaction SmartList does not use just one select statement to get the data, but uses a bunch of stored procedure calls to get the data. The SmartView list will use one main SQL query to get the data. So, if the query timeout in SQL Server is too small, it will timeout that query on SmartView. Thanks, Nicole
DonCarver replied 9 years ago

The SQL trace does not show a time-out. And the only error in the event log is an Unhandled Exception in the Application Log:

Faulting application name: Dynamics.exe, version: 11.0.349.0, time stamp: 0x4d9b8c91
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0xe0434f4d
Fault offset: 0x0000c42d
Faulting process id: 0x1744
Faulting application start time: 0x01cf6f757655e0eb
Faulting application path: C:Program FilesMicrosoft DynamicsGP2010Dynamics.exe
Faulting module path: C:Windowssyswow64KERNELBASE.dll
Report Id: 6a2379a6-db69-11e3-ae4d-bc305bba15d6

After a few attempts, probably due to SQL optimization during the repeated queries, SV does return results without faulting.

Nicole answered 9 years ago
If you capture the select statement from the SQL Trace that it is trying to run and run that in SQL Management Studio, does it return appropriately? This may be something that the support team needs to look at. If you would like, you can contact them at
DonCarver replied 9 years ago

The SQL statements from the Trace return appropriately when copy/pasted into SSMS.  I phoned support and never got a callback from whom they referred my issue…I'll try the support email.  Thanks for the suggestions!

Nicole replied 9 years ago

We have contacted you through the support case.

For others reading this forum, we will post the resolution when complete.

Billc replied 8 years ago

Hello, I am having similar issue. Has this been resolved? Thank you,


doncarver replied 8 years ago

No.  From the prior forum response, EOne evidently opened a support case for this, but I haven't been contacted by them.

We did go ahead an purchase SV…it works most of the time…we still crash out of GP if the search runs long.  All my SQL traces showed no errors on the SQL side, and the queries run to completion if copied/pasted/executed in SSMS, so it would appear that it crash is caused by SV.  If I repeat the query a couple times, such that SQL Server has optimized/cached data to the point where subsequent calls are "more efficient", SV does not crash.

Billc replied 8 years ago

I think you are correct about timeout issue. I have one that returns top 1000. That causes the issue. Reduced that to 10, and no issue. Changed it to 100, and issue returns.

Look forward to the answer.



wahlga replied 8 years ago

Has this been resolved yet?  We have several smartlists that cause GP to crash and these seem to be either ones that return a lot of rows or ones that may take some processing before returning any results.  I have been in contact with support but I saw this thread and wondered if it may have been resolved.

doncarver replied 8 years ago

Unfortunately, I have never received any resolution to this.

billc replied 8 years ago

Our vendor has requested the fix, whatever that is, and eOne has not responded yet.

Jared replied 8 years ago

We are currently working on the issue.  At this time we do not have a fix, but we will let you know as soon as we do.  Thank You.

Jim replied 5 years ago

I know this issue is old, but is there any update on a resolution? We’re still running into this with GP2015 and SV 14.0.6

Patrick Roth Staff replied 5 years ago

Assuming the issue is really a query timeout, then think we can resolve:
In your dex.ini, add the line:


where xxxx is the number of seconds you want to allow long running queries to run.

You could be able to set it to 0 which means “infinite”. Not desirable necessarily since a long running query will run and run. But it does beat crashing GP I suspect.

Reply back and let me know if that fixes it.

If you would like to submit an answer or comment, please sign in to the eOne portal.