Cannot deploy to RS2K from Visual Studio 2005

I started using Visual Studio 2005 and when trying to create a SQL Report and
deploy it to a SQL RS 2000 I get this error message "the attemp to connect to
the report server failed. Checked your connection information and that the
report server is a compatible version.
(Microsoft.ReportingServices.Designer)".
Does that mean Visual Studio 2005 is not backward compatible with SQRS2000?
or do I have to modify something in the config of VS2005?
Any ideas?
CarlosYou can deploy 2000 reports to 2005. You cannot deploy 2005 reports to 2000
server.
2005 is backward compatible in the sense that you don't have to modify any
2000 reports for the report to work in 2005 server. However, to use the new
features (multi-select parameters, user run-time sorting etc) you have to
convert the report.
If you think about it, how would 2005 be able to deploy with a 2000 server.
2000 knows nothing about the new features.
You can run side by side for development. If you have to deploy to 2000 then
you need to install RS 2000 report designer and VS 2003 to host the
designer.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Carlos" <carlosarango@.SQLserver.com> wrote in message
news:D638ACB1-553D-4AE4-B87F-156C9E622A79@.microsoft.com...
>I started using Visual Studio 2005 and when trying to create a SQL Report
>and
> deploy it to a SQL RS 2000 I get this error message "the attemp to connect
> to
> the report server failed. Checked your connection information and that the
> report server is a compatible version.
> (Microsoft.ReportingServices.Designer)".
> Does that mean Visual Studio 2005 is not backward compatible with
> SQRS2000?
> or do I have to modify something in the config of VS2005?
> Any ideas?
> Carlos|||Thanks Bruce
"Bruce L-C [MVP]" wrote:
> You can deploy 2000 reports to 2005. You cannot deploy 2005 reports to 2000
> server.
> 2005 is backward compatible in the sense that you don't have to modify any
> 2000 reports for the report to work in 2005 server. However, to use the new
> features (multi-select parameters, user run-time sorting etc) you have to
> convert the report.
> If you think about it, how would 2005 be able to deploy with a 2000 server.
> 2000 knows nothing about the new features.
> You can run side by side for development. If you have to deploy to 2000 then
> you need to install RS 2000 report designer and VS 2003 to host the
> designer.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Carlos" <carlosarango@.SQLserver.com> wrote in message
> news:D638ACB1-553D-4AE4-B87F-156C9E622A79@.microsoft.com...
> >I started using Visual Studio 2005 and when trying to create a SQL Report
> >and
> > deploy it to a SQL RS 2000 I get this error message "the attemp to connect
> > to
> > the report server failed. Checked your connection information and that the
> > report server is a compatible version.
> > (Microsoft.ReportingServices.Designer)".
> >
> > Does that mean Visual Studio 2005 is not backward compatible with
> > SQRS2000?
> > or do I have to modify something in the config of VS2005?
> >
> > Any ideas?
> >
> > Carlos
>
>

Cannot deploy new report

I been not been uploading any new reports for a while but reporting services is running fine on our network.

I added a new report via Visual studio 2003 today but got the following error when trying to deploy

a connection cannot be made to the report server.

Im not sure if sql server 2000 user has been taken off as I was doing a spring clean and may have remove the vital user. This is just a worry, maybe not true.

What users shoulod I have on SQL server to enable deploying of reports, or has anyone come across this problem?

Many thanks in advance

Scott

If anyone else has this problem, I have figured it out for me..

The SSL needed re-importing. Work fine after this. When importing into IE I allowed the system to decided where to put it rather than selecting myself. Hope that helps anyone else

Scott

sql

cannot debug class liberary sproc

im trying to debug a sproc that was written as a class liberary, in c#. i go to the debug menu in visual studio, and click "attach to process". i attach to the sqlsevr process. but now, any breakpoints i create give the message :

"he breakpoint will not currently be hit. no symbols have been loaded for this document"

and no matter how i execute the sproc in sql server, my breakpoints are never hit. what is wrong here?

Have you uploaded the debug symbols file to SQL Server?

ALTER ASSEMBLY your_asm_name
add file from 'some location'

You better check the syntax for ALTER ASSEMBLY as I wrote it from memory and I don't have BOL handy at the moment.

Niels|||Hmm, I was almost certain I had replied to this a couple of minutes ago (I apologize if this post appears twice).

Have you uploaded the debug symbols file from your assembly to the database?

The syntax is as follows:

ALTER ASSEMBLY your_asm_name
ADD FILE FROM 'path_to_debug_symbols'

You better check the syntax above, as I wrote it from memory and I don't have BOL handy.

Nielssql

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 new SQL database.....

I have Visual Studio 2005 Pro. I installed SQL Express 2005 and rebooted.
But, when I right click on "Data Connections" in the Server Explorer and
choose "Create New SQL Server Database..." and attempt to create a new
database on the local PC, I get the following error "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 default
settings SQL Server does not allow remote connections. (provider:
NamedPipes Provider, error:40 - Could not open a connection to SQL Server)".
Any idea what this is?You might get some information by looking in the latest error log in the
c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory. It looks
like your connection is trying to use named pipes to connect and named pipes
are disabled by default in SQL Express so you might try enabling named pipes
with the SQL Server Configuration Manager.(network configuration/protocols)
You may also have to allow SQL Server to open connections through the XP
firewall but that's usually not necessary.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"wally" <wally@.mart.com> wrote in message
news:7PDpg.16987$7K2.406@.bignews2.bellsouth.net...
>I have Visual Studio 2005 Pro. I installed SQL Express 2005 and rebooted.
>But, when I right click on "Data Connections" in the Server Explorer and
>choose "Create New SQL Server Database..." and attempt to create a new
>database on the local PC, I get the following error "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 default
>settings SQL Server does not allow remote connections. (provider:
>NamedPipes Provider, error:40 - Could not open a connection to SQL
>Server)".
> Any idea what this is?
>|||Thanks for the pointers.....but no luck.
To make sure that my installation of SQL Express was good, I uninstalled SE
and deleted the directory it leaves behind.
I restarted the dev box, downloaded SE Basic from
http://msdn.microsoft.com/vstudio/express/sql/download/ and reinstalled it
with the client tools selected.
I tried again....same error.
I enabled both TCP/IP and Named Pipes, restarted the dev box and got the
same error.
I disabled the Windows firewall and tried again....same error.
At this point, I am at a loss as to what the problem could be.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:uHhVVQXnGHA.4452@.TK2MSFTNGP05.phx.gbl...
> You might get some information by looking in the latest error log in the
> c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG directory. It
> looks like your connection is trying to use named pipes to connect and
> named pipes are disabled by default in SQL Express so you might try
> enabling named pipes with the SQL Server Configuration Manager.(network
> configuration/protocols) You may also have to allow SQL Server to open
> connections through the XP firewall but that's usually not necessary.

> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "wally" <wally@.mart.com> wrote in message
> news:7PDpg.16987$7K2.406@.bignews2.bellsouth.net...
>|||@.!#@.#!@.$!@.......The answer is that you CANNOT connect to SQL Express using
the machine name (nevermind that is what is shown in the drop down for the
connection and SQL Express is running as a service that could be queried).
You must manually add "\SQLExpress" (i.e. "machineName\SQLExpress") to be
able to connect to it.
Now just why didn't those brilliant Microsoft minds code that OR AT LEAST
LET US KNOW ABOUT IT?
"wally" <wally@.mart.com> wrote in message
news:eFHpg.81373$qd2.64435@.bignews6.bellsouth.net...
> Thanks for the pointers.....but no luck.
> To make sure that my installation of SQL Express was good, I uninstalled
> SE and deleted the directory it leaves behind.
> I restarted the dev box, downloaded SE Basic from
> http://msdn.microsoft.com/vstudio/express/sql/download/ and reinstalled it
> with the client tools selected.
> I tried again....same error.
> I enabled both TCP/IP and Named Pipes, restarted the dev box and got the
> same error.
> I disabled the Windows firewall and tried again....same error.
> At this point, I am at a loss as to what the problem could be.
>
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:uHhVVQXnGHA.4452@.TK2MSFTNGP05.phx.gbl...
>
>
>
>|||Wally,
Have you installed in past some Beta SQL server products, than you have to
look in the mydocuments folders, it is possible that there are than some
orphaned files. Set those temportaly an other place and try to install
SQLExpress again.
Cor
"wally" <wally@.mart.com> schreef in bericht
news:eFHpg.81373$qd2.64435@.bignews6.bellsouth.net...
> Thanks for the pointers.....but no luck.
> To make sure that my installation of SQL Express was good, I uninstalled
> SE and deleted the directory it leaves behind.
> I restarted the dev box, downloaded SE Basic from
> http://msdn.microsoft.com/vstudio/express/sql/download/ and reinstalled it
> with the client tools selected.
> I tried again....same error.
> I enabled both TCP/IP and Named Pipes, restarted the dev box and got the
> same error.
> I disabled the Windows firewall and tried again....same error.
> At this point, I am at a loss as to what the problem could be.
>
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:uHhVVQXnGHA.4452@.TK2MSFTNGP05.phx.gbl...
>
>
>
>|||Thanks for the help Cor, but the name thing was the issue.
"Cor Ligthert [MVP]" <notmyfirstname@.planet.nl> wrote in message
news:uAUuyfZnGHA.4172@.TK2MSFTNGP03.phx.gbl...
> Wally,
> Have you installed in past some Beta SQL server products, than you have to
> look in the mydocuments folders, it is possible that there are than some
> orphaned files. Set those temportaly an other place and try to install
> SQLExpress again.
> Cor
> "wally" <wally@.mart.com> schreef in bericht
> news:eFHpg.81373$qd2.64435@.bignews6.bellsouth.net...
>|||Wally,
Sorry I did not look well to your follow up. AFAIK does a dot this as well.
Cor
"wally" <wally@.mart.com> schreef in bericht
news:uYIpg.81378$qd2.31318@.bignews6.bellsouth.net...
> Thanks for the help Cor, but the name thing was the issue.
>
> "Cor Ligthert [MVP]" <notmyfirstname@.planet.nl> wrote in message
> news:uAUuyfZnGHA.4172@.TK2MSFTNGP03.phx.gbl...
>|||On Sun, 2 Jul 2006 01:12:26 -0400, "wally" <wally@.mart.com> wrote:

>@.!#@.#!@.$!@.......The answer is that you CANNOT connect to SQL Express using
>the machine name (nevermind that is what is shown in the drop down for the
>connection and SQL Express is running as a service that could be queried).
>You must manually add "\SQLExpress" (i.e. "machineName\SQLExpress") to be
>able to connect to it.
>Now just why didn't those brilliant Microsoft minds code that OR AT LEAST
>LET US KNOW ABOUT IT?
Wally,
The machineName\instanceName thing is well documented in assorted
places. But there is just so much information around that it may not
be easy to find, particularly if you don't know that you need to look
for it.
Andrew Watt MVP

Cannot create new SQL database file.

Hello,

I'm using MS Visual C# 2005 Express, but I can't create a new local database file in the "Add -> New Item" dialog. The Studio doesn't create the database, but shows a file not found message.

Any ideas?

Can you connect to SQL Server Express and create the database manually? If yes, then the issue is within Visual C# and you should post this issue on a Visual C# Express forum. If you encounter an error with manually creating the database, let us know what that error is.

Thanks
Laurentiu

|||

I can connect to the server with the SQL Server Management Studio und create new databases. But Visual C# could't even connect to any existing database. If I click on "Test connection" in add data source dialog the following message shows up:

"Unable to open physical file <path>. Operating System error 32 (Error not found) An attempt to attach a auto-named database failed. A database with the same name exists or the specified file cannot be opened or it's located on an UNC share."

I haven't much experience with the SQL Server, therefore I have now idea what this error means. In fact there is no database with the same name and don't know why it couldn't access the file. Unfortunately I've never heard anything about UNC shares before.

Are there some important steps I have to consider before I create a database manually?

Thanks.

|||

Let's take these as two different problems; connecting to an existing database and creating a database. It's easy to start mixing up the behaivors and confuse the issue.

Creating a DB in VS

Could you describe the exact steps you're using in VS to create a new database? What is the exact error message you're getting? Does your effort result in a database file being created and where does the file end up?

Connecting to an existing DB in VS

Again, what are the exact steps you're using to connect to the database? Is the database already attached to SQL Express? Where is the database file located?

Thanks for the additional detail.

Regards,

Mike Wachal
SQL Express team

-
Please mark your thread as Answered when you get your solution.

|||

Create a DB in VS

When I tried to create a new DB in VS I followed this steps: First of all I loaded my solution then made a right click on my project in the solution explorer and selected "Add Item -> New Item" in the context menu. Finally I selected the SQL DB in the "Add New Item" dialog in order to add a local database file to my project. But it still doesn't work although I have tried it with various file names. VS shows up a short error message ("The system cannot find the specified file.") with the title "Local database file" I cannot find a database file too.

Is it necessary to make any further inititialisations before I can use SQL files in VS? I've already done a lot with VS but I never used SQL before. Because of that I didn't configure anything but the process or service is running in the background.

