To schedule a database backup operation by using SQL Server Management Studio in SQL Server 2005, follow these steps:
1. Start SQL Server Management Studio.
2. In the Connect to Server dialog box, click the appropriate values in the Server type list, in the Server name list, and in the Authentication list.
3. Click Connect.
4. In Object Explorer, expand Databases.
5. Right-click the database that you want to back up, click Tasks, and then click Back Up.
6. In the Back Up Database - DatabaseName dialog box, type the name of the backup set in the Name box, and then click Add under Destination.
7. In the Select Backup Destination dialog box, type a path and a file name in the Destinations on disk box, and then click OK.
8. In the Script list, click Script Action to Job.
9. In the New Job dialog box, click Steps under Select a page, and then click Edit if you want to change the job parameters.
*Note In the Job Step Properties - 1 dialog box, you can see the backup command.
10. Under Select a page, click Schedules, and then click New.
11. In the New Job Schedule dialog box, type the job name in the Name box, specify the job schedule, and then click OK.
* Note If you want to configure alerts or notifications, you can click Alerts or Notifications under Select a page.
12. Click OK two times.
You receive the following message:
The backup of database 'DatabaseName' completed successfully.
* Note To verify the backup job, expand SQL Server Agent, and then expand Jobs. When you do this, the SQL Server Agent service must be running.
Problems faced and their Solution listed are for apply in Post Offices on day to day operation.
Thursday, March 18, 2010
Tuesday, March 9, 2010
Network Printing
Printing Through USB Port
Share the Printer name( in the Printer attached System)
Go to Command Prompt
Create a Batch file like this thro edit command ( Eg. NETPRINT.BAT)
@ECHO ON
NET USE LPT1: \\SYSTEMNAME\SHARENAME /PERSISTENT:YES
CLS
Add the Batch file into Windows startup menu in the required client system
Install the Attached DOS2USB Software ( Download DOS2USB)
Network Print Setup
Share the Printer name( in the Printer attached System)
In Other Clients:
Go to Command Prompt
Create a Batch file like this thro edit command ( Eg. NETPRINT.BAT)
@ECHO ON
NET USE LPT1: \\SYSTEMNAME\SHARENAME /PERSISTENT:YES
CLS
Add the Batch file into Windows startup menu in the required client system
Share the Printer name( in the Printer attached System)
Go to Command Prompt
Create a Batch file like this thro edit command ( Eg. NETPRINT.BAT)
@ECHO ON
NET USE LPT1: \\SYSTEMNAME\SHARENAME /PERSISTENT:YES
CLS
Add the Batch file into Windows startup menu in the required client system
Install the Attached DOS2USB Software ( Download DOS2USB)
Network Print Setup
Share the Printer name( in the Printer attached System)
In Other Clients:
Go to Command Prompt
Create a Batch file like this thro edit command ( Eg. NETPRINT.BAT)
@ECHO ON
NET USE LPT1: \\SYSTEMNAME\SHARENAME /PERSISTENT:YES
CLS
Add the Batch file into Windows startup menu in the required client system
Monday, March 8, 2010
SB Data Transfer
SB Table Transfer.
OCX Files : http://www.box.net/shared/6d1469dtab
Download and rename as SB Table Transfer.exe. and execute from any where
Restore the Source database ( may be EDSO or any SO database for Computerisation)
1. It a self executing software for transfer of Tables between two Sanchaypost – SB databases.
2. It is used to transfer the tables from EDSO / GDS SO to Merged SO
3. It is useful to New SO Computerisation ( for SB)
4. It used to Update PO Code for the particular tables
*Check any Duplicate Account No in relevant the SQL table manually and delete
The Required DLL/ OCX files are attached h/w
SB Transfer Download
OCX Files : http://www.box.net/shared/6d1469dtab
Download and rename as SB Table Transfer.exe. and execute from any where
Restore the Source database ( may be EDSO or any SO database for Computerisation)
1. It a self executing software for transfer of Tables between two Sanchaypost – SB databases.
2. It is used to transfer the tables from EDSO / GDS SO to Merged SO
3. It is useful to New SO Computerisation ( for SB)
4. It used to Update PO Code for the particular tables
*Check any Duplicate Account No in relevant the SQL table manually and delete
The Required DLL/ OCX files are attached h/w
SB Transfer Download
Thursday, March 4, 2010
ePayment Reset Registraton
Re-register the office both from web and client.
For resetting the existing registration please do the following.
1. Download the resetregistrtation.zip file from http://www.sendspace.com/file/0dp1l5
2. Unzip the zip file to get ResetRegistration and Readme.txt files
Go through the Readme.txt file and execute the exe as per instructions
For resetting the existing registration please do the following.
1. Download the resetregistrtation.zip file from http://www.sendspace.com/file/0dp1l5
2. Unzip the zip file to get ResetRegistration and Readme.txt files
Go through the Readme.txt file and execute the exe as per instructions
When Speedpost Booked, Despatch, Delivery articles are shown as NA then
Despatch Module:
1- Download the Despatch latest 270110.zip file from http://www.sendspace.com/file/jr0rjr
and unzip it. Rename the it to DESPATCH.EXE
2- Replace the existing exe with new
3- Update counter database with exl files using Scripttool in following sequence
1 counter16122009.exl
2 Counter21012010.exl
3 and last Counter22012010.exl
Postman Module :
Download the zipped folder postman21122009.zip from http://www.sendspace.com/file/xc6hs0.
Unzip and follow the guidelines in the readme file therein.
Pls do shift end using the new postman exe after completing all the work.
Pls provide your feedback whether your problem is solved or not
Day End Sequence:
You have to strictly follow the shiftend sequence where POS shiftend should be at last. i.e.
The sequence of shift end is
Despatch, Postman, Speednet, Point of sale
For doing day end in postman, there are no conditions, except that
i) returns of all the speed post articles invoiced to postman should have been taken and
ii) if any speed post articles are to be despatched (returns taken as returned to sender/redirected) then such articles should be included in the concerned despatch bag
There is no any other conditions for other modules.
BNPL articles:
Regarding BNPL articles, ensure that the data entry of BNPL articles is done before doing day end of Point of Sale. Also ensure flush data is done in Speednet.
DET figures are available for some days and not available for some other days. This may be probably due to operational problems on those days. Please check.
1- Download the Despatch latest 270110.zip file from http://www.sendspace.com/file/jr0rjr
and unzip it. Rename the it to DESPATCH.EXE
2- Replace the existing exe with new
3- Update counter database with exl files using Scripttool in following sequence
1 counter16122009.exl
2 Counter21012010.exl
3 and last Counter22012010.exl
Postman Module :
Download the zipped folder postman21122009.zip from http://www.sendspace.com/file/xc6hs0.
Unzip and follow the guidelines in the readme file therein.
Pls do shift end using the new postman exe after completing all the work.
Pls provide your feedback whether your problem is solved or not
Day End Sequence:
You have to strictly follow the shiftend sequence where POS shiftend should be at last. i.e.
The sequence of shift end is
Despatch, Postman, Speednet, Point of sale
For doing day end in postman, there are no conditions, except that
i) returns of all the speed post articles invoiced to postman should have been taken and
ii) if any speed post articles are to be despatched (returns taken as returned to sender/redirected) then such articles should be included in the concerned despatch bag
There is no any other conditions for other modules.
BNPL articles:
Regarding BNPL articles, ensure that the data entry of BNPL articles is done before doing day end of Point of Sale. Also ensure flush data is done in Speednet.
DET figures are available for some days and not available for some other days. This may be probably due to operational problems on those days. Please check.
Tuesday, March 2, 2010
Simple Upgradation Procedure from Sanchaypost version 6.5 into R2 ( 15/02/2010)
Upgradation Procedure from Sanchaypost version 6.5 into R2 ( 15/02/2010) ( Download the latest from the following links) 1.Execute the SP5.exe in all Client Machine where SanchayPost software installed 2.Execute the Server Only.exe in Server or any one Client Machine 3.A. Use ‘DBAnalyzer >> SQL Compatibility Level’ option. B. Use ‘DBAnalyzer >> DBUtilities >> Clear log file’ for all SB databases. C. Use ‘DBAnalyzer >> Missing Tables' for all SB databases and ensure that no tables are missing. D. Use DBAnalyzer >> ‘Database Discrepancies >> SCS >> Account numbers with SI without previous quarter interest withdrawal’. 4. Perform Day End in Version 6.5 A.After day end, Go to DBAnalyzer folder in SBServer and execute Patch65R2.EXE from the same location. Wait till the message 'Upgraded successfully' is displayed. B. Check for upgradation status using 'DBAnalyzer >> Version 6.5R2' to ensure that the upgradation is successful. | |
SanchayPost 6.5 R2 Updates for All Clients (15/02/2010) | |
SanchayPost 6.5 R2 Updates for Server Only (15/02/2010) |
Subscribe to:
Posts (Atom)