cannot deploy analysis services tutorial db

i am using sql server developer 2005 .... i follow a tutorial example and attempt to deploy a created analysis services project to the analysis server .... but when i attempt to deploy i get the following:

Error 1 The following system error occurred: Key not valid for use in specified state. . 0 0

i have looked a bunch of different places and found references to this error and have tried things like deleting & creating a new data connection but this does not have any effect .... also these references i have found on the web dont look like they matche my particular situation (deploying to the analysis server) ..... does anyone know how I can get around this ? unfortunately i have not been sucessful in executing the most rudimentary task in sql server ...

thanks

Daver, this error message typically appears in scenarios where the SQL Server Analysis Services service account has been changed to Local Service or if there was an inappropriate change in the service startup account. Can you run your AS service as "Local System" or some valid domain user that has permissions to the relational database referenced in your project’s data source? To change the service account, please use the SQL Server Configuration Manager utility that ships with the product.

Hope this helps,

Artur

sql

Cannot create SSIS projects

When i create a new SSIS project, the system alert will popup a window to show 'Constructor on type 'Microsoft.DataTransformationService.wizards.ETLProjectInitializer' not found'

I met this kind of questions more than 3 time.

Reinstall VS2005?

How should i do?

It sounds like something in the system dll's did not get included or was removed.

Probably the best thing would be to reinstall business intelligence which is a part of the SQL Server install

Re Installing Visual Studio would do nothing due to the fact that SSIS is not associated with Visual Studio 2005 other then through Business Intelligence.

cannot create new sql express database

Hi,

I am trying to create a new Sql Express Database (.mdf file) from inside Visual Studio 2005. I did the following:

1) Created a Database Project in Visual Studio.

2) Choose Data Source to be Microsoft SQL Server Database File

3) Browse to a directory and enter a file name for the new database, say abc.mdf

4) When I click OK, Visual Studio prompts me if I want to create the database file, I click yes.

5) After a while, I get this error message:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Then I opened SQL Server Configuration Manager, and I enabled Named Pipes and TCP/IP for both SQLEXPRESS and MSSQLSERVER. It prompts me that the settings will not change until the service is re-started.

When I go to Administrative Tools -> Services, I see that SQLServer (MSSQLSERVER) is started, and SQL Server (SQLEXPRESS) is stopped. I can stop the MSSQLSERVER service. But when I tried to start SQLEXPRESS service, I get the following error message:

Windows could not start the SQL Server (SQLEXPRESS) on Local Computer. For more information, review the System Event Lo9g. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 17058.

I have Visual Stuio 2005 and Sql Server 2005 Installed on my machine, and I believe I am logged on using an administrator account.

Can someone help me to figure out what's wrong please?

Thanks and regards,

Alice

It seems that something is wrong with your SQL Express isntallation if it won't start. You should check the error log to see if it give more details about the problem starting the service. The error log is generally located at C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG (Your InstanceID may be different).

When you check the error log, please also verify that you are not running a beta version of SQL Express. The version number should contain either 9.00.1399 or 9.00.2047.

Mike

|||

Hi,

It turns out SQL Express wasn't installed properly. I re-installed it and it works fine now. Thanks a lot.

Alice

Cannot create a connection to data source 'myservername'.

No matter how many times I redeploy my report and data sources from my
project to Report Manager, I keep getting this error when trying to run
the report from Reprt manager. It runs fine in VS 2005 though. I
don't know what else to do. I see no way to delete the report from
Report Manager in attempts to try to redeploy it from scratch either.
"An error has occurred during report processing.
Cannot create a connection to data source 'myservername'.
For more information about this error navigate to the report server on
the local server machine, or enable remote errors "In report manager on the datasource properties, credentials tab and set the
credentials to be used. Then when deploying do not overwirte the datasource
(this is the default behavior, to not overwrite the source).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"dba123" <d_schinkel@.hotmail.com> wrote in message
news:1141683199.061931.270510@.u72g2000cwu.googlegroups.com...
> No matter how many times I redeploy my report and data sources from my
> project to Report Manager, I keep getting this error when trying to run
> the report from Reprt manager. It runs fine in VS 2005 though. I
> don't know what else to do. I see no way to delete the report from
> Report Manager in attempts to try to redeploy it from scratch either.
>
> "An error has occurred during report processing.
> Cannot create a connection to data source 'myservername'.
> For more information about this error navigate to the report server on
> the local server machine, or enable remote errors "
>

Cannot create a connection to data source 'mydatasourcename'.

No matter how many times I redeploy my report and data sources from my project to Report Manager, I keep getting this error when trying to run the report from Reprt manager. It runs fine in VS 2005 though. I don't know what else to do. I see no way to delete the report from Report Manager in attempts to try to redeploy it from scratch either.