Connecting to an existing DB in VS

In order to isolate the problem I created a new DB with the MS SQL Server Management Studio Express and tried to connect in VS to the new database considering the following steps: I clicked on "Add New Data Source" in the Data Source Frame in VS. Then I selected a database in the dialog and the file of the database I had created with the Management Studio before. If I detached the DB the VS test connection succeeds but if I click on "OK" VS shows again the same error as if I created the DB directly in VS. ("The system cannot find the specified file.") If I didn't detach the DB, VS failed to establish a test connection because the file is already in use. I moved the database file in different directories but nothing changed.

In the end it seems to me that VS can neither create a database nor connect to a existing one.

Thanks for your support.

Bj?rn

|||

Hi Bjorn,

Create DB in VS

I'll see if any of the VS folks have an idea on this one. What you describe should work.

Connecting to Existing DB in VS

The error you're getting here is expected. In this case, VS is actually creating a connection string that starts a new instance of SQL Express (called a User Instance) and attaches the database to that new instance. Since you can only have a database attached to a single instance of SQL, you get an error. As you've noticed, this problem doesn't happen when you've detached the database from the main instance.

Regards,

Mike Wachal
SQL Express team

-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1

|||

A couple of things. First, it sounds like SQL Server Express (SSE) is not installed on your machine. SSE allows you to make file-based connections to a database without a logical database name (as is the default behavior for the "local" database story in VS.

Secondly, if you are using VC#, VB, or VC Express, you cannot even connect to an up-level version of SQL Server. You can only connect to SSE (the free version of SQL Server). And, in particular, you can *only* make a local database style connection via the tools.

For the version of SQL Server that is running, see if the instance name is "SQLExpress". If it is not, that is the most likely problem. You can download it from the web for free.

Lance

This posting is provided "AS IS" and confers no rights and provides no warranties.

|||

First of all thanks for your support and you are right. It seems I have a SQL Server 2005 version on my system instead of SQL 2005 Express. Therefore I downloaded the SQL Express Version (with Advanced Services) from Microsoft.com but it turns out that I've got another problem. Since I already had an Running SQL Server on my machine (named "Microsoft SQL Server 2005" in control panel->software and running 2 background processes SQLServ and SQLwriter), I followed the download notice and tried to remove the old version. Unfortunately the wizards halts with this meaningful error:

"TITLE: Microsoft SQL Server 2005 Setup. MESSAGE: There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information."

The message comes up whether I stop all SQL processes in the SQL Configuration Manager or not. Furthermore the help button and the related help page don't provide any additional information.

Hence I tried out the other way outlined by the installation instructions. I removed all files from the "\MSSQL.1\MSSQL\Template Data\" directory and ran the installation routine of SQL 2005 Express afterwards, but surprisingly the new wizards halts with the same error already mentioned above.

It's maybe useful to consider that I didn't install the old version explicitly. I guess it comes bundled with Visual C# 2005 Express.

bj?rn

|||

Hi Bjorn,

There seems to be some confusion about whether you actually have SQL Express or not. You've said you don't, but the Template Data directory should even exist unless you actually have SQL Express installed. We need to clear up what you've installed and what you haven't. All versions of VS Express give you the option to install SQL Express.

To determine what you have installed, could you open up SQL Configuration Manager and let me know how many instances of SQL you have listed and what each of them is named?

Also, there should be more information in the setup error logs about the failure you're experiencing. Could you take a look at those logs and let me know what they say?

Thanks for the additional information.

Regards,

Mike Wachal
SQL Express team

-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1

|||

Hello,

There are two instances listed in the SQL Configuration Manager. The first is labeled "SQL Server (SQLExpress)" and is running. The second one is "SQL Server Browser", it's stopped and I can't start it (the run button is disabled).

I found the following setup log:

Microsoft SQL Server 2005 Setup beginning at Wed Apr 26 13:59:32 2006
Process ID : 4028
D:\Programme\Microsoft SQL Server\90\Setup Bootstrap\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2006/3/26 13:59:32
Complete: LoadResourcesAction at: 2006/3/26 13:59:32, returned true
Running: ParseBootstrapOptionsAction at: 2006/3/26 13:59:32
Loaded DLL:D:\Programme\Microsoft SQL Server\90\Setup Bootstrap\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2006/3/26 13:59:32, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run:
Could not parse command line due to datastore exception.
Source File Name: utillib\persisthelpers.cpp
Compiler Timestamp: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 124
-
writeEncryptedString() failed
Source File Name: utillib\persisthelpers.cpp
Compiler Timestamp: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 123
-
Error Code: 0x80070002 (2)
Windows Error Text: Das System kann die angegebene Datei nicht finden.

Source File Name: cryptohelper\cryptsameusersamemachine.cpp
Compiler Timestamp: Mon Jun 13 14:30:00 2005
Function Name: sqls::CryptSameUserSameMachine::ProtectData
Source Line Number: 50

2
Running: ValidateWinNTAction at: 2006/3/26 13:59:32
Complete: ValidateWinNTAction at: 2006/3/26 13:59:32, returned true
Running: ValidateMinOSAction at: 2006/3/26 13:59:32
Complete: ValidateMinOSAction at: 2006/3/26 13:59:32, returned true
Running: PerformSCCAction at: 2006/3/26 13:59:32
Complete: PerformSCCAction at: 2006/3/26 13:59:32, returned true
Running: ActivateLoggingAction at: 2006/3/26 13:59:32
Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run:
Datastore exception while trying to write logging properties.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
-
No collector registered for scope: "SetupStateScope"
00D7CFC4Unable to proceed with setup, there was a command line parsing error. : 2
Error Code: 0x80070002 (2)
Windows Error Text: Das System kann die angegebene Datei nicht finden.

Source File Name: utillib\persisthelpers.cpp
Compiler Timestamp: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 123

Failed to create CAB file due to datastore exception
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "4028"} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupBootstrapOptionsScope.HostSetup
Source Line Number: 44
-
No collector registered for scope: "SetupBootstrapOptionsScope"
Message pump returning: 2

I installed it with VS C# Express and the version is Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86).

Bj?rn

|||

Hi Bjorn,

At this point I'm not sure what's up with your server. From your first message there was something wrong with your copy of C# creating database, but SQL Express seemed find based on the fact that it worked with Management Studio.

If I were you, I'd try to uninstall SQL Express to get it completely off your system and then do a clean installation of either SQL Express or SQL Express with Advanced Services, which ever one you want. I'd try to get back to the state where SQL is working, then if there is still a problem with C#, we can push this thread to one of the VS groups to see if they have any ideas how to fix the VS problem.

