By using this web site, you agree to all terms and conditions for acceptable use.

ServiceLedger KnowledgeBase Knowledgebase Home Page > ServiceLedger > Technical | Contact Us

Search the Knowledge Base Browse by Category

ServiceLedger provides this content as-is for self help support purposes. ServiceLedger assumes no liability for any steps you take based on the directions in our knowledge base, and assumes that you have the knowledge to determine whether a given step is appropriate for your situation. Certain solutions can affect third-party software that ServiceLedger relies on or integrates with; it is your responsibility to consult with the documentation or publishers of such third-party software to understand whether any changes suggested here will have negative effects on other applications.


(T0150) Installing or restoring a ServiceLedger database on your own copy of SQL Server, MSDE, or SQL Server Express

Would you like to...

Print this page
Email this to a friend

Installation

If you are not using the built-in database engine included with the ServiceLedger Installer, you will need to restore a database to a fully licensed MS SQL Server (or an Express edition). If you are using MS SQL Server 2005, 2008, 2008 R2, or 2012, you must restore the database through the MS SQL Server Management Studio.

There are two broad steps to this process:

  1. Restore a ServiceLedger database to your SQL Server
  2. Use the ServiceLedger installer to do a WORKSTATION install on your server.

To restore the database:

  1. If you're installing from scratch, contact ServiceLedger support to obtain the correct empty database backup for your version of ServiceLedger. If you're moving from an existing server, get a copy of the latest ServiceLedger backup (see KB Article T0003) from your old server.
  2. Open SQL Server Management Studio and log into the SQL Server instance-- Important: You can freely obtain and download MS SQL Server Management Studio from Microsoft's website
  3. Right click the Databases node under the chosen server and select Restore Database
  4. In the To database field enter in ServiceLedger (use the same capitalization)
  5. Select the From device: option, then click the [...] box
  6. Ensure the Backup media: field is set to File
  7. Click Add
  8. Navigate to the local disk (it must be a local fixed disk, not removable media or a network share) and locate your downloaded .BAK file (or your previous backup, if the installation is not new), then click OK
  9. Click OK on the Specify Backup window
  10. Check the ServiceLedger Database in the Select the backup sets to restore: frame
  11. Click the Options node in the Select a Page view on the left
  12. In the Restore the Database Files as Grid, please alter the paths as necessary for your storage. Alternatively you can simply create the specified folder before proceeding.
  13. Click OK
  14. After a few moments the database will be restored and your ServiceLedger database will be visible under the Databases node on the left
  15. Note: You may need to grant access to the new ServiceLedger database to your SQL Server or NT Users. ServiceLedger requires public and db_owner access on the ServiceLedger database.

Additional Configuration:

In addition to restoring the ServiceLedger database, you will need to perform additional server configuration to make sure that the database is accessible to workstations.

  1. Enable xp_cmdshell; see the following KB Article for instructions: (T0151) ServiceLedger won't launch and shows the error message: "SQL Server blocked access to procedure 'sys.xp_cmdshell'..."
  2. Enable the TCP/IP protocol using the SQL Server Configuration Manager (Look for "SQL Server Network Configuration")
  3. Ensure the SQL Server Browser Service is enabled, running, and set to start automatically by going to Control Panel > Administrative Tools > Services or by typing services.msc from a command line. If you have previously run other installations of SQL Server, the SQL Server Browser service may be disabled.
  4. The following Firewall Exceptions must be created:
    • Port opening: UDP port 1434 (the port through which workstations communicate with the SQL Browser service)
    • Program exception for sqlservr.exe: You will need to locate the copy of sqlservr.exe that corresponds with your database. You can find this by right-clicking on your ServiceLedger database in SQL Management Studio, selecting Properties, then selecting the Files page from the pane on the left: The directory referenced under Path will help you find where sqlservr.exe is located. If the path listed for the database files is:

      C:\Program Files\Microsoft SQL Server\MSSQL10_50.SERVICELEDGER\MSSQL\DATA,

      then sqlservr.exe will be located one directory higher in the \BINN folder. The location of sqlservr.exe, then, in this example will be:

      C:\Program Files\Microsoft SQL Server\MSSQL10_50.SERVICELEDGER\MSSQL\BINN.

Completing Workstation Installs:

See the following KB article for information on completing the WORKSTATION installations:


Related Questions:

Attachments:

No attachments were found.


ServiceLedger KnowledgeBase Copyright © 2019 support.serviceledger.com
Powered by AcitveKB Knowledgebase Software