Asp.net / sql help: beta

Showing posts with label beta. Show all posts

Sunday, March 25, 2012

Attach Database

I have a database, I was using in SQL server 2005 beta 2. Now I want to
attach this database in SQL server 2000 machine. but when I attached this
database, it gives error 602, Could not find row in sysindexes for database
ID 12, object ID 1, index 1, index ID 1, Run DBCC CHECKTABLE on sysindexes.
Can we do this.I haven't tested it, or bothered to look in the docs, but I would be
surprised if this was in fact supported.
Have you looked in Books Online for SQL Server 2005 to see what it says
about detached DBs?
--
Brian
"Rajaram" <Rajaram@.discussions.microsoft.com> wrote in message
news:6EA3C9EF-8DA7-44CB-ACD3-E4F56B5F5EEE@.microsoft.com...
> I have a database, I was using in SQL server 2005 beta 2. Now I want to
> attach this database in SQL server 2000 machine. but when I attached this
> database, it gives error 602, Could not find row in sysindexes for
database
> ID 12, object ID 1, index 1, index ID 1, Run DBCC CHECKTABLE on
sysindexes.
> Can we do this.|||Brian's right, it's not supported. You can attach SQL Server 2000 databases
to SQL Server 2005, but not the other way around.
--
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:eC7gNfjoEHA.3792@.TK2MSFTNGP11.phx.gbl...
>I haven't tested it, or bothered to look in the docs, but I would be
> surprised if this was in fact supported.
> Have you looked in Books Online for SQL Server 2005 to see what it says
> about detached DBs?
> --
> Brian
>
> "Rajaram" <Rajaram@.discussions.microsoft.com> wrote in message
> news:6EA3C9EF-8DA7-44CB-ACD3-E4F56B5F5EEE@.microsoft.com...
>> I have a database, I was using in SQL server 2005 beta 2. Now I want to
>> attach this database in SQL server 2000 machine. but when I attached this
>> database, it gives error 602, Could not find row in sysindexes for
> database
>> ID 12, object ID 1, index 1, index ID 1, Run DBCC CHECKTABLE on
> sysindexes.
>> Can we do this.
>|||You can't downgrade using BACKUP/RESTORE or detach/attach.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Rajaram" <Rajaram@.discussions.microsoft.com> wrote in message
news:6EA3C9EF-8DA7-44CB-ACD3-E4F56B5F5EEE@.microsoft.com...
> I have a database, I was using in SQL server 2005 beta 2. Now I want to
> attach this database in SQL server 2000 machine. but when I attached this
> database, it gives error 602, Could not find row in sysindexes for database
> ID 12, object ID 1, index 1, index ID 1, Run DBCC CHECKTABLE on sysindexes.
> Can we do this.

Attach Database

I have a database, I was using in SQL server 2005 beta 2. Now I want to
attach this database in SQL server 2000 machine. but when I attached this
database, it gives error 602, Could not find row in sysindexes for database
ID 12, object ID 1, index 1, index ID 1, Run DBCC CHECKTABLE on sysindexes.
Can we do this.
I haven't tested it, or bothered to look in the docs, but I would be
surprised if this was in fact supported.
Have you looked in Books Online for SQL Server 2005 to see what it says
about detached DBs?
Brian
"Rajaram" <Rajaram@.discussions.microsoft.com> wrote in message
news:6EA3C9EF-8DA7-44CB-ACD3-E4F56B5F5EEE@.microsoft.com...
> I have a database, I was using in SQL server 2005 beta 2. Now I want to
> attach this database in SQL server 2000 machine. but when I attached this
> database, it gives error 602, Could not find row in sysindexes for
database
> ID 12, object ID 1, index 1, index ID 1, Run DBCC CHECKTABLE on
sysindexes.
> Can we do this.
|||Brian's right, it's not supported. You can attach SQL Server 2000 databases
to SQL Server 2005, but not the other way around.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:eC7gNfjoEHA.3792@.TK2MSFTNGP11.phx.gbl...
>I haven't tested it, or bothered to look in the docs, but I would be
> surprised if this was in fact supported.
> Have you looked in Books Online for SQL Server 2005 to see what it says
> about detached DBs?
> --
> Brian
>
> "Rajaram" <Rajaram@.discussions.microsoft.com> wrote in message
> news:6EA3C9EF-8DA7-44CB-ACD3-E4F56B5F5EEE@.microsoft.com...
> database
> sysindexes.
>
|||You can't downgrade using BACKUP/RESTORE or detach/attach.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Rajaram" <Rajaram@.discussions.microsoft.com> wrote in message
news:6EA3C9EF-8DA7-44CB-ACD3-E4F56B5F5EEE@.microsoft.com...
> I have a database, I was using in SQL server 2005 beta 2. Now I want to
> attach this database in SQL server 2000 machine. but when I attached this
> database, it gives error 602, Could not find row in sysindexes for database
> ID 12, object ID 1, index 1, index ID 1, Run DBCC CHECKTABLE on sysindexes.
> Can we do this.

attach 2005 db on 2000

As far as I remember
from the original post, the situation is that he has a database detached
from SQL Server 2005, but no SQL Server 2005 instance.
He can install one though...
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging
|||That they have to manage.
Regards
Amish
|||No. The internal bits are different. You can not attach a 2005 database to
2000.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"Andre" <no@.spam.com> wrote in message
news:%23p$1Pm8DGHA.344@.TK2MSFTNGP11.phx.gbl...
>I have a sql 2005 beta 2 db that I need to move back to a sql 2000 box. Is
>there any way to do this if I no longer have sql 2005 running? I detached
>and saved the db, but I don't have 2005 running anywhere anymore.
> Thanks, Andre
>
|||Thanks all.
In fact, I did end up installing SQL2005 beta 2 on another box. Then the
fun began because that box didn't have enough disk space to hold my 2005 db
that I was concerned with. But fortunately I found the article that showed
my how to flip a traceflag so that I could connect the db to a network
share. That worked - and then I used Integration Services (dts) to transfer
the data to a new sql 2k db. Where there's a will, there's a way.

Andre

attach 2005 db on 2000

I have a sql 2005 beta 2 db that I need to move back to a sql 2000 box. Is
there any way to do this if I no longer have sql 2005 running? I detached
and saved the db, but I don't have 2005 running anywhere anymore.
Thanks, Andre"Andre" <no@.spam.com> wrote in
news:#p$1Pm8DGHA.344@.TK2MSFTNGP11.phx.gbl:
> I have a sql 2005 beta 2 db that I need to move back to a sql 2000
> box. Is there any way to do this if I no longer have sql 2005
> running? I detached and saved the db, but I don't have 2005 running
> anywhere anymore.
Unfortunately, I do not think so. It's quite possible to attach a SQL
Server 2000 to SQL Server 2005, but as far as I know not the other way
around.
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging|||Bummer, that's what I was afraid of. Thanks for the reply.|||1. Create new database in SQL 2000
2. Genarete script from objtects on the SQL 2005
3. Execute this script on the SQL 2000
If you have data, use bcp utilities or DTS/SSIS to export and import.
Regards
Amish|||"amish" <shahamishm@.gmail.com> wrote in news:1136273968.474136.28240
@.g44g2000cwa.googlegroups.com:
> 1. Create new database in SQL 2000
> 2. Genarete script from objtects on the SQL 2005
> 3. Execute this script on the SQL 2000
> If you have data, use bcp utilities or DTS/SSIS to export and import.
Of course, there are only one problem: There are no SQL Server 2005
instance, so there is nowhere to create the scripts :) As far as I remember
from the original post, the situation is that he has a database detached
from SQL Server 2005, but no SQL Server 2005 instance.
He can install one though...
--
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging|||That they have to manage.
Regards
Amish|||No. The internal bits are different. You can not attach a 2005 database to
2000.
--
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"Andre" <no@.spam.com> wrote in message
news:%23p$1Pm8DGHA.344@.TK2MSFTNGP11.phx.gbl...
>I have a sql 2005 beta 2 db that I need to move back to a sql 2000 box. Is
>there any way to do this if I no longer have sql 2005 running? I detached
>and saved the db, but I don't have 2005 running anywhere anymore.
> Thanks, Andre
>|||Thanks all.
In fact, I did end up installing SQL2005 beta 2 on another box. Then the
fun began because that box didn't have enough disk space to hold my 2005 db
that I was concerned with. But fortunately I found the article that showed
my how to flip a traceflag so that I could connect the db to a network
share. That worked - and then I used Integration Services (dts) to transfer
the data to a new sql 2k db. Where there's a will, there's a way. :)
Andre

attach 2005 db on 2000

As far as I remember
from the original post, the situation is that he has a database detached
from SQL Server 2005, but no SQL Server 2005 instance.
He can install one though...
Ole Kristian Bangs
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging|||That they have to manage.
Regards
Amish|||No. The internal bits are different. You can not attach a 2005 database to
2000.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"Andre" <no@.spam.com> wrote in message
news:%23p$1Pm8DGHA.344@.TK2MSFTNGP11.phx.gbl...
>I have a sql 2005 beta 2 db that I need to move back to a sql 2000 box. Is
>there any way to do this if I no longer have sql 2005 running? I detached
>and saved the db, but I don't have 2005 running anywhere anymore.
> Thanks, Andre
>|||Thanks all.
In fact, I did end up installing SQL2005 beta 2 on another box. Then the
fun began because that box didn't have enough disk space to hold my 2005 db
that I was concerned with. But fortunately I found the article that showed
my how to flip a traceflag so that I could connect the db to a network
share. That worked - and then I used Integration Services (dts) to transfer
the data to a new sql 2k db. Where there's a will, there's a way.

Andre

Monday, March 19, 2012

Assisted Editor for stored procedures

I have been using SQL server management studio beta to manage my SQL server 2000 and to develop stored procedures. I was very happy with Assisted Editor, but it seems to be missing from final SQL server 2005 products (developer's version) Sad .

In object browser when I right-click on stored procedure and chose modify I used to get Assisted editor (described in http://msdn.microsoft.com/sql/learn/prog/tsql/default.aspx?pull=/library/en-us/dnsql90/html/tsqlqueries.asp). Now I get full Alter procedure statement (like in old Query analyzer) that can be edited and executed but not "real time" edited.

Is there any setting to get my beloved Assisted Editor back or Microsoft decided to get us rid of this user friendly addition?

Thanks and regards, Danko Jevtovic

The assisted editors functionality was cut from SQL Server 2005.

We had a lot of work left to make the feature correctly handle all the scenarios it needed to handle, and we ran out of time to fix it.

Saturday, February 25, 2012

assembly for stored procedure

I was playing around with the CLR in writing assemblies for the sql server 2005 stored procedure. I guess the example i found was for the beta version

This line is from the beta but no longer works. Any ideas what will fix this. There is no longer GetCommand property.

SqlCommand cmd =SqlContext.GetCommand();

Example

publicpartialclassStoredProcedures{[Microsoft.SqlServer.Server.SqlProcedure] publicstaticvoid StoredProcedure1()

{

// Put your code here

SqlCommand cmd =SqlContext.GetCommand();

cmd.CommandText="select firstname + ' ' + lastname + as [name] from person.contact";

SqlDataReader rdr = cmd.ExecuteReader();

SqlPipe sp =SqlContext.GetPipe();

sp.Send(rdr);

}};

Hi,

yes that has changed quite a bit till SQL 2005's RTM. Something like

using(SqlConnection connection = new SqlConnection("context connection=true"))
{

connection.Open();
SqlCommand cmd=new SqlCommand("select firstname + ' ' + lastname + as [name] from person.contact",connection);

SqlContext.Pipe.ExecuteAndSend(cmd);

}

For more information:http://msdn2.microsoft.com/en-us/library/ms190790.aspx

Monday, February 13, 2012

ASP.NET ReportViewer Problems

Hi,
I am using the web version of the ReportViewer control in a Visual
Studio 2005 Beta 2 project. We have an Oracle database, and SQL
Reporting Services. I have been using the ReportViewer in local mode
therefore.
But I have a problem with printing/output of reports. At the moment
the ReportViewer will only export to Excel, which is the only way to
get a report to print.
Is there a way to get a report to output all pages of a report at once
using the viewer. Then users could simply print the web page to print
out the report without having to export to Excel.
Is there something I am doing wrong? Is there a way to export a report
programmatically somehow? (Remembering I am using local mode. Should I
really be using the SQL Reporting Services server? If so can I using
the SQL 2005 Express tool?).
Thanks for any help,
Regards,
RichardSorry, I meant to say we have an Oracle database and *no* SQL Reporting
services.
Thanks,
Richard|||Now some time has passed, it would be worth trying the release version as it
has lots of improvements over the beta 2 version.

Asp.Net not finding the SQLServer for setting up Security problem

I have just reciently installed and started upgrading the last beta code to this beta and am having a problem conecting to my sqlinstance with the WebSite Configuration Tool.

The error indicates it is looking for a file in the app_data directory. (empty), but everthing else points to SQLServer (express) as being the issue.

I have run aspnet_regsql.exe (both on my default instance of sql (a sql2kas) and the beta2 instance that shipped with VS.

Both created datasases and eveyting looked good inside the db's.

However when I click the "Securtiy tab" I get a message "Unable to connect to SQL Server Database."

When I go to The Provider Tab, there is nothing to configure, just a test Hlink that generates the following when clicked.

SQLExpress database file auto-creation error:

The connection string specifies a local SQL Server Express instance using a database location within the applications App_Data directory. The provider attempted to automatically create the application services database because the provider determined that the database does not exist. The .......

I have run SQL Trace (profiler) against both instances of SQL when aps is trying to connect, but neither show anything.

I keep feeling like I must have missed something.. Anyu clues are welcome.

Rob

The issue was the Machine.Config file and the fact that when I named my new instance of SQL2005, I installed it using a NonDefault name.

This I fixed by editing the Machine.Config file and changing the Connection String for the Database Access. (Can't remember just which one, but if you do a search for SQLExpress in teh machine.config you will find it.)

HTH

Rob
Smile |||Here is another approach in using a full blown SQL Server as the repository of your credentials for ASP.NET 2.0 if you do not want to use the default SQL Express.

1) Create a database in SQL Server (2000 or 2005) and make sure that you give the ASPNET account permissions to this database.
2) Run the aspnet_regsql.exe file in your System%Root\Microsoft.NET\Framework\v2.0.xyz directory. This will open an ASP.NET SQL Server Setup Wizard which will create the objects necessary for ASP.NET security.
3) Point to the database you just created.
4) In your web.config file, locate the <connectionStrings> element and add the following:

<remove name="LocalSqlServer" />
<add name="LocalSqlServer" connectionString="Data Source=localhost;initial catalog=<your database name>;integrated security=true" providerName="System.Data.SqlClient">

This overrides the default SQL Express and points to the new database you just created - be it in the same machine or a different machine. You can also change the configuration in the machine.config file although this will affect every web application sitting on top of your machine.|||WOW! it did solve my problem. thanks so much|||

Worked !

Thanks a lot.

(I can now start growing my hair back )

Bill

|||

I have the same problem :S

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

i still get error

Error 4 XML document cannot contain multiple root level elements.

:S:S

|||

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

I think your error might be pointing to the Add tag as it is missing the Close Tag. However you seem to have an XML issue, not the issue that started the thread..

Rob

E.G. (highlighted in red)

|||Is it mandatory to have SQL Server for accessing the security features like creating users and roles in ASP.Net Configuration tool? If not please tell me the way to avoid the same problem...

Asp.Net not finding the SQLServer for setting up Security problem

I have just reciently installed and started upgrading the last beta code to this beta and am having a problem conecting to my sqlinstance with the WebSite Configuration Tool.

The error indicates it is looking for a file in the app_data directory. (empty), but everthing else points to SQLServer (express) as being the issue.

I have run aspnet_regsql.exe (both on my default instance of sql (a sql2kas) and the beta2 instance that shipped with VS.

Both created datasases and eveyting looked good inside the db's.

However when I click the "Securtiy tab" I get a message "Unable to connect to SQL Server Database."

When I go to The Provider Tab, there is nothing to configure, just a test Hlink that generates the following when clicked.

SQLExpress database file auto-creation error:

I have run SQL Trace (profiler) against both instances of SQL when aps is trying to connect, but neither show anything.

I keep feeling like I must have missed something.. Anyu clues are welcome.

Rob

The issue was the Machine.Config file and the fact that when I named my new instance of SQL2005, I installed it using a NonDefault name.

HTH

Rob
Smile |||Here is another approach in using a full blown SQL Server as the repository of your credentials for ASP.NET 2.0 if you do not want to use the default SQL Express.

Worked !

Thanks a lot.

(I can now start growing my hair back )

Bill

|||

I have the same problem :S

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

i still get error

Error 4 XML document cannot contain multiple root level elements.

:S:S

|||

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

I think your error might be pointing to the Add tag as it is missing the Close Tag. However you seem to have an XML issue, not the issue that started the thread..

Rob

E.G. (highlighted in red)

|||Is it mandatory to have SQL Server for accessing the security features like creating users and roles in ASP.Net Configuration tool? If not please tell me the way to avoid the same problem...

Asp.Net not finding the SQLServer for setting up Security problem

I have just reciently installed and started upgrading the last beta code to this beta and am having a problem conecting to my sqlinstance with the WebSite Configuration Tool.

The error indicates it is looking for a file in the app_data directory. (empty), but everthing else points to SQLServer (express) as being the issue.

I have run aspnet_regsql.exe (both on my default instance of sql (a sql2kas) and the beta2 instance that shipped with VS.

Both created datasases and eveyting looked good inside the db's.

However when I click the "Securtiy tab" I get a message "Unable to connect to SQL Server Database."

When I go to The Provider Tab, there is nothing to configure, just a test Hlink that generates the following when clicked.

SQLExpress database file auto-creation error:

I have run SQL Trace (profiler) against both instances of SQL when aps is trying to connect, but neither show anything.

I keep feeling like I must have missed something.. Anyu clues are welcome.

Rob

The issue was the Machine.Config file and the fact that when I named my new instance of SQL2005, I installed it using a NonDefault name.

HTH

Rob
Smile |||Here is another approach in using a full blown SQL Server as the repository of your credentials for ASP.NET 2.0 if you do not want to use the default SQL Express.

Worked !

Thanks a lot.

(I can now start growing my hair back )

Bill

|||

I have the same problem :S

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

i still get error

Error 4 XML document cannot contain multiple root level elements.

:S:S

|||

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

I think your error might be pointing to the Add tag as it is missing the Close Tag. However you seem to have an XML issue, not the issue that started the thread..

Rob

E.G. (highlighted in red)

|||Is it mandatory to have SQL Server for accessing the security features like creating users and roles in ASP.Net Configuration tool? If not please tell me the way to avoid the same problem...|||

Hi bass_player,

I think I was a bit late in getting this error, but when I got it in 2007 your post of 2005 saved my day.

Thanks a lot

RaghavS

|||hi
the first three steps done greatly
the fourth is not
i did not find any<connectionStrings> in my web.config

i'm just a beginer
thank u
|||

Place the <connectionstrings>...</connectionstrings> section right before the <system.web> seciton

Asp.Net not finding the SQLServer for setting up Security problem

I have just reciently installed and started upgrading the last beta code to this beta and am having a problem conecting to my sqlinstance with the WebSite Configuration Tool.

The error indicates it is looking for a file in the app_data directory. (empty), but everthing else points to SQLServer (express) as being the issue.

I have run aspnet_regsql.exe (both on my default instance of sql (a sql2kas) and the beta2 instance that shipped with VS.

Both created datasases and eveyting looked good inside the db's.

However when I click the "Securtiy tab" I get a message "Unable to connect to SQL Server Database."

When I go to The Provider Tab, there is nothing to configure, just a test Hlink that generates the following when clicked.

SQLExpress database file auto-creation error:

I have run SQL Trace (profiler) against both instances of SQL when aps is trying to connect, but neither show anything.

I keep feeling like I must have missed something.. Anyu clues are welcome.

Rob

The issue was the Machine.Config file and the fact that when I named my new instance of SQL2005, I installed it using a NonDefault name.

HTH

Rob
Smile |||Here is another approach in using a full blown SQL Server as the repository of your credentials for ASP.NET 2.0 if you do not want to use the default SQL Express.

Worked !

Thanks a lot.

(I can now start growing my hair back )

Bill

|||

I have the same problem :S

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

i still get error

Error 4 XML document cannot contain multiple root level elements.

:S:S

|||

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

I think your error might be pointing to the Add tag as it is missing the Close Tag. However you seem to have an XML issue, not the issue that started the thread..

Rob

E.G. (highlighted in red)

|||Is it mandatory to have SQL Server for accessing the security features like creating users and roles in ASP.Net Configuration tool? If not please tell me the way to avoid the same problem...|||

Hi bass_player,

I think I was a bit late in getting this error, but when I got it in 2007 your post of 2005 saved my day.

Thanks a lot

RaghavS

|||hi
the first three steps done greatly
the fourth is not
i did not find any <connectionStrings> in my web.config

i'm just a beginer
thank u
|||

Place the <connectionstrings>...</connectionstrings> section right before the <system.web> seciton

Asp.Net not finding the SQLServer for setting up Security problem

I have just reciently installed and started upgrading the last beta code to this beta and am having a problem conecting to my sqlinstance with the WebSite Configuration Tool.

The error indicates it is looking for a file in the app_data directory. (empty), but everthing else points to SQLServer (express) as being the issue.

I have run aspnet_regsql.exe (both on my default instance of sql (a sql2kas) and the beta2 instance that shipped with VS.

Both created datasases and eveyting looked good inside the db's.

However when I click the "Securtiy tab" I get a message "Unable to connect to SQL Server Database."

When I go to The Provider Tab, there is nothing to configure, just a test Hlink that generates the following when clicked.

SQLExpress database file auto-creation error:

I have run SQL Trace (profiler) against both instances of SQL when aps is trying to connect, but neither show anything.

I keep feeling like I must have missed something.. Anyu clues are welcome.

Rob

The issue was the Machine.Config file and the fact that when I named my new instance of SQL2005, I installed it using a NonDefault name.

HTH

Rob
Smile |||Here is another approach in using a full blown SQL Server as the repository of your credentials for ASP.NET 2.0 if you do not want to use the default SQL Express.

Worked !

Thanks a lot.

(I can now start growing my hair back )

Bill

|||

I have the same problem :S

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

i still get error

Error 4 XML document cannot contain multiple root level elements.

:S:S

|||

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

I think your error might be pointing to the Add tag as it is missing the Close Tag. However you seem to have an XML issue, not the issue that started the thread..

Rob

E.G. (highlighted in red)

|||Is it mandatory to have SQL Server for accessing the security features like creating users and roles in ASP.Net Configuration tool? If not please tell me the way to avoid the same problem...|||

Hi bass_player,

I think I was a bit late in getting this error, but when I got it in 2007 your post of 2005 saved my day.

Thanks a lot

RaghavS

|||hi
the first three steps done greatly
the fourth is not
i did not find any <connectionStrings> in my web.config

i'm just a beginer
thank u
|||

Place the <connectionstrings>...</connectionstrings> section right before the <system.web> seciton

Asp.Net not finding the SQLServer for setting up Security problem

I have just reciently installed and started upgrading the last beta code to this beta and am having a problem conecting to my sqlinstance with the WebSite Configuration Tool.

The error indicates it is looking for a file in the app_data directory. (empty), but everthing else points to SQLServer (express) as being the issue.

I have run aspnet_regsql.exe (both on my default instance of sql (a sql2kas) and the beta2 instance that shipped with VS.

Both created datasases and eveyting looked good inside the db's.

However when I click the "Securtiy tab" I get a message "Unable to connect to SQL Server Database."

When I go to The Provider Tab, there is nothing to configure, just a test Hlink that generates the following when clicked.

SQLExpress database file auto-creation error:

I have run SQL Trace (profiler) against both instances of SQL when aps is trying to connect, but neither show anything.

I keep feeling like I must have missed something.. Anyu clues are welcome.

Rob

The issue was the Machine.Config file and the fact that when I named my new instance of SQL2005, I installed it using a NonDefault name.

HTH

Rob
Smile |||Here is another approach in using a full blown SQL Server as the repository of your credentials for ASP.NET 2.0 if you do not want to use the default SQL Express.

Worked !

Thanks a lot.

(I can now start growing my hair back )

Bill

|||

I have the same problem :S

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

i still get error

Error 4 XML document cannot contain multiple root level elements.

:S:S

|||

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

I think your error might be pointing to the Add tag as it is missing the Close Tag. However you seem to have an XML issue, not the issue that started the thread..

Rob

E.G. (highlighted in red)

|||Is it mandatory to have SQL Server for accessing the security features like creating users and roles in ASP.Net Configuration tool? If not please tell me the way to avoid the same problem...

Asp.Net not finding the SQLServer for setting up Security problem

I have just reciently installed and started upgrading the last beta code to this beta and am having a problem conecting to my sqlinstance with the WebSite Configuration Tool.

The error indicates it is looking for a file in the app_data directory. (empty), but everthing else points to SQLServer (express) as being the issue.

I have run aspnet_regsql.exe (both on my default instance of sql (a sql2kas) and the beta2 instance that shipped with VS.

Both created datasases and eveyting looked good inside the db's.

However when I click the "Securtiy tab" I get a message "Unable to connect to SQL Server Database."

When I go to The Provider Tab, there is nothing to configure, just a test Hlink that generates the following when clicked.

SQLExpress database file auto-creation error:

I have run SQL Trace (profiler) against both instances of SQL when aps is trying to connect, but neither show anything.

I keep feeling like I must have missed something.. Anyu clues are welcome.

Rob

The issue was the Machine.Config file and the fact that when I named my new instance of SQL2005, I installed it using a NonDefault name.

HTH

Rob
Smile |||Here is another approach in using a full blown SQL Server as the repository of your credentials for ASP.NET 2.0 if you do not want to use the default SQL Express.

Worked !

Thanks a lot.

(I can now start growing my hair back )

Bill

|||

I have the same problem :S

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

i still get error

Error 4 XML document cannot contain multiple root level elements.

:S:S

|||

<add name ="LocalSqlServer" connectionString="Data Source=localhost;initial catalog = memberDB;

integrated security=true " providerName="System.Data.SqlClient">

</connectionStrings>

I think your error might be pointing to the Add tag as it is missing the Close Tag. However you seem to have an XML issue, not the issue that started the thread..

Rob

E.G. (highlighted in red)

|||Is it mandatory to have SQL Server for accessing the security features like creating users and roles in ASP.Net Configuration tool? If not please tell me the way to avoid the same problem...

Thursday, February 9, 2012

ASP.NET 1.1 and SQL Server 2005. Possible?

Hey,
I am starting to work on a project using ASP.NET. I am intending to useversion 1.1 cause version 2.0 is still Beta and not finalized yet. Iwas wondering if it is possible to use MS SQL Server 2005 with ASP.NET1.1. As far as I know the SQL Server 2005 requires ASP.NET 2.0. But Istill want to check if it is possible some how and if it was possible,will I find a server on the Internet that hosts SQL Server 2005 withASP.NET 1.1 cause till now all the companies I found provide onlyASP.NET 2.0 with SQL Server 2005.
[I don't actually know for sure but...]
Depends what you mean by "use" I guess. I'm sure it will respond to basic SQL Server requests at least as an OLEDB database, possibly as a SQL Server provider. However if you want to make use of any of the nice stuff then I doubt it very much.

Sunday, March 25, 2012

Attach Database

Attach Database

attach 2005 db on 2000

attach 2005 db on 2000

attach 2005 db on 2000

Monday, March 19, 2012

Assisted Editor for stored procedures

Saturday, February 25, 2012

assembly for stored procedure

Monday, February 13, 2012

ASP.NET ReportViewer Problems

Asp.Net not finding the SQLServer for setting up Security problem

Asp.Net not finding the SQLServer for setting up Security problem

Asp.Net not finding the SQLServer for setting up Security problem

Asp.Net not finding the SQLServer for setting up Security problem

Asp.Net not finding the SQLServer for setting up Security problem

Asp.Net not finding the SQLServer for setting up Security problem

Asp.Net not finding the SQLServer for setting up Security problem

Thursday, February 9, 2012

ASP.NET 1.1 and SQL Server 2005. Possible?

Asp.net / sql help

Blog Archive

About Me