[6.1] FRx Export SQL Timeout

Todd sure would like to talk to you about SQL and Vantage. Give me your
number via email off list and I will call you... if you Can spare the
time



Thanks,



Bob Sanders

Kerusso Inc.

870-423-6242 ext. 263

bob@...



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Todd Caughey
Sent: Monday, November 12, 2007 11:15 AM
To: vantage@yahoogroups.com
Subject: RE: RE: [Vantage] [6.1] FRx Export SQL Timeout



OK. Never mind. The export issue was resolved in 6.10.543 per SCR 8212
and we are on 536. I will load 543 on the new server in a few weeks and
that should be the end of the export error.
-Todd C.

________________________________
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
[mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
Behalf Of Todd Caughey
Sent: Monday, November 12, 2007 9:35 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] [6.1] FRx Export SQL Timeout

We got part of this resolved via Web Ex. Although the index build fails
in the export it gets re-done anyway in the report running process. The
errors in the actual report were a seperate problem related to linking
to an external spreadsheet and not related to the export error. There
still remains the actual export error but the workaround seems to be to
ignore it. Frank at Epicor is going to look into that but if anyone has
any ideas on the SQL side as to why the build index phase timesout for
large period spans it would be nuch appreciated.
Thanks,
-Todd C.

________________________________
From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com
<mailto:vantage%40yahoogroups.com> <mailto:vantage%40yahoogroups.com>]
On Behalf Of Todd Caughey
Sent: Monday, November 12, 2007 8:26 AM
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] [6.1] FRx Export SQL Timeout

To their credit Epicor's support staff has been very diligent on the
following issue and I am waiting to set up a WebEx session for them to
take a look at our systems...but time is running short on my boss's
patience so I will see if anyone here, particularly SQL Server experts,
has any suggestions.

When exporting large date ranges from Vantage (6.1) the export process
produces the following error at the 99% level (after running 3 hrs) in
the building indexes phase....
--------------------------------------
Error occurred while accessing component property/method: Execute
[Microsoft][ODBC SQL Server Driver]Timeout Expired
Error code: 0x80020009 SQL_Table_Build GL/GLFRx10-mn.w (5890)
--------------------------------------
I have ruled out Vantage inactivity timeout and at support's suggestion
set the ODBC settings for SQL Server pool connectivity timeout from 60
seconds to 14,400 seconds with no positive result. I have been thinking
there my be something on the SQL Server database side but don't know
enough about SQL Server to know where to start or if there are even
timeout settings on the server. Shorter date ranges (2 years instead of
4) work fine. Another thought is if there is an inherent limit in the
SQL DB schema that gets recreated with every export that can't handle a
certain number of years. Has anyone out there that uses FRx been able to
export four or more years of data?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co,

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
To their credit Epicor's support staff has been very diligent on the following issue and I am waiting to set up a WebEx session for them to take a look at our systems...but time is running short on my boss's patience so I will see if anyone here, particularly SQL Server experts, has any suggestions.

When exporting large date ranges from Vantage (6.1) the export process produces the following error at the 99% level (after running 3 hrs) in the building indexes phase....
--------------------------------------
Error occurred while accessing component property/method: Execute
[Microsoft][ODBC SQL Server Driver]Timeout Expired
Error code: 0x80020009 SQL_Table_Build GL/GLFRx10-mn.w (5890)
--------------------------------------
I have ruled out Vantage inactivity timeout and at support's suggestion set the ODBC settings for SQL Server pool connectivity timeout from 60 seconds to 14,400 seconds with no positive result. I have been thinking there my be something on the SQL Server database side but don't know enough about SQL Server to know where to start or if there are even timeout settings on the server. Shorter date ranges (2 years instead of 4) work fine. Another thought is if there is an inherent limit in the SQL DB schema that gets recreated with every export that can't handle a certain number of years. Has anyone out there that uses FRx been able to export four or more years of data?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co,