Mike

|||

Hello,

I already tried to remove SQL Server from my system, but unfortunately there's the same problem. So I can't even uninstall it.

Errorlog:

Microsoft SQL Server 2005 Setup beginning at Wed May 03 13:16:44 2006
Process ID : 2348
D:\Programme\Microsoft SQL Server\90\Setup Bootstrap\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2006/4/3 13:16:44
Complete: LoadResourcesAction at: 2006/4/3 13:16:44, returned true
Running: ParseBootstrapOptionsAction at: 2006/4/3 13:16:44
Loaded DLL:D:\Programme\Microsoft SQL Server\90\Setup Bootstrap\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2006/4/3 13:16:44, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run:
Could not parse command line due to datastore exception.
Source File Name: utillib\persisthelpers.cpp
Compiler Timestamp: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 124
-
writeEncryptedString() failed
Source File Name: utillib\persisthelpers.cpp
Compiler Timestamp: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 123
-
Error Code: 0x80070002 (2)
Windows Error Text: Das System kann die angegebene Datei nicht finden.

Source File Name: cryptohelper\cryptsameusersamemachine.cpp
Compiler Timestamp: Mon Jun 13 14:30:00 2005
Function Name: sqls::CryptSameUserSameMachine::ProtectData
Source Line Number: 50

2
Running: ValidateWinNTAction at: 2006/4/3 13:16:44
Complete: ValidateWinNTAction at: 2006/4/3 13:16:44, returned true
Running: ValidateMinOSAction at: 2006/4/3 13:16:44
Complete: ValidateMinOSAction at: 2006/4/3 13:16:44, returned true
Running: PerformSCCAction at: 2006/4/3 13:16:44
Complete: PerformSCCAction at: 2006/4/3 13:16:44, returned true
Running: ActivateLoggingAction at: 2006/4/3 13:16:44
Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run:
Datastore exception while trying to write logging properties.
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
-
No collector registered for scope: "SetupStateScope"
00D7CFC4Unable to proceed with setup, there was a command line parsing error. : 2
Error Code: 0x80070002 (2)
Windows Error Text: Das System kann die angegebene Datei nicht finden.

Source File Name: utillib\persisthelpers.cpp
Compiler Timestamp: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 123

Failed to create CAB file due to datastore exception
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "2348"} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupBootstrapOptionsScope.HostSetup
Source Line Number: 44
-
No collector registered for scope: "SetupBootstrapOptionsScope"
Message pump returning: 2

Is it possible that my windows installation is corrupt? But I haven't any other problems except that my system is quite slow.

Bj?rn

|||

Hi Bjorn,

It looks like something failed to uninstall correctly. You can find some suggestions on how to clean up your systems at the following link :

http://blogs/jdbaker/archive/2006/04/20/10684.aspx

I hope that helps

Michelle

Cannot Create New Database

when i am trying to connect to sql server2005 thru Visual studio i am getting an Error:

"SQL Server does not allow remote connections (provider: Named Pipes Provider, error: 40 could not open connection to Sql Server)"

Can any body tell me why is it happening and its Solution....

You will have to enable Remote Connections for your SQL Server instance, by default this is turned off. See the screencast on the screencast section on my website for more details.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Cannot create Linked Server.

Hello.
Can you help me?
I need create Linked server for Visual Fox Pro, but I can not create it.
For DBase no problem, but for VFP, no.
May be anyone have script?
Thank you very much.Try...
exec sp_addlinkedserver
'myVFP',
'',
'MSDASQL',
null,
null,
'Driver=Microsoft Visual Foxpro Driver;
DBQ=;
SourceType=DBF;
SourceDB=x:\VFP'
exec sp_addlinkedsrvlogin 'myVFP',false,null,null,null
-oj
Rac v2.2 & QALite!
http://www.rac4sql.net
"Yuriy B. Belyaev" <jurijb@.mail.ru> wrote in message
news:%23LT5fylhDHA.2536@.TK2MSFTNGP10.phx.gbl...
> Hello.
> Can you help me?
> I need create Linked server for Visual Fox Pro, but I can not create it.
> For DBase no problem, but for VFP, no.
> May be anyone have script?
> Thank you very much.
>
>|||I try
select count(*) from myVFP...goodsfox ("goodsfox" is a table name)
this is message from SQL Server:
Server: Msg 7313, Level 16, State 1, Line 1
Invalid schema or catalog specified for provider 'MSDASQL'.
"oj" <nospam_ojngo@.home.com> wrote in message
news:O9tzICmhDHA.3276@.tk2msftngp13.phx.gbl...
> Try...
> exec sp_addlinkedserver
> 'myVFP',
> '',
> 'MSDASQL',
> null,
> null,
> 'Driver=Microsoft Visual Foxpro Driver;
> DBQ=;
> SourceType=DBF;
> SourceDB=x:\VFP'
> exec sp_addlinkedsrvlogin 'myVFP',false,null,null,null
>
> --
> -oj
> Rac v2.2 & QALite!
> http://www.rac4sql.net
>
> "Yuriy B. Belyaev" <jurijb@.mail.ru> wrote in message
> news:%23LT5fylhDHA.2536@.TK2MSFTNGP10.phx.gbl...
> > Hello.
> >
> > Can you help me?
> > I need create Linked server for Visual Fox Pro, but I can not create it.
> > For DBase no problem, but for VFP, no.
> >
> > May be anyone have script?
> > Thank you very much.
> >
> >
> >
>|||do:
select *
from openquery(myVFP,'select count(*) from goodsfox')
-oj
RAC v2.2 & QALite!
http://www.rac4sql.net
"Yuriy B. Belyaev" <jurijb@.mail.ru> wrote in message
news:e17ZsHmhDHA.3784@.tk2msftngp13.phx.gbl...
> I try
> select count(*) from myVFP...goodsfox ("goodsfox" is a table name)
> this is message from SQL Server:
> Server: Msg 7313, Level 16, State 1, Line 1
> Invalid schema or catalog specified for provider 'MSDASQL'.
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:O9tzICmhDHA.3276@.tk2msftngp13.phx.gbl...
> > Try...
> >
> > exec sp_addlinkedserver
> > 'myVFP',
> > '',
> > 'MSDASQL',
> > null,
> > null,
> > 'Driver=Microsoft Visual Foxpro Driver;
> > DBQ=;
> > SourceType=DBF;
> > SourceDB=x:\VFP'
> >
> > exec sp_addlinkedsrvlogin 'myVFP',false,null,null,null
> >
> >
> > --
> > -oj
> > Rac v2.2 & QALite!
> > http://www.rac4sql.net
> >
> >
> > "Yuriy B. Belyaev" <jurijb@.mail.ru> wrote in message
> > news:%23LT5fylhDHA.2536@.TK2MSFTNGP10.phx.gbl...
> > > Hello.
> > >
> > > Can you help me?
> > > I need create Linked server for Visual Fox Pro, but I can not create
it.
> > > For DBase no problem, but for VFP, no.
> > >
> > > May be anyone have script?
> > > Thank you very much.
> > >
> > >
> > >
> >
> >
>

