Accounts Update 28/07/2010 For Increment & Pay Drawl Problems
Download
Problems faced and their Solution listed are for apply in Post Offices on day to day operation.
Thursday, July 29, 2010
Thursday, June 17, 2010
While doing submit accounts ‘Server not configured for RPC’
Solution: Run the following query using query analyzer (replace ‘myserver’ with your server name):
exec sp_serveroption @server='myserver', @optname='rpc', @optvalue='true'
go
exec sp_serveroption @server='myserver', @optname='rpc out', @optvalue='true'
go
Note: The above error is related to SQL Server configuration settings and not related to the application. (RPC is Remote Procedure Call).
exec sp_serveroption @server='myserver', @optname='rpc', @optvalue='true'
go
exec sp_serveroption @server='myserver', @optname='rpc out', @optvalue='true'
go
Note: The above error is related to SQL Server configuration settings and not related to the application. (RPC is Remote Procedure Call).
Friday, May 28, 2010
Daily Accounts Head Problem
execute the attached script using script tool.
if the accountheads are required for the current date execute the following:
use treasury
go
update_megh66_accountheads
if the accountheads are required for a particular date:
use treasury
go
update_megh66_accountheads_ bydate 'ddmmyy'
in this ddmmyy explanation is as follows:
if the date is 16/04/2010 then it will be equal dd/mm/yyyy so the ddmmyy will be 160410. This can be applied to any date on the same analogy.Download
if the accountheads are required for the current date execute the following:
use treasury
go
update_megh66_accountheads
if the accountheads are required for a particular date:
use treasury
go
update_megh66_accountheads_
in this ddmmyy explanation is as follows:
if the date is 16/04/2010 then it will be equal dd/mm/yyyy so the ddmmyy will be 160410. This can be applied to any date on the same analogy.Download
Saturday, May 15, 2010
Point of Sale Submit Account Problem after SP1
The Error in POS Submit Account-
Run time error '3704' operation is not allowed when the object is closed
Run time error '440' Automation error OK
counter13042010.exl
Run time error '3704' operation is not allowed when the object is closed
Run time error '440' Automation error OK
counter13042010.exl
Tuesday, May 4, 2010
Invalid Column Name pliotl in SOSummaryb030510 - Temporary Solution
Change the Column name / Date and Run this Query
USE BOSUBACCOUNTS
ALTER TABLE Sosummaryb030510 ADD pliotl Numeric(15,2) NULL
UPDATE Sosummaryb030510
set pliotl =0
USE BOSUBACCOUNTS
ALTER TABLE Sosummaryb030510 ADD pliotl Numeric(15,2) NULL
UPDATE Sosummaryb030510
set pliotl =0
Saturday, May 1, 2010
Sub Accounts Missing Head Problem
1. Please Download this attached file and run with script tool executor ..
2. after this .. pl. execute the query mentioned below in SQL Query Analyzer ...
execute treasury..update_megh66_ accountheads_bydate '010510'
Pl. also check ..
the option 'Convert Temporary Fields' under tools menu through supervisory login ..
If the missing heads are listed, then make them permanent ...
During the course you may need to perform undo day's work .. perform day end and day begin once again
2. after this .. pl. execute the query mentioned below in SQL Query Analyzer ...
execute treasury..update_megh66_
Pl. also check ..
the option 'Convert Temporary Fields' under tools menu through supervisory login ..
If the missing heads are listed, then make them permanent ...
During the course you may need to perform undo day's work .. perform day end and day begin once again
Subscribe to:
Posts (Atom)