[Non-text portions of this message have been removed]
We got part of this resolved via Web Ex. Although the index build fails in the export it gets re-done anyway in the report running process. The errors in the actual report were a seperate problem related to linking to an external spreadsheet and not related to the export error. There still remains the actual export error but the workaround seems to be to ignore it. Frank at Epicor is going to look into that but if anyone has any ideas on the SQL side as to why the build index phase timesout for large period spans it would be nuch appreciated.
Thanks,
-Todd C.

________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Todd Caughey
Sent: Monday, November 12, 2007 8:26 AM
To: vantage@yahoogroups.com
Subject: [Vantage] [6.1] FRx Export SQL Timeout


To their credit Epicor's support staff has been very diligent on the following issue and I am waiting to set up a WebEx session for them to take a look at our systems...but time is running short on my boss's patience so I will see if anyone here, particularly SQL Server experts, has any suggestions.

When exporting large date ranges from Vantage (6.1) the export process produces the following error at the 99% level (after running 3 hrs) in the building indexes phase....
--------------------------------------
Error occurred while accessing component property/method: Execute
[Microsoft][ODBC SQL Server Driver]Timeout Expired
Error code: 0x80020009 SQL_Table_Build GL/GLFRx10-mn.w (5890)
--------------------------------------
I have ruled out Vantage inactivity timeout and at support's suggestion set the ODBC settings for SQL Server pool connectivity timeout from 60 seconds to 14,400 seconds with no positive result. I have been thinking there my be something on the SQL Server database side but don't know enough about SQL Server to know where to start or if there are even timeout settings on the server. Shorter date ranges (2 years instead of 4) work fine. Another thought is if there is an inherent limit in the SQL DB schema that gets recreated with every export that can't handle a certain number of years. Has anyone out there that uses FRx been able to export four or more years of data?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co,

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
OK. Never mind. The export issue was resolved in 6.10.543 per SCR 8212 and we are on 536. I will load 543 on the new server in a few weeks and that should be the end of the export error.
-Todd C.

________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Todd Caughey
Sent: Monday, November 12, 2007 9:35 AM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] [6.1] FRx Export SQL Timeout


We got part of this resolved via Web Ex. Although the index build fails in the export it gets re-done anyway in the report running process. The errors in the actual report were a seperate problem related to linking to an external spreadsheet and not related to the export error. There still remains the actual export error but the workaround seems to be to ignore it. Frank at Epicor is going to look into that but if anyone has any ideas on the SQL side as to why the build index phase timesout for large period spans it would be nuch appreciated.
Thanks,
-Todd C.

________________________________
From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of Todd Caughey
Sent: Monday, November 12, 2007 8:26 AM
To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] [6.1] FRx Export SQL Timeout

To their credit Epicor's support staff has been very diligent on the following issue and I am waiting to set up a WebEx session for them to take a look at our systems...but time is running short on my boss's patience so I will see if anyone here, particularly SQL Server experts, has any suggestions.

When exporting large date ranges from Vantage (6.1) the export process produces the following error at the 99% level (after running 3 hrs) in the building indexes phase....
--------------------------------------
Error occurred while accessing component property/method: Execute
[Microsoft][ODBC SQL Server Driver]Timeout Expired
Error code: 0x80020009 SQL_Table_Build GL/GLFRx10-mn.w (5890)
--------------------------------------
I have ruled out Vantage inactivity timeout and at support's suggestion set the ODBC settings for SQL Server pool connectivity timeout from 60 seconds to 14,400 seconds with no positive result. I have been thinking there my be something on the SQL Server database side but don't know enough about SQL Server to know where to start or if there are even timeout settings on the server. Shorter date ranges (2 years instead of 4) work fine. Another thought is if there is an inherent limit in the SQL DB schema that gets recreated with every export that can't handle a certain number of years. Has anyone out there that uses FRx been able to export four or more years of data?

Thanks,
Todd Caughey
Harvey Vogel Mfg. Co,

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]