This is a migrated thread and some comments may be shown as answers.
Problem with installing examples
3 Answers 482 Views
This is a migrated thread and some comments may be shown as answers.
Bosko Maksimovic
Top achievements
Rank 1
Bosko Maksimovic asked on 04 Nov 2006, 09:09 PM
When installing the Reporting tools I receive an error message saying "Unable to detect a running instance of SQL Server 2005".  I have SQL Server 2005 (full version - not express) installed and running on my computer.  Is there anything that I am missing when doing the install or does the CTP only work with SQL Server 2005 Express?

Thank you!

3 Answers, 1 is accepted

Sort by
0
Svetoslav
Telerik team
answered on 06 Nov 2006, 03:12 PM
Hello Bosko,

First of all I want to thank you for your interest to our new product and for the fast and useful feedback.

In order to setup working examples of the telerik Reporting on a client machine we need any version of SQL Server 2005 - not exactly the Express Edition. During the installation process we're looking trough every installed instance of SQL Server 2005 and try to connect to it using the current Windows account credentials. Then we use the 1st successful connection to deploy the sample database.

As you can see, in addition to the possible problems in the installation itself, there are several reasons of the setup of the sample database to fail. We need some time to investigate and eliminate all the possible problems with sample database deployment for the upcoming releases.

Anyway, the easiest (but not the most correct) way to work round this issue now is to install the SQL Server Express Edition. You can download it from Microsoft Web site.

The other way is to manually install and configure the sample database. All the telerik Reporting examples use connection strings against the default SQL Server Express Edition instance name - (local)\sqlexpress. If you use different SQL Server instance you should modify all the connection strings to let the examples work correctly.

Prerequisites:

You must have a SQL Server instance installed for which you have permissions. If you installed SQL Server 2005 Express, the default instance name is (local)\sqlexpress. All the scripts below are will be executed against this instance. If the target SQL Server instance has different name you should replace sqlexpress with the name of your instance: (local)\[SqlServerInstanceName]. For the default SQL Server instance you should use only (local).

To download AdventureWorksDB.msi:

  1. Navigate to this download Microsoft Web site. Double-click AdventureWorksDB.msi.
  2. Click Run and complete the installation wizard. AdventureWorks_Data.mdf and AdventureWorks_Log.ldf are copied to your SQL Server data directory. For SQL Server 2005 Express, the default is c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\.

To attach AdventureWorksT to your SQL Server:
The telerik Reporting examples are configured to use database named AdventureWorksT.

  1. Open a Visual Studio 2005 command window. From the Start menu, click All Programs, Microsoft Visual Studio 2005, Visual Studio Tools, Visual Studio 2005 Command Prompt.
  2. Open a connection to a local SQL Server Express instance by typing or copying the following command into the command line:

    SQLCMD -S (local)\sqlexpress -E

     
  3. Press Enter.
  4. At the SQLCMD 1> prompt, call the sp_attach_db stored procedure to attach the AdventureWorksT database in the data directory determined in the previous step. The line below uses the default location for SQL Server 2005 Express. Edit the text as necessary to use the data directory confirmed in the previous steps. Type or copy and paste the following statement into the command window (the statement must not have line breaks).

    exec sp_attach_db @dbname=N'AdventureWorksT', @filename1=N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\AdventureWorks_Data.mdf', @filename2=N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\AdventureWorks_log.ldf'
     
  5. Type go.
  6. Press ENTER. You may see a series of messages about converting and upgrading the database.
  7. Type exit to close the command window.

To verify AdventureWorksT is attached:

  1. Open Visual Studio 2005. You do not need to open a project.
  2. From the View menu, choose Server Explorer.
  3. In the Server Explorer window, right-click on Data Connections and choose Add Connection. The Add Connection dialog box opens.
  4. Confirm Data source is set to Microsoft SQL Server (SqlClient).
  5. In the Server name textbox, enter (local)\sqlexpress.
  6. In Log on to the server, choose your method of authentication.
  7. In Select or enter a database name, expand the list of databases.
  8. Select AdventureWorksT.
  9. Click the Test Connection button to confirm that you have connected to AdventureWorksT successfully.

To configure AdventureWorksT to work with Web server controls:

  1. Open a Visual Studio 2005 command window to run SQLCMD. You will use SQLCMD to grant access to the database and ASP.NET account.
    On Windows Server 2003, the ASP.NET process used by the Web server control runs under NT AUTHORITY\NETWORK SERVICE. On other Windows operating systems, the process runs under MACHINENAME\ASPNET.
    If you installed SQL Server Express 2005, type or copy the following SQLCMD below to grant login authority to the service. Otherwise, you must specify the SQL Server instance you want to use in place of (local)\sqlexpress.
    The following example works for Windows Server 2003 and must have no line breaks.
    sqlcmd -E -S (local)\sqlexpress -Q "sp_grantlogin N'NT AUTHORITY\NETWORK SERVICE'"
     
  2. To grant access to AdventureWorksT for this service, use the following command with no line breaks.
    sqlcmd -E -S (local)\sqlexpress -d AdventureWorksT -Q "sp_grantdbaccess N'NT AUTHORITY\NETWORK SERVICE'"
     
  3. To add this service to the owner role account for AdventureWorksT, use the following command with no line breaks.
    sqlcmd -E -S (local)\sqlexpress -d AdventureWorksT -Q "sp_addrolemember 'db_owner', N'NT AUTHORITY\NETWORK SERVICE'"
     
  4. Close the command window.

At the moment of writing this response we've already discovered a problem with installing the sample database to the default SQL Server instance and we will fix it in the upcoming days.


Best wishes,

Svetoslav

the telerik team

0
edgebyte
Top achievements
Rank 1
answered on 27 Nov 2006, 11:38 AM
Looking forward to that fix..
0
Vassil Petev
Telerik team
answered on 27 Nov 2006, 01:50 PM
Hi guys,

Expect the second CTP version of the reporting tool within couple of weeks - the fix mentioned will appear in the second CTP.


Kind regards,
Rob
the telerik team
Asked by
Bosko Maksimovic
Top achievements
Rank 1
Answers by
Svetoslav
Telerik team
edgebyte
Top achievements
Rank 1
Vassil Petev
Telerik team
Share this question
or