Cannot create database

I am getting the following message while creating SQL Database on my local machine in Visual Studio:

An error has occured while establishing a connection to the server. When connecting to SQL Sever 2005, this failure may be caused by the fact that under the default settings SQL Sever does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Sever/Instance Specified)what address are you trying to connect via?

Cannot create an instance of OLE DB provider "VFPOLEDB"

I created a view refer to a visual foxpro with ole db for visual foxpro which was working fine before. But now, I received an error while select the view

Msg 7302, Level 16, State 1, Line 1
Cannot create an instance of OLE DB provider "VFPOLEDB" for linked server "ORST3".

Please advise. Thanks in advance

Hi Stephanie,

You posted this question to microsoft.public.data.oledb on April 3. Later in the thread you said you were successful getting it working, partly due to enabling "Allow inprocess" in the OLE DB setup.

Is this a new problem since you posted on April 3?

Cannot create a connection to data source

I created a very simple report just to see how Reporting Services works adn
it shows all the data just fine in the preview inside Visual Studio but whe
I run the report it shows me this error:
Reporting Services Error
----
--
a.. An error has occurred during report processing. (rsProcessingAborted)
Get Online Help
a.. Cannot create a connection to data source 'Northwind'.
(rsErrorOpeningConnection) Get Online Help
a.. Login failed for user 'sa'.
----
--
Microsoft Reporting Services
Isn't this weird? I mean, I'm working with a shared data source which
connects properly when I test it and the data gets shwon on the preview so
why doesn't it work?.
--
Sergio Florez M.
Medellin, ColombiaSergio,
In your data source, check for "allow saving password". You should also
consider using windows authentication instead.
Jon Jahren
"Sergio Florez M." <sergioflorezm @. hotmail.com> wrote in message
news:OcSs0hDyEHA.3804@.TK2MSFTNGP10.phx.gbl...
> I created a very simple report just to see how Reporting Services works
adn
> it shows all the data just fine in the preview inside Visual Studio but
whe
> I run the report it shows me this error:
> Reporting Services Error
> ----
--
> --
> a.. An error has occurred during report processing.
(rsProcessingAborted)
> Get Online Help
> a.. Cannot create a connection to data source 'Northwind'.
> (rsErrorOpeningConnection) Get Online Help
> a.. Login failed for user 'sa'.
> ----
--
> --
> Microsoft Reporting Services
> Isn't this weird? I mean, I'm working with a shared data source which
> connects properly when I test it and the data gets shwon on the preview so
> why doesn't it work?.
> --
> Sergio Florez M.
> Medellin, Colombia
>|||I changed the connection settings in the report manager and now it works
fine. Now I have the same problem in a report that I created without a
shared data source and I can't find how to allow saving password.
Changing to Windows authentication isn't the kind of solution I'm looking
for as it should work just fine either way.
--
Sergio Florez M.
Medellin, Colombia
"Jon Jahren" <jon.jahren.fightspam@.sqlkompetanse.no> wrote in message
news:uzkq#1JyEHA.2676@.TK2MSFTNGP12.phx.gbl...
> Sergio,
> In your data source, check for "allow saving password". You should also
> consider using windows authentication instead.
> Jon Jahren
> "Sergio Florez M." <sergioflorezm @. hotmail.com> wrote in message
> news:OcSs0hDyEHA.3804@.TK2MSFTNGP10.phx.gbl...
> > I created a very simple report just to see how Reporting Services works
> adn
> > it shows all the data just fine in the preview inside Visual Studio but
> whe
> > I run the report it shows me this error:
> >
> > Reporting Services Error
> ----
> --
> > --
> >
> > a.. An error has occurred during report processing.
> (rsProcessingAborted)
> > Get Online Help
> > a.. Cannot create a connection to data source 'Northwind'.
> > (rsErrorOpeningConnection) Get Online Help
> > a.. Login failed for user 'sa'.
> >
> ----
> --
> > --
> > Microsoft Reporting Services
> >
> > Isn't this weird? I mean, I'm working with a shared data source which
> > connects properly when I test it and the data gets shwon on the preview
so
> > why doesn't it work?.
> >
> > --
> > Sergio Florez M.
> > Medellin, Colombia
> >
> >
>

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 via Web Application...