An error has occurred during report processing.

Cannot create a connection to data source 'myservername'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

Report manager has an icon in the toolbar to toggle between list view (default view) and detail view. In the detail view, you can select a report and delete it.

One reason why the connection could fail is that you are using Windows Integrated Security, but Kerberos is not set up for delegation.

-- Robert

|||I'm having the same problem. But how do I fix it without deleting my reports?|||

If your report server and the database used to get report data are not on the same machine,

1. Enable Kerberos protocol so that credentials can be delegated to other computers without limit.

2. If enabling Kerberos is not an option, consider using either stored credentials or a combination of Windows Authentication and database authentication. For example, you can use Windows Authentication to connect a client to a report server, and then configure the report to use database authentication to access an external data source. For this use a specific username and password in the credentials tab of data source designer. The report server will use the specific credential to access the database server.

Another option is to locate the report data sources on the same computer that hosts the report server.

Cannot create a connection to data source 'mydatasourcename'.

No matter how many times I redeploy my report and data sources from my project to Report Manager, I keep getting this error when trying to run the report from Reprt manager. It runs fine in VS 2005 though. I don't know what else to do. I see no way to delete the report from Report Manager in attempts to try to redeploy it from scratch either.

An error has occurred during report processing.

Cannot create a connection to data source 'myservername'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

Report manager has an icon in the toolbar to toggle between list view (default view) and detail view. In the detail view, you can select a report and delete it.

One reason why the connection could fail is that you are using Windows Integrated Security, but Kerberos is not set up for delegation.

-- Robert

|||I'm having the same problem. But how do I fix it without deleting my reports?|||

If your report server and the database used to get report data are not on the same machine,

1. Enable Kerberos protocol so that credentials can be delegated to other computers without limit.

2. If enabling Kerberos is not an option, consider using either stored credentials or a combination of Windows Authentication and database authentication. For example, you can use Windows Authentication to connect a client to a report server, and then configure the report to use database authentication to access an external data source. For this use a specific username and password in the credentials tab of data source designer. The report server will use the specific credential to access the database server.

Another option is to locate the report data sources on the same computer that hosts the report server.

cannot copy sqlexpress to another pc for vb.net 2.0 project update

Hi. I have done alot of searching around but can't find answer to this specific problem.

Here is my connection string in vb.net app config

<connectionStrings>
<add name="myfile.My.MySettings.ffgscrmConnectionString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\myfile.mdf;Integrated Security=True;Connect Timeout=30;User Instance=True"
providerName="System.Data.SqlClient" />
</connectionStrings>

The database is locally attached to the vb.net project residing in a data directory in the project. I am testing installation on a virtual pc - with no sql express managment or other sql server databases attached.

When I do a vb.net setup project and run this on, there is no problem. However, once having done that, when I want to update the app, I can't just copy in the new database along with exe. I get the error:"sql server does not allow remote connections (provider:sql network interfaces error 26 - error locating server/instance specified).

Is this a problem of the virtual PC? I am testing this because I need to be able to send updates to another local machine without using setup program.

Hi,

the destination machine where you copy the files on, does that have SQL Server Express installed ? Otherwise you won′t be able to use the .\SQLEXPRESS instance which points to a local SQLExpress instance on that computer. If there is a SQLExpress instance installed on that machine, make sure you enabled remote connections on this instance. I made a screencast for that, which can be found on my site in the screencast section which will show you how to enabled the remote conenction feature.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Cannot convert between unicode and non-unicode string data type

HI.

I'm having this problem.

I use Visual Studio's, integration project to load XML file into SQL Server. In the XML file, i have defined collumns as string. When i try to load XML file with parts defined in scheme as string, i get an error "cannot convert between unicode and non-unicode string data type.

Destinated collumns in SQL are defined as varchar and char.

Thanks for help

I had the same problem and I put a Data Conversation object to convert the fields from XML to string [ST_STR] and everything works fine.

Hope this helps
Paulo Aboim Pinto
Odivelas - Portugal

|||Thank you. You saved me lot of work today. O have bypassed this problem with querry in SQL Server, but this solution is better. Thanks again.
|||

pkv wrote:

Thank you. You saved me lot of work today. O have bypassed this problem with querry in SQL Server, but this solution is better. Thanks again.

Please mark your post as answered if you've solved your own issue. It helps us to filter out which posts still require attention.|||Post from another topic that might help...
-

