On rare occasions, SQL Server marks the WaspConfig database as SUSPECT, or some other problem occurs with WaspConfig, and MobileAsset cannot be opened. This procedure allows you to rebuild the WaspConfig database, including any additional databases that have been created.
- In SQL Server Management Studio, detach the WaspConfig and WaspTrackAsset databases.
- Rename the data files. Suggestion: Add the word original to the end of the filenames.
- Run Database Manager. It should prompt to install WaspConfig and WaspTrackAsset, click Yes.
- The database installer runs. During this process, it creates WaspConfig and WaspTrackAsset, and rebuilds the WaspConfig file to contain the list of databases you had previously.
- The Company names of the databases are not recovered, so on the Existing Databases tab, select each database in turn, click the Update Company button, and give it a descriptive name.
- In SQL Server Management Studio, detach WaspTrackAsset.
- Move or delete the freshly-installed data files WaspTrackAsset.MDF and WaspTrackAsset_log.LDF.
- Rename the original WaspTrackAsset datafiles from Step 2 back to their original names.
- In SQL Server Management Studio, attach WaspTrackAsset.