I am using SQLServer 2000, Visual Studio 2003, C#.
I am writing a web part which requires me to connect to a local sql
database.
I wrote a class which handles the connection and reading of the table.
When I try to call .Open on the connection, it fails, the exception is
something to do with permission.
I used the same class to connect with a console application and a
windows application, and it works fine. I am able to connect and read
the table.
Can anyone shed some light on what is the difference between
connecting/accessing to a database via Web Application as opposed to a
Non-Web App.
TIAI think your problem has something to do with permission as the error
indicates. If you are writing an ASP.Net web page then your web application
is running as the ASPUSER Windows user and chances are this use does not
have permissions to connect to the database. When you run as a Windows
application you run as you and you probably have admin permissions on the
box which gives you SA permissions in the database so you can do whatever
you want. Confirm that you are running as ASPUSER and then create a login
and user for it in SQL Server.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
news:1168476873.734347.313800@.k58g2000hse.googlegroups.com...
>I am using SQLServer 2000, Visual Studio 2003, C#.
> I am writing a web part which requires me to connect to a local sql
> database.
> I wrote a class which handles the connection and reading of the table.
> When I try to call .Open on the connection, it fails, the exception is
> something to do with permission.
> I used the same class to connect with a console application and a
> windows application, and it works fine. I am able to connect and read
> the table.
> Can anyone shed some light on what is the difference between
> connecting/accessing to a database via Web Application as opposed to a
> Non-Web App.
> TIA
>|||Roger,
Thanks for the reply.
I ran SQL Server Enterprise Manager and for that database, I checked
the Users.
there are two, dbo and guest, both having full permissions.
How would I confirm tthat I am running as ASPUSER and create a login
for it?
Thanks,
IV
Roger Wolter[MSFT] wrote:[vbcol=seagreen]
> I think your problem has something to do with permission as the error
> indicates. If you are writing an ASP.Net web page then your web applicati
on
> is running as the ASPUSER Windows user and chances are this use does not
> have permissions to connect to the database. When you run as a Windows
> application you run as you and you probably have admin permissions on the
> box which gives you SA permissions in the database so you can do whatever
> you want. Confirm that you are running as ASPUSER and then create a login
> and user for it in SQL Server.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
> news:1168476873.734347.313800@.k58g2000hse.googlegroups.com...|||Log in as an admin. USE the database where your tables are and execute
these commands (substituting the name of you machine for servername)
CREATE LOGIN [servername\ASPNET] FROM WINDOWS
CREATE USER [servername\ASPNET] FROM LOGIN [servername\ASPNET]
http://msdn2.microsoft.com/en-us/library/ms189751.aspx
http://msdn2.microsoft.com/en-us/library/ms173463.aspx
You will then have to grant this user access to the objects it needs to
access for your application
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
news:1168487427.667116.147270@.p59g2000hsd.googlegroups.com...
> Roger,
> Thanks for the reply.
> I ran SQL Server Enterprise Manager and for that database, I checked
> the Users.
> there are two, dbo and guest, both having full permissions.
> How would I confirm tthat I am running as ASPUSER and create a login
> for it?
> Thanks,
> IV
> Roger Wolter[MSFT] wrote:
>|||Roger,
I appreciate you taking the time to help me out.
I tried what you said and am still failing with the same exception.
Imtiaz
Roger Wolter[MSFT] wrote:[vbcol=seagreen]
> Log in as an admin. USE the database where your tables are and execute
> these commands (substituting the name of you machine for servername)
> CREATE LOGIN [servername\ASPNET] FROM WINDOWS
> CREATE USER [servername\ASPNET] FROM LOGIN [servername\ASPNET]
> http://msdn2.microsoft.com/en-us/library/ms189751.aspx
> http://msdn2.microsoft.com/en-us/library/ms173463.aspx
> You will then have to grant this user access to the objects it needs to
> access for your application
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
> news:1168487427.667116.147270@.p59g2000hsd.googlegroups.com...

Cannot connect via Web Application...

I am using SQLServer 2000, Visual Studio 2003, C#.
I am writing a web part which requires me to connect to a local sql
database.
I wrote a class which handles the connection and reading of the table.
When I try to call .Open on the connection, it fails, the exception is
something to do with permission.
I used the same class to connect with a console application and a
windows application, and it works fine. I am able to connect and read
the table.
Can anyone shed some light on what is the difference between
connecting/accessing to a database via Web Application as opposed to a
Non-Web App.
TIA
I think your problem has something to do with permission as the error
indicates. If you are writing an ASP.Net web page then your web application
is running as the ASPUSER Windows user and chances are this use does not
have permissions to connect to the database. When you run as a Windows
application you run as you and you probably have admin permissions on the
box which gives you SA permissions in the database so you can do whatever
you want. Confirm that you are running as ASPUSER and then create a login
and user for it in SQL Server.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
news:1168476873.734347.313800@.k58g2000hse.googlegr oups.com...
>I am using SQLServer 2000, Visual Studio 2003, C#.
> I am writing a web part which requires me to connect to a local sql
> database.
> I wrote a class which handles the connection and reading of the table.
> When I try to call .Open on the connection, it fails, the exception is
> something to do with permission.
> I used the same class to connect with a console application and a
> windows application, and it works fine. I am able to connect and read
> the table.
> Can anyone shed some light on what is the difference between
> connecting/accessing to a database via Web Application as opposed to a
> Non-Web App.
> TIA
>
|||Roger,
Thanks for the reply.
I ran SQL Server Enterprise Manager and for that database, I checked
the Users.
there are two, dbo and guest, both having full permissions.
How would I confirm tthat I am running as ASPUSER and create a login
for it?
Thanks,
IV
Roger Wolter[MSFT] wrote:[vbcol=seagreen]
> I think your problem has something to do with permission as the error
> indicates. If you are writing an ASP.Net web page then your web application
> is running as the ASPUSER Windows user and chances are this use does not
> have permissions to connect to the database. When you run as a Windows
> application you run as you and you probably have admin permissions on the
> box which gives you SA permissions in the database so you can do whatever
> you want. Confirm that you are running as ASPUSER and then create a login
> and user for it in SQL Server.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
> news:1168476873.734347.313800@.k58g2000hse.googlegr oups.com...
|||Log in as an admin. USE the database where your tables are and execute
these commands (substituting the name of you machine for servername)
CREATE LOGIN [servername\ASPNET] FROM WINDOWS
CREATE USER [servername\ASPNET] FROM LOGIN [servername\ASPNET]
http://msdn2.microsoft.com/en-us/library/ms189751.aspx
http://msdn2.microsoft.com/en-us/library/ms173463.aspx
You will then have to grant this user access to the objects it needs to
access for your application
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
news:1168487427.667116.147270@.p59g2000hsd.googlegr oups.com...
> Roger,
> Thanks for the reply.
> I ran SQL Server Enterprise Manager and for that database, I checked
> the Users.
> there are two, dbo and guest, both having full permissions.
> How would I confirm tthat I am running as ASPUSER and create a login
> for it?
> Thanks,
> IV
> Roger Wolter[MSFT] wrote:
>
|||Roger,
I appreciate you taking the time to help me out.
I tried what you said and am still failing with the same exception.
Imtiaz
Roger Wolter[MSFT] wrote:[vbcol=seagreen]
> Log in as an admin. USE the database where your tables are and execute
> these commands (substituting the name of you machine for servername)
> CREATE LOGIN [servername\ASPNET] FROM WINDOWS
> CREATE USER [servername\ASPNET] FROM LOGIN [servername\ASPNET]
> http://msdn2.microsoft.com/en-us/library/ms189751.aspx
> http://msdn2.microsoft.com/en-us/library/ms173463.aspx
> You will then have to grant this user access to the objects it needs to
> access for your application
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "IV" <Imtiaz.Vohra@.vtechsr.com> wrote in message
> news:1168487427.667116.147270@.p59g2000hsd.googlegr oups.com...

Cannot connect to SQL Server

I have an SQL Server 2005 installed on one partition (G:). Visual Studio 2005 with C# is on C: The OS on C:\ is Win2K Pro, OS on G: is WinServ2003.

I've created a database on G: in SQL Management Studio. Its name is "endPoint_forMe" The Server (default) as I can see is ALEX-*** data source is "strongUpdate" which is one of the tables in the database "endPoint..."

I cannot establish connection. What am I doing wrong?

I checked in the Control Panel-->>Management Tools-->>IIS on C:. Only one server is registered there: My computer name. There is no way to add another server.