Katrina, you are a goddess among men. For anyone out there who still has this problem, Katrina has led me to the solution. I was still a little confused when I read it, so here are the exact steps I took to change it. I was loading from a flat text file. In the edit page of the file connection manager (not flat file source), go to the advanced tabs to see the columns. Here you can set the load type for the columns (I wanted non-unicode, so I chose String). Then you connect to (let's say) an OLE DB Destination. If you double click to open the connection, you can choose "metadata" and see the types are correct. Right click on the OLE DB Destination, and choose "Show Advanced Editor". Then click on the "Input and Output Properties" tab. Expand "OLE DB Destination Input" and you will see two folders ("External Columns" and "Input Columns"). If you open "Input Columns" and choose one of your columns, you will see the correct data type (ie. DT_STR). Now, if you expand the "External Columns" folder and choose one of your columns, you will see that it thinks an incorrect data type is coming in (ie. "Unicode string [DT_WSTR]"). This is what is causing your error. This makes the package think that it needs to implicitly convert what it THINKS is coming in (DT_WSTR) to what it wants (DT_STR), which it refuses to do. In the "External Columns" folder, change all of your data types to the correct incoming types, and all your worries will float away.
To aid in the discussion on many forums about why this is a problem, this is most definitely a Microsoft error. When you connect the source to the destination, the connection should force the destination to update its input types. Again, thanks to Katrina for leading the way!
|||

Tim/Katrina, that all sounds great. But when I change the External Columns to DT_STR, it doesn't save my changes!!!! I'll go right back into my OLE DB Destination, and whamo, it changes it back to DT_WSTR.

Any ideas?

I'm running:

Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727

SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.1399.00

|||

Hi..

Set ValidateExternalMetata option of the Destination False from True, and change types of external columns in Advnaced Editor.

Related Article and sample packages (written by Korean..Sorry!!)

http://www.sqlleader.com/mboard.asp?exec=view&strBoardID=SS2005SSIS&intSeq=807

test user_id and password : test / test

HTH

|||

OH MY GOD THANKS FOR POINTING THIS VALIDATEEXTERNALMETADATA OUT I HAVE SPENT HOURS FIDDLING WITH SETTINGS AND FINALLY IT WORKS!!!!!

But it totally sucks beyond belief that SSIS is so full of gotchas like this.

Cannot convert between unicode and non-unicode string data type

HI.

I'm having this problem.

I use Visual Studio's, integration project to load XML file into SQL Server. In the XML file, i have defined collumns as string. When i try to load XML file with parts defined in scheme as string, i get an error "cannot convert between unicode and non-unicode string data type.

Destinated collumns in SQL are defined as varchar and char.

Thanks for help

I had the same problem and I put a Data Conversation object to convert the fields from XML to string [ST_STR] and everything works fine.

Hope this helps
Paulo Aboim Pinto
Odivelas - Portugal

|||Thank you. You saved me lot of work today. O have bypassed this problem with querry in SQL Server, but this solution is better. Thanks again.|||

pkv wrote:

Thank you. You saved me lot of work today. O have bypassed this problem with querry in SQL Server, but this solution is better. Thanks again.

Please mark your post as answered if you've solved your own issue. It helps us to filter out which posts still require attention.|||Post from another topic that might help...
-

Katrina, you are a goddess among men. For anyone out there who still

has this problem, Katrina has led me to the solution. I was still a

little confused when I read it, so here are the exact steps I took to

change it. I was loading from a flat text file. In the edit page of the

file connection manager (not flat file source), go to the advanced tabs

to see the columns. Here you can set the load type for the columns (I

wanted non-unicode, so I chose String). Then you connect to (let's say)

an OLE DB Destination. If you double click to open the connection, you

can choose "metadata" and see the types are correct. Right click on the

OLE DB Destination, and choose "Show Advanced Editor". Then click on

the "Input and Output Properties" tab. Expand "OLE DB Destination

Input" and you will see two folders ("External Columns" and "Input

Columns"). If you open "Input Columns" and choose one of your columns,

you will see the correct data type (ie. DT_STR). Now, if you expand the

"External Columns" folder and choose one of your columns, you will see

that it thinks an incorrect data type is coming in (ie. "Unicode string

[DT_WSTR]"). This is what is causing your error. This makes the package

think that it needs to implicitly convert what it THINKS is coming in

(DT_WSTR) to what it wants (DT_STR), which it refuses to do. In the

"External Columns" folder, change all of your data types to the correct

incoming types, and all your worries will float away.

To aid in the discussion on many forums about why this is a problem,

this is most definitely a Microsoft error. When you connect the source

to the destination, the connection should force the destination to

update its input types. Again, thanks to Katrina for leading the way!|||

Tim/Katrina, that all sounds great. But when I change the External Columns to DT_STR, it doesn't save my changes!!!! I'll go right back into my OLE DB Destination, and whamo, it changes it back to DT_WSTR.

Any ideas?

I'm running:

Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727

SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.1399.00

|||

Hi..

Set ValidateExternalMetata option of the Destination False from True, and change types of external columns in Advnaced Editor.

Related Article and sample packages (written by Korean..Sorry!!)

http://www.sqlleader.com/mboard.asp?exec=view&strBoardID=SS2005SSIS&intSeq=807

test user_id and password : test / test

HTH

|||

OH MY GOD THANKS FOR POINTING THIS VALIDATEEXTERNALMETADATA OUT I HAVE SPENT HOURS FIDDLING WITH SETTINGS AND FINALLY IT WORKS!!!!!

But it totally sucks beyond belief that SSIS is so full of gotchas like this.

Cannot convert between unicode and non-unicode string data type

HI.

I'm having this problem.

I use Visual Studio's, integration project to load XML file into SQL Server. In the XML file, i have defined collumns as string. When i try to load XML file with parts defined in scheme as string, i get an error "cannot convert between unicode and non-unicode string data type.

Destinated collumns in SQL are defined as varchar and char.

Thanks for help

I had the same problem and I put a Data Conversation object to convert the fields from XML to string [ST_STR] and everything works fine.

Hope this helps
Paulo Aboim Pinto
Odivelas - Portugal

|||Thank you. You saved me lot of work today. O have bypassed this problem with querry in SQL Server, but this solution is better. Thanks again.|||

pkv wrote:

Thank you. You saved me lot of work today. O have bypassed this problem with querry in SQL Server, but this solution is better. Thanks again.

Please mark your post as answered if you've solved your own issue. It helps us to filter out which posts still require attention.|||Post from another topic that might help...
-

Katrina, you are a goddess among men. For anyone out there who still

has this problem, Katrina has led me to the solution. I was still a

little confused when I read it, so here are the exact steps I took to

change it. I was loading from a flat text file. In the edit page of the

file connection manager (not flat file source), go to the advanced tabs

to see the columns. Here you can set the load type for the columns (I

wanted non-unicode, so I chose String). Then you connect to (let's say)

an OLE DB Destination. If you double click to open the connection, you

can choose "metadata" and see the types are correct. Right click on the

OLE DB Destination, and choose "Show Advanced Editor". Then click on

the "Input and Output Properties" tab. Expand "OLE DB Destination

Input" and you will see two folders ("External Columns" and "Input

Columns"). If you open "Input Columns" and choose one of your columns,

you will see the correct data type (ie. DT_STR). Now, if you expand the

"External Columns" folder and choose one of your columns, you will see

that it thinks an incorrect data type is coming in (ie. "Unicode string

[DT_WSTR]"). This is what is causing your error. This makes the package

think that it needs to implicitly convert what it THINKS is coming in

(DT_WSTR) to what it wants (DT_STR), which it refuses to do. In the

"External Columns" folder, change all of your data types to the correct

incoming types, and all your worries will float away.

To aid in the discussion on many forums about why this is a problem,

this is most definitely a Microsoft error. When you connect the source

to the destination, the connection should force the destination to

update its input types. Again, thanks to Katrina for leading the way!|||

Tim/Katrina, that all sounds great. But when I change the External Columns to DT_STR, it doesn't save my changes!!!! I'll go right back into my OLE DB Destination, and whamo, it changes it back to DT_WSTR.

Any ideas?

I'm running:

Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727

SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.1399.00

|||

Hi..

Set ValidateExternalMetata option of the Destination False from True, and change types of external columns in Advnaced Editor.

Related Article and sample packages (written by Korean..Sorry!!)

http://www.sqlleader.com/mboard.asp?exec=view&strBoardID=SS2005SSIS&intSeq=807

test user_id and password : test / test

HTH

|||

OH MY GOD THANKS FOR POINTING THIS VALIDATEEXTERNALMETADATA OUT I HAVE SPENT HOURS FIDDLING WITH SETTINGS AND FINALLY IT WORKS!!!!!

But it totally sucks beyond belief that SSIS is so full of gotchas like this.

Cannot connect to the SQL 2005 Express

I created test project and want to use SQL 2005 database inside.

1. I created Test database with DEFAULT rights

2. I go into server explorer, press Add Connection. Shows message box for connecting to the server: <PCNAME> using windows authntification.

But NO database allowed to view :(.

Which setting should be set for SQL server database to i could connect and work with it?

P.S I use LOCAL connection. The Application and Server should be on the same PC.|||

sqlexpress is a named instance with instance name as "sqlexpress". For local connection, your connection string can be ".\sqlexpress", "(local)\sqlexpress", "<machinename>\sqlexpress", and e.t.c..

some other useful info: http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx

|||

I do not use connection string - I use Visual Studio User Interface for connecting. I could try to connect as blind but I want to get list of the databases and connect on click.

Could you please give me advice how I could to do that?

|||In Visual Studio, click Connect to Database in Server Explorer. Under Choose Data Source, select Microsoft SQL Server. Under Data Provider drop-down list, select .NET Framework Data Provider for SQL Server and click Continue. On the Add Connection window, in the Server Name drop-down list, either you type .\SQLEXPRESS or select it in your list. Select the database in the drop-down list and click Test Connection. Once you're done, you now have this connection in your SQL Server 2005 Express database from Visual Studio 2005|||

bass_player wrote:

On the Add Connection window, in the Server Name drop-down list, either you type .\SQLEXPRESS or select it in your list. Select the database in the drop-down list and click Test Connection.

I CANNOT SEE ANY databases, so I CANNOT SELECT invisible (for me) database and because I ask - WHICH RIGHTS I should to set in MS SQL Express to Databases could be visible.

Server list - exist (one server: <PCNAME>)

Databases list is EMPTY!!!!!!

|||

The list is for server, a server can host multiple databases. In order to see your local server in the drop down list, you need to have your SQL Browser running. Did you try to type ".\sqlexpress"?

|||

Aaaaaaa!!!....

I've understood. You all were right. .\sqlexpress is required - and all works.

Thanx bass_player and Xinwei Hong - MSFT

Cannot connect to SQLServer2000

Hello everyone,

My project (asp.net and sqlserver2000) is working fine in my intranet. But sometime, it cannot connect to sqlserver, it shows "SQLServer does not exists or access denied". If I restart my dbserver and webserver, then it again works fine.Please give me a solution.

Hi,

"SQL Server does not exist or access denied" is a generic Microsoft Data Access Components (MDAC) message that indicates that the computer that is running Microsoft SQL Server cannot be contacted. Since your problem occurs radomly. So it has many potential causes, the following link may provide some detail information.

http://support.microsoft.com/kb/328306/en-us

Thanks.

Cannot connect to locally SQL Server in C#.net 2005 Express

I am trying to do the Chapter 1 project of Getting Started with ADO.net 2.0 Step by Step (microsoft press)...

I enter the data source configuration wizard and select database, and press next.

I then press the new connection button, and the Choose data source screen appears.

In the List are only 2 options:

Microsoft Access Database File

Microsoft SQL Server Database File.

The option they want me to choose does not appear in the list.

Microsoft SQL Server sqlclient

I tried following the instructions in this thread [http://forums.microsoft.com/msdn/showpost.aspx?postid=85686&siteid=1] where a user had a similar problem, but had no success.

I have reinstalled C#, reinstalled SQL Server Express 2005 with Advanced Tools, but neither helped.

Any help would be greatly appriciated.

sao123

This seems like a difference between Express and Pro edtions of these products. The connections between VS and SQL are slightly different in the Express Edtions of VS. I've read parts of this book and you have to modify the connection instruction when you're using an Express Edition, the book assumes you're using VS Pro.

I found you could either must make a copy of the database into each project and change the connections to be User Instance based, our you could manually Attach the database to the SQL Express Parent and then modify the connection strings manually an not follow the instructions in the book.

Mike

Cannot connect to locally SQL Server in C#.net 2005 Express

I am trying to do the Chapter 1 project of Getting Started with ADO.net 2.0 Step by Step (microsoft press)...

I enter the data source configuration wizard and select database, and press next.

I then press the new connection button, and the Choose data source screen appears.

In the List are only 2 options:

Microsoft Access Database File

Microsoft SQL Server Database File.

The option they want me to choose does not appear in the list.

Microsoft SQL Server sqlclient

I tried following the instructions in this thread [http://forums.microsoft.com/msdn/showpost.aspx?postid=85686&siteid=1] where a user had a similar problem, but had no success.

I have reinstalled C#, reinstalled SQL Server Express 2005 with Advanced Tools, but neither helped.

Any help would be greatly appriciated.

sao123

This seems like a difference between Express and Pro edtions of these products. The connections between VS and SQL are slightly different in the Express Edtions of VS. I've read parts of this book and you have to modify the connection instruction when you're using an Express Edition, the book assumes you're using VS Pro.

I found you could either must make a copy of the database into each project and change the connections to be User Instance based, our you could manually Attach the database to the SQL Express Parent and then modify the connection strings manually an not follow the instructions in the book.

Mike