Database service not found
Summary
The instance of SQL Server for Solatech was not found on this computer.
When the Solatech Window Covering Software is installed it installs an instance of Microsoft SQL Server Express 2005. This instance of SQL Server is what is used to manage the company databases. If the database server is not installed then no company databases can be created or used.
To install the Solatech instance of SQL Server Express, run the setup program for your Solatech Window Covering Software.
Note: Under some circumstances an installation of a Solatech instance of SQL Server can be skipped if you are using an existing SQL server. In this case you can ignore this error.
APPLIES TO
Related Articles
Cannot connect to Solatech database server
Summary The instance of SQL Server for Solatech was found on this computer however a connection to the server could not be made. This problem can also occur if testing multiple connections to the company database fails. More Information This could ...
How to back up SWCS when using an online backup service
Summary This article describes how to perform a backup of your Solatech Window Covering software which can be sent to an online backup service. Note: This article is not specific to any of the online backup services, rather it explains the process, ...
SWCS 4.x can't access a SQL Server 2005 database
Symptoms When you attempt to open a company file located on a server using SQL Server 2005 you receive the following error message: The company '...' is not a valid company or you don't have permission to access it. Check with your system ...
How to access the SWCS 4.2 company database using SQL Server Management Studio
This document assumes you are familiar with SQL Server and it's tools and have SQL Server Management Studio installed on your computer. In order to access the SWCS 4.2 company database you'll need to gather some information from SWCS such as the ...
Error 9003 when attaching a database
Problem When attempting to attach a company database to SQL Server using SQL Server Management Studio you receive error 9003 with a message similar to this: The log scan number %S_LSN passed to log scan in database '%.*ls' is not valid. This error ...