string myConnString = "Persist Security Info=False;Integrated Security=SSPI;database=endPoint_forMe;server=ALEX-OPLHOFP92;data source=strongUpdate";

SqlConnection myConnection = new SqlConnection(myConnString);

myConnection.Open();

The last statement does not connect. I get an error report while debugging. What shall I do?

// Can you try the following:

private String GetConnectionString(

String SqlInstanceName,

String DataBaseName)

{

System.Text.StringBuilder sb = new System.Text.StringBuilder();

sb.Append("data source=") ;

sb.Append(SqlInstanceName);

sb.Append(";initial catalog=") ;

sb.Append(DataBaseName);

sb.Append(";integrated security=SSPI;") ;

sb.Append("persist security info=False;") ;

sb.Append("workstation id=") ;

sb.Append(System.Environment.MachineName) ;

sb.Append(";packet size=4096") ;

return(sb.ToString());

}

private void button2_Click(object sender, EventArgs e)

{

String cs = GetConnectionString(".", "model");

System.Data.SqlClient.SqlConnection cn =

new System.Data.SqlClient.SqlConnection(cs);

cn.Open();

if (cn.State == ConnectionState.Open)

System.Windows.Forms.MessageBox.Show("success");

else

System.Windows.Forms.MessageBox.Show("fail");

cn.Close();

}
// the "." is the default instance on the current computer, "model" is the catalog...

|||

I've tried this string.

string myConnString = "Data Source=(local);Initial Catalog=endPoint_forMe;Integrated Security=SSPI;";

The debug shows that the system runs out of time trying to make the connection. I increased the time parameter from 30 to 130 sec in Tools-->Options-->database-->queries.

I don't think it helped. The same exception with the same error message.

Pl help.

Thanks.

|||Hello

> server=ALEX-OPLHOFP92

I had a comparable problem with the new security (TCP/IP turned off by default). Have you used "SQL Server Surface Area Configuration" or "SQL Server Configuration Manager" to enable TCP/IP?|||Many thanks.

Sure, mine was disabled! I just enabled it and am rushing to test the connection.

God bless newsgroups friendly help.

Thanks.|||Thank you very much. It is very interesting. I will try it and report the outcome. I feel it should work.|||It turns out not only TCP/IP was disabled but the MSSQLSERVER is stopped! SQL Server Agent is stopped also!

The trouble is I cannot get them started.

This is a part of the error log resulting from my attempt to start the Server. I quote error messages only:

2005-10-30 15:35:44.79 Server Error: 17182, Severity: 16, State: 1.
2005-10-30 15:35:44.79 Server TDSSNIClient initialization failed with error 0xd, status code 0x36.
2005-10-30 15:35:44.79 Server Error: 17182, Severity: 16, State: 1.
2005-10-30 15:35:44.79 Server TDSSNIClient initialization failed with error 0xd, status code 0x1.
2005-10-30 15:35:44.79 Server Error: 17826, Severity: 18, State: 3.
2005-10-30 15:35:44.79 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2005-10-30 15:35:44.79 Server Error: 17120, Severity: 16, State: 1.
2005-10-30 15:35:44.79 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

What shall I do about the "network library" which is apparently corrupted?

Thanks.|||

Try checking what network protocols are enabled for SQL Server in the SQL Computer Manager application. If the VIA protocol is enabled disable it and then try starting the SQL Server service again.

Hope this helps,
Vaughn

|||You were right. I enabled it along with TCP/IP. After disabling VIA the server got started.

Thanks a lot.|||Eduardo hi,

All my attempts to enable a connection so far have failed. I cannot achieve it either programmatically as you suggested or via the GUI at VS where a special pane exists for attached databases. I am wondering if a prerequisite for a healthy connection is SQL Server.2005 up and running? In my current setting it is next to impossible to accomplish. My SQL Server.2005 is on a partition under the OS WinSer2003 but the Visual Studio with C# and all other stuff (the client, the recepient of the connection) is on C: under Win2K Pro. Thus I am trying to connect to an inactive database which exists in a directory. It seems to me that the notion of the Server instance is inapplicable here. Am I wrong? And the Server Instance is a component of the connection string!

If this is the case then I have to somehow set VS with C# up on the other partition with the server. The SQL Server does have a VS variant supporting the SQL Server but it is not furnished with C# compiler, I understand.

Typical error message I get when I run a program trying to make connection is that the timeout expired or the SQL Server is not responding.

Please comment on this.

Thanks.|||I just made connection with GUI but only when I invoked the VS on the same partition where SQL Server resides. It was a snap job, very elementary. The SQL Server was not even running at all. It is just important to have it on the same partition under the same OS.

My troubles are not over yet. It is a stip down version of VS I have here. Now I may try to install the full version on this partition and see how it goes. I need access to C# compiler and debugger. It is not a part of the VS that comes with SQL Server as I can see.

Thanks.|||

Got the problem solved by your helps by disabling the VIA protocol. Do you know what's the reason to cause the problem?

Cannot connect to SQL Server

I have an SQL Server 2005 installed on one partition (G:). Visual Studio 2005 with C# is on C: The OS on C:\ is Win2K Pro, OS on G: is WinServ2003.

I've created a database on G: in SQL Management Studio. Its name is "endPoint_forMe" The Server (default) as I can see is ALEX-*** data source is "strongUpdate" which is one of the tables in the database "endPoint..."

I cannot establish connection. What am I doing wrong?

I checked in the Control Panel-->>Management Tools-->>IIS on C:. Only one server is registered there: My computer name. There is no way to add another server.

string myConnString = "Persist Security Info=False;Integrated Security=SSPI;database=endPoint_forMe;server=ALEX-OPLHOFP92;data source=strongUpdate";

SqlConnection myConnection = new SqlConnection(myConnString);

myConnection.Open();

The last statement does not connect. I get an error report while debugging. What shall I do?

// Can you try the following:

private String GetConnectionString(

String SqlInstanceName,

String DataBaseName)

{

System.Text.StringBuilder sb = new System.Text.StringBuilder();

sb.Append("data source=") ;

sb.Append(SqlInstanceName);

sb.Append(";initial catalog=") ;

sb.Append(DataBaseName);

sb.Append(";integrated security=SSPI;") ;

sb.Append("persist security info=False;") ;

sb.Append("workstation id=") ;

sb.Append(System.Environment.MachineName) ;

sb.Append(";packet size=4096") ;

return(sb.ToString());

}

private void button2_Click(object sender, EventArgs e)

{

String cs = GetConnectionString(".", "model");

System.Data.SqlClient.SqlConnection cn =

new System.Data.SqlClient.SqlConnection(cs);

cn.Open();

if (cn.State == ConnectionState.Open)

System.Windows.Forms.MessageBox.Show("success");

else

System.Windows.Forms.MessageBox.Show("fail");

cn.Close();

}
// the "." is the default instance on the current computer, "model" is the catalog...

|||

I've tried this string.

string myConnString = "Data Source=(local);Initial Catalog=endPoint_forMe;Integrated Security=SSPI;";

The debug shows that the system runs out of time trying to make the connection. I increased the time parameter from 30 to 130 sec in Tools-->Options-->database-->queries.

I don't think it helped. The same exception with the same error message.

Pl help.

Thanks.

|||Hello

> server=ALEX-OPLHOFP92

I had a comparable problem with the new security (TCP/IP turned off by default). Have you used "SQL Server Surface Area Configuration" or "SQL Server Configuration Manager" to enable TCP/IP?|||Many thanks.

Sure, mine was disabled! I just enabled it and am rushing to test the connection.

God bless newsgroups friendly help.

Thanks.|||Thank you very much. It is very interesting. I will try it and report the outcome. I feel it should work.|||It turns out not only TCP/IP was disabled but the MSSQLSERVER is stopped! SQL Server Agent is stopped also!

The trouble is I cannot get them started.

This is a part of the error log resulting from my attempt to start the Server. I quote error messages only:

2005-10-30 15:35:44.79 Server Error: 17182, Severity: 16, State: 1.
2005-10-30 15:35:44.79 Server TDSSNIClient initialization failed with error 0xd, status code 0x36.
2005-10-30 15:35:44.79 Server Error: 17182, Severity: 16, State: 1.
2005-10-30 15:35:44.79 Server TDSSNIClient initialization failed with error 0xd, status code 0x1.
2005-10-30 15:35:44.79 Server Error: 17826, Severity: 18, State: 3.
2005-10-30 15:35:44.79 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2005-10-30 15:35:44.79 Server Error: 17120, Severity: 16, State: 1.
2005-10-30 15:35:44.79 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

What shall I do about the "network library" which is apparently corrupted?

Thanks.|||

Try checking what network protocols are enabled for SQL Server in the SQL Computer Manager application. If the VIA protocol is enabled disable it and then try starting the SQL Server service again.

Hope this helps,
Vaughn

|||You were right. I enabled it along with TCP/IP. After disabling VIA the server got started.

Thanks a lot.|||Eduardo hi,

All my attempts to enable a connection so far have failed. I cannot achieve it either programmatically as you suggested or via the GUI at VS where a special pane exists for attached databases. I am wondering if a prerequisite for a healthy connection is SQL Server.2005 up and running? In my current setting it is next to impossible to accomplish. My SQL Server.2005 is on a partition under the OS WinSer2003 but the Visual Studio with C# and all other stuff (the client, the recepient of the connection) is on C: under Win2K Pro. Thus I am trying to connect to an inactive database which exists in a directory. It seems to me that the notion of the Server instance is inapplicable here. Am I wrong? And the Server Instance is a component of the connection string!

If this is the case then I have to somehow set VS with C# up on the other partition with the server. The SQL Server does have a VS variant supporting the SQL Server but it is not furnished with C# compiler, I understand.

Typical error message I get when I run a program trying to make connection is that the timeout expired or the SQL Server is not responding.

Please comment on this.

Thanks.|||I just made connection with GUI but only when I invoked the VS on the same partition where SQL Server resides. It was a snap job, very elementary. The SQL Server was not even running at all. It is just important to have it on the same partition under the same OS.

My troubles are not over yet. It is a stip down version of VS I have here. Now I may try to install the full version on this partition and see how it goes. I need access to C# compiler and debugger. It is not a part of the VS that comes with SQL Server as I can see.

Thanks.|||

Got the problem solved by your helps by disabling the VIA protocol. Do you know what's the reason to cause the problem?

Cannot connect to SQL Express from my Application

Hey everyone, I'm having trouble connecting to my sql express instance through my vb.net application. I can connect to it from Visual Studio and the management tools, but get an error when connection with a connection string. What should my connection string look like? I'm using the a default SQLEXPRESS instance.

Can you try connection string like this "server=.\\SQLExpress;Trusted_Connection=true;"

|||I mean "server=.\SQLExpress;Trusted_Connection=true;"|||no luck so far. Just timeouts.. aarrrrr.

Cannot connect to SQL Express db with visual c++

I've installed both SQL Server Express and Visual C++. I'm trying to connect to a SQL database, but keep receiving various errors. This is what I've done so far.

1. Eventually, I used the surface area manager to allow a remote connect.

2. The server and my development environment exist on the same virtual machine, I created with Virtual Pc.

3. I'm running Vista as my operating system.

4. My Data Source wizard looks like this:

Data Source: MS SQL Database File

Database file name: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ETS.mdf

If I use Windows Authen I get the following error:

Unable to open physical file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ETS_log.ldf" Operating System Error 5: (Access is Denied). An attempt to attach to an auto-named database for file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ETS.mdf failed. A database with the same name exist , or specified file cannot be opened, or it is located on a UNC share.

If I use SQL Server Authen I get the following error:

Failed to generate a user instance of SQL Server. Only an integrated connection can generate a user instance. The connection will be closed.

I'm new to this. I really would like help in knowing what these errors mean and how to get pass them. But this is very, very, very, frustrating. First off, there was no instructions on allowing remote connections. I stumble upon it myself. Giving permission to the file, stumble upon myself. I spent 4 days with a You do not have permission to open file error. Didn't realize I didn't have permission.

I need a step by step on what to do. I can be emailed at gregw.energytaxsolutions@.hotmail.com if need be.

If this is in the wrong place, moderator please move to the correct area.

Redirected from visual c++ express forum to SQL Server Express forum.

In case you are disagree with the movement, please feel free to point it out so that we can have further discuss.

|||

hi,

you are using the User Instance feature of SQLExpress edition and this "method" only supports Windows authenticated connections and not mixed mode connections with standard SQL Server logins...

the other problem regards the permissions on the folder containing the referenced database file... the path must be accessible by the user instance.. please read the linked article about that..

regards

|||Thank you for the direction to the article, it was really informative (although I didn't quite understand everything it was talking about). I did get the overall jist of what it was trying to tell me. I have a lot to learn. If anyone knows of a good source of where to start, I would really appreciate it.|||

hi Gregw,

additional information about User Instances can be found at http://msdn2.microsoft.com/en-us/library/ms143684.aspx, http://msdn2.microsoft.com/en-us/library/ms345154.aspx, http://msdn2.microsoft.com/en-us/library/ms254504.aspx..

regards