You’re offline. This is a read only version of the page.
Hello,
A customer is experiencing a problem with remote users who print checks. I hope someone can point us toward a solution. The version is 7.0 FP1.
There is a home office that has no problems with checks, a New York office that has a problem about once per month, and a Chicago office that has a problem once or twice per week. When "the problem" occurs, the remote user prints checks, and the checks print fine. The AP Check Update screen never opens. There is no error. Sometimes the screen is frozen. Sometimes they have to disconnect in order to do anything more in SL. Approximately 4 out of 5 checks batches process fine in Chicago, which rules out access rights. It is the same person printing checks from the same remote workstation each time.
When the problem happens, the AP checks batch ends up with a V status, and temporary check records are left behind in the database.
The NY and Chicago offices connect to the server via a VPN and remote desktop connection. They have connected this way for a few years, and the problem started happening about 6 months ago, with increasing frequency. In each case, there is no error, and AP Check Update just doesn't open.
We don't think it's bandwidth - has happened during times of very low activity. They are all using the same set of databases.
What can we do to solve this?
Thanks!
Laura Barber
*This post is locked for comments
I have the same question (0)
Hi Laura,
I found bug 20512 which may relate to this issue. Does this client use OM? Blocking on APdoc and Rptruntime can occur if another user is previewing OM invoices at the same time. We worked around it by running the following modification to the stored procedure:
alter Procedure roi1 @rptidb smallint , @rptide smallint As
Select * from rptruntime with (nolock) --added 9588235
Where rptruntime.RI_ID Between @rptidb and @rptide
Order by RI_ID
go
/****** Object: Stored Procedure dbo.TempCheckDocAllBat Script Date: 4/7/98 12:19:55 PM ******/
alter Procedure TempCheckDocAllBat As
Select * From APDoc with (nolock) --added 9588235
Where BatNbr = '' and
RefNbr = '' and
DocType = 'CK' and
Status = 'T'
Order By APDoc.VendId, APDoc.InvcNbr
go
/****** Object: Stored Procedure dbo.APDoc_Acct_Sub_RefNbr Script Date: 4/7/98 12:19:54 PM ******/
alter Procedure APDoc_Acct_Sub_RefNbr
@parm1 varchar ( 10), @parm2 varchar ( 24), @parm3 varchar ( 10) as
Select * from APDoc with (nolock) --added 9588235
where Acct = @parm1
and Sub = @parm2
and RefNbr = @parm3
and Doctype in ('CK' ,'HC', 'MC', 'QC', 'SC', 'VC' , 'ZC' )
Order by Acct, Sub, DocType, RefNbr
go
/****** Object: Stored Procedure dbo.APCheck_Prtd_to_Keep Script Date: 4/7/98 12:19:54 PM ******/
alter Procedure APCheck_Prtd_to_Keep @parm1 varchar ( 10), @parm2 varchar ( 10) As
Select Acct, Sub, RefNbr, DocType, CuryOrigDocAmt, Vendid, BatNbr
From APDoc with (nolock) --added 9588235
where BatNbr = @parm1 and RefNbr Like @parm2
order by Acct, Sub, DocType, RefNbr
Let me know if you think this may have something to do with the issue.
Share
Report
All responses (
Answers (
