Temp FileNum Sequence [E9.05.607b, SQL, x64]

Yahoo Archive
1
E9 Support confirmed that the current_value field can be reset to 1 using SQL. Doing so has corrected the issue.

Now to find out how the value went to NULL in the first place.


--- In vantage@yahoogroups.com, "robertbeaghan" <robert.beaghan@...> wrote:
>
> We started receiving various printing errors yesterday. It appears that the XML report data files all have a sequence of 00000, e.g. "Packing Slip Print00000.xml".
>
> In the database, field _SEQT_tempfilenum.current_value is showing as NULL. After some tests in our test environment, I'm pretty sure that the current_value didn't cycle back to zero properly.
>
> Has anyone else encountered this issue? Is it safe to update this field back to 0 directly with SQL? Or is there a conversion program to run that will correct the issue?
>
> Thanks,
> Bob Beaghan
>
2
We started receiving various printing errors yesterday. It appears that the XML report data files all have a sequence of 00000, e.g. "Packing Slip Print00000.xml".

In the database, field _SEQT_tempfilenum.current_value is showing as NULL. After some tests in our test environment, I'm pretty sure that the current_value didn't cycle back to zero properly.

Has anyone else encountered this issue? Is it safe to update this field back to 0 directly with SQL? Or is there a conversion program to run that will correct the issue?

Thanks,
Bob Beaghan
3
Have you tried to restart process, task and report servers (if you have one) first to see if this will fix the issue?

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of robertbeaghan
Sent: Wednesday, July 31, 2013 11:17 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Temp FileNum Sequence [E9.05.607b, SQL, x64]



We started receiving various printing errors yesterday. It appears that the XML report data files all have a sequence of 00000, e.g. "Packing Slip Print00000.xml".

In the database, field _SEQT_tempfilenum.current_value is showing as NULL. After some tests in our test environment, I'm pretty sure that the current_value didn't cycle back to zero properly.

Has anyone else encountered this issue? Is it safe to update this field back to 0 directly with SQL? Or is there a conversion program to run that will correct the issue?

Thanks,
Bob Beaghan



[Non-text portions of this message have been removed]
4
Yes, we did try that. It didn't help.


--- In vantage@yahoogroups.com, Karen Schoenung <kschoenung@...> wrote:
>
> Have you tried to restart process, task and report servers (if you have one) first to see if this will fix the issue?
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of robertbeaghan
> Sent: Wednesday, July 31, 2013 11:17 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Temp FileNum Sequence [E9.05.607b, SQL, x64]
>
>
>
> We started receiving various printing errors yesterday. It appears that the XML report data files all have a sequence of 00000, e.g. "Packing Slip Print00000.xml".
>
> In the database, field _SEQT_tempfilenum.current_value is showing as NULL. After some tests in our test environment, I'm pretty sure that the current_value didn't cycle back to zero properly.
>
> Has anyone else encountered this issue? Is it safe to update this field back to 0 directly with SQL? Or is there a conversion program to run that will correct the issue?
>
> Thanks,
> Bob Beaghan
>
>
>
> [Non-text portions of this message have been removed]
>