[BCB:3:Network warning:ECB]

1. At the file server, verify dictionary files for Service Management data.  NOTE: Skip this step if you think there's no issue with the DDF files, and go to Step 2. 
   1. Have all operators exit all applications and tasks that use Service Management data.
   2. Make a backup of all Service Management *.ddf files in your SMData folder (located in your data folder).
   3. Use Windows Explorer to browse to your Servmngt folder. For example, X:\Timberline Office\Accounting\Servmngt, where X is the network drive.
   4. Note the Date Modified on the Field.ddf, File.ddf, and Index.ddf files.
   5. Use Windows Explorer to browse to the SMData folder.
   6. Note the Date Modified on the Field.ddf, File.ddf, and Index.ddf files. No further action is necessary if the Date Modified matches the files in Step 1.d and Step 1.f. If the Date Modified doesn’t match the files in Step 1.d and Step 1.f, continue with the next step.
   7. In the SMData folder, use Windows Explorer to rename the Field.ddf, File.ddf, and Index.ddf files.
   8. Use Windows Explorer to browse to your Servmngt folder. For example, X:\Timberline Office\Accounting\Servmngt, where X is the network drive.
   9. Copy the Field.ddf, File.ddf, and Index.ddf files to the SMData data folder.
   10. If a message appears to ask if you want to replace an existing file, click No. Repeat Steps 1.g–1.i. 

    

    

2. Set up the Pervasive ODBC Engine Interface DSN at the file server.
   1. Log on to the file server as the local administrator.
   2. Note down the server's IP address.
   3. Click Start and select Programs, Administrative Tools, Data Sources (ODBC).
   4. Click the System DSN tab and then click Add.
   5. Select Pervasive ODBC Engine Interface and then click Finish.
   6. Type a Data Source Name name.
       NOTE: The Data Source Name can't contain special characters and the first character can’t be a number. 
   7. Click Create.
   8. Enter the Data Source Name you created in Step 2.f in the Database Name box.
   9. Click Browse and then find and select your SMData folder.
       NOTE: You can't use a mapped network drive. You need to use a local drive path to the SMData folder. 
   10. Click OK twice and then click Test.
   11. A message, Connection successful appears. Click OK three times.

    

    

3. If you have terminal servers connecting to other Sage Timberline Office data servers, set up the Pervasive ODBC Client Interface DSN.
   1. Click [Start] and select Programs, Administrative Tools, Data Sources (ODBC).
   2. Click the System DSN tab and then click Add.
   3. Select Pervasive ODBC Client Interface and then click Finish.
   4. Type a Data Source Name name.
   5.  NOTE: The Data Source Name can't contain special characters and the first character can’t be a number.
   6. The Data Source Name can be any name that doesn’t contain special characters unless otherwise specified in a knowledgebase solution or Sage Timberline Office documentation.
      Note: The first character can’t be a number.
   7. In the Server Address box, type the IP Address for the server you logged on to in step 1.
   8. Click Get DSN List and select the DSN created in Step 1.f.
   9. Click Test.
   10. A message, Connection successful appears. Click OK three times.

    

    

4. Set up the Pervasive ODBC Engine Interface DSN on your workstations for Service Management as follows:
   1. Launching SM on the workstation creates the SM data source automatically.
   2. To verify the DSN, go to Start, Programs or All Programs, ODBC, 32Bit ODBC Administrator, User DSN tab and look for the Timberline SM Data.
   3. If Timberline SM Data still doesn’t appear in the ODBC Data Source Administrator window, launch SM on the workstation and then go into Report, Work Orders, Work Orders in Progress to create the Timberline SM Data listing.
   4. To verify the DSN, go to Start, Programs or All Programs, ODBC, 32Bit ODBC Administrator, User DSN tab and look for the Timberline SM Data.

How do I find a server's IP address?