Showing posts with label working. Show all posts
Showing posts with label working. Show all posts

Tuesday, March 27, 2012

Can't close IDE, modal dialog, anyone know what's causing this?

I've only seen this happen when using the report designer, and I think only
when working with Dundas chart properties. I don't have a modal dialog
open, or at least not that I can find. I use alt-esc to loop through the
dialogs on the OS, nothing. Microsoft has an entry in support, it says it
usually happens when I try to shut down and have left a modal dialog
open...only there is no dialog to close. I end up ending the IDE process
tree. Anyone else getting this and/or know the cause?
Microsoft Visual Studio cannot shut down because a modal dialog is active.
Close the active dialog and try again.
Yes it's Friday the 13th :)
Steve MunLeeuwhttp://geekswithblogs.net/geekusconlivus/archive/2006/02/28/70918.aspx
This is a lot better description, sorry for posting.
Steve MunLeeuw
"Steve MunLeeuw" <smunson@.clearwire.net> wrote in message
news:u6iO0Qy7GHA.940@.TK2MSFTNGP03.phx.gbl...
> I've only seen this happen when using the report designer, and I think
> only when working with Dundas chart properties. I don't have a modal
> dialog open, or at least not that I can find. I use alt-esc to loop
> through the dialogs on the OS, nothing. Microsoft has an entry in
> support, it says it usually happens when I try to shut down and have left
> a modal dialog open...only there is no dialog to close. I end up ending
> the IDE process tree. Anyone else getting this and/or know the cause?
> Microsoft Visual Studio cannot shut down because a modal dialog is active.
> Close the active dialog and try again.
> Yes it's Friday the 13th :)
> Steve MunLeeuw
>|||If I've been working with the code view of reports, my VS 2005 doesn't close
like normal. I usually have to close it by killing the DevEnv.exe service in
Task Manager...
Not a very elegant solution, but it will close. ;)
Kaisa M. Lindahl Lervik
"Steve MunLeeuw" <smunson@.clearwire.net> wrote in message
news:ekQn5Ty7GHA.3740@.TK2MSFTNGP05.phx.gbl...
> http://geekswithblogs.net/geekusconlivus/archive/2006/02/28/70918.aspx
> This is a lot better description, sorry for posting.
> Steve MunLeeuw
> "Steve MunLeeuw" <smunson@.clearwire.net> wrote in message
> news:u6iO0Qy7GHA.940@.TK2MSFTNGP03.phx.gbl...
>> I've only seen this happen when using the report designer, and I think
>> only when working with Dundas chart properties. I don't have a modal
>> dialog open, or at least not that I can find. I use alt-esc to loop
>> through the dialogs on the OS, nothing. Microsoft has an entry in
>> support, it says it usually happens when I try to shut down and have left
>> a modal dialog open...only there is no dialog to close. I end up ending
>> the IDE process tree. Anyone else getting this and/or know the cause?
>> Microsoft Visual Studio cannot shut down because a modal dialog is
>> active. Close the active dialog and try again.
>> Yes it's Friday the 13th :)
>> Steve MunLeeuw
>|||Kaisa M. Lindahl Lervik wrote:
> If I've been working with the code view of reports, my VS 2005 doesn't close
> like normal. I usually have to close it by killing the DevEnv.exe service in
> Task Manager...
> Not a very elegant solution, but it will close. ;)
> Kaisa M. Lindahl Lervik
>
> "Steve MunLeeuw" <smunson@.clearwire.net> wrote in message
> news:ekQn5Ty7GHA.3740@.TK2MSFTNGP05.phx.gbl...
> > http://geekswithblogs.net/geekusconlivus/archive/2006/02/28/70918.aspx
> >
> > This is a lot better description, sorry for posting.
> >
> > Steve MunLeeuw
> >
> > "Steve MunLeeuw" <smunson@.clearwire.net> wrote in message
> > news:u6iO0Qy7GHA.940@.TK2MSFTNGP03.phx.gbl...
> >> I've only seen this happen when using the report designer, and I think
> >> only when working with Dundas chart properties. I don't have a modal
> >> dialog open, or at least not that I can find. I use alt-esc to loop
> >> through the dialogs on the OS, nothing. Microsoft has an entry in
> >> support, it says it usually happens when I try to shut down and have left
> >> a modal dialog open...only there is no dialog to close. I end up ending
> >> the IDE process tree. Anyone else getting this and/or know the cause?
> >>
> >> Microsoft Visual Studio cannot shut down because a modal dialog is
> >> active. Close the active dialog and try again.
> >>
> >> Yes it's Friday the 13th :)
> >> Steve MunLeeuw
> >>
> >
> >
yes..this is happening to me quie a bit when writing a lot of reports
and changing a lot of charts...save soon save often....it looks like
the dundas dialogs and the vs dialogs get a bit confused...that is
all...
Peter
www.peternolan.com

Sunday, March 25, 2012

Can't attach to database

Hi,

I have a database that I developed using both Toad for SQL and SQL Server Managment Studio.

All was working fine. I could connect to the database with one of the above and also run two an applications I developed (one in C# and One in VB.NET using VS Express) using the standard SQLConnection class.

the following connection string worked fine...

Server="(local)"; Trusted_Connection="yes"; Database="CDEvolution";

Now, for one reason or another I decided to create a new data source in my Visual Studio project and pointed it to the database fine.

At first it seemed ok as I could see all tables from teh database. However somethign strage has happened. I now can't access the database in TOAD or SQL Server Managment Studio. I also couldn't connect using the above string.

I finally managed to get the two appllications I developed to access database using the following connection string...

Data Source=.\SQLEXPRESS;AttachDbFilename=C:\Program Files\Microsoft SQL Server\MSSQL\Data\CDEvolution.mdf;Integrated Security=True;Connect Timeout=6000;User Instance=True;

and the applications work fine, however I can access the database using the DB tools.

In SQL Server Managment Studio I remove the database and tried to attach it again but I keep getting the following error message...

Could not find row in sysindexes for database ID 5, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
Could not open new database 'C:\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL\DATA\CDEVOLUTION.MDF'. CREATE DATABASE is aborted. (.Net SqlClient Data Provider)

Any ideas on how I can get access back?

Cheers in advance,

Kevin

The latter error looks similar to what you get if you try to attach a SQL 2005 database to a SQL 2000 instance. SQL 2000 will not work with databases that have been upgraded to SQL 2005.|||

Hi,

Thanks for the response. before all this happened I was connecting to the database using SQL Manager Studio with no problems. This all started when I created a data source connection to the database in Visual Studio Express. After that I needed to change the connection string if I wanted to connect at run time using SQLConnection and have still not been able to connect using any of the DB managment tools.

Cheers,

Kevin

|||

This error is from SQL 2000, not SQL 2005, and incidates you are trying to attach a SQL 2005 database to SQL 2000.

Could not find row in sysindexes for database ID 5, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
Could not open new database 'C:\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL\DATA\CDEVOLUTION.MDF'. CREATE DATABASE is aborted. (.Net SqlClient Data Provider)

When you attached the databaes to Visual Studio Express, it would have been upgraded to SQL 2005 format and can no longer be used by SQL 2000.

|||

Thanks,

I was under the impression that SQL Express was 2005, I will look into it further and see what I can find.

Cheers,

Kevin.

|||

Sorted!

It seems that another instance of the SQL server has been created called SQLEXPRESS and you have the option to connect to it when the application starts.

Once I connected It created a new folder called MSSQL.1 (MSSQL already exists) so I simply coppied the database files into the new folder and attached them. So now I should be able to change to application to connect at the new location and I should be good to go.

Cheers,

YNWA

Kevin.

Can't attach database after server crash?

Hi...
I have a database I was working on a few months ago. The server it was on
crashed before I could get backups of it but I managed to get the original
database
file before anything happened to it. When the server was redone, the
usernames were changed a little and I now have a different windows username.
I wouldn't
think this would matter since the sql server uses windows security to sign
in anyways. Either way, I have tried to attach the database and I keep
getting
this error:
Attach database failed for Server 'ANDY\SQLEXPRESS'.
(Microsoft.SqlServer.Express.Smo)
Additional information:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.Express.ConnectionInfo)
The file "C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
compressed but does not reside in a read-only database or filegroup. The
file must be
decompressed.
Could not open new database 'EternityRecords'. CREATE DATABASE is aborted.
(Microsoft SQL
Server, Error: 5118)
Any ideas how to fix this? I suppose I can redo if I had to since there was
only 3 tables in there but it is annoying that I have to redo the whole
thing
anytime something small happens...> The file "C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
> compressed but does not reside in a read-only database or filegroup. The
> file must be
> decompressed.
NTFS compressed files on writable file groups are not supported, hence the
error.
Try decompressing the file. Navigate to the mdf file using Windows Explorer
and select Properties-->Advanced and uncheck the compress option. Same with
the log file (ldf).
Hope this helps.
Dan Guzman
SQL Server MVP
"Sunfire" <a_borka@.sbcglobal.net> wrote in message
news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
> Hi...
> I have a database I was working on a few months ago. The server it was on
> crashed before I could get backups of it but I managed to get the original
> database
> file before anything happened to it. When the server was redone, the
> usernames were changed a little and I now have a different windows
> username. I wouldn't
> think this would matter since the sql server uses windows security to sign
> in anyways. Either way, I have tried to attach the database and I keep
> getting
> this error:
> Attach database failed for Server 'ANDY\SQLEXPRESS'.
> (Microsoft.SqlServer.Express.Smo)
> Additional information:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.Express.ConnectionInfo)
> The file "C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
> compressed but does not reside in a read-only database or filegroup. The
> file must be
> decompressed.
> Could not open new database 'EternityRecords'. CREATE DATABASE is aborted.
> (Microsoft SQL
> Server, Error: 5118)
> Any ideas how to fix this? I suppose I can redo if I had to since there
> was only 3 tables in there but it is annoying that I have to redo the
> whole thing
> anytime something small happens...
>|||I will check it out and let you know what happens. You might have saved my
neck...
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
> NTFS compressed files on writable file groups are not supported, hence the
> error.
> Try decompressing the file. Navigate to the mdf file using Windows
> Explorer and select Properties-->Advanced and uncheck the compress option.
> Same with the log file (ldf).
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
> news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
>|||Hi... I tried your idea of unchecking the compress this file box in the
database file and its log file. I tried to attach it again and I get the
following message:
Attach database failed for Server 'ANDY\SQLEXPRESS'.
(Microsoft.SqlServer.Express.Smo)
Additional information:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.Express.ConnectionInfo)
One or more files do not match the primary file of the database. If you are
attempting to attach
a database, retry the operation with the correct files. If this is an
existing database, the file may
be corrupted and should be restored from a backup. (Microsoft SQL Server,
Error: 5173)
Does this mean I have to redo my database by hand? I don't have any backup
of it and I have no idea what is wrong now. Any ideas?
"Sunfire" <a_borka@.sbcglobal.net> wrote in message
news:ua7zYRA4HHA.600@.TK2MSFTNGP05.phx.gbl...
>I will check it out and let you know what happens. You might have saved my
>neck...
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
>|||You can try sp_attach_db and specify the path & file name for *all* the data
base files (mdf, ldf and
possibly ndf). If you are sure you got the path correct and still get some s
trange error, you are
most probably in trouble. Attaching is only supported if you did a clean det
ach first, if you
didn't, well, these things can happen.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Sunfire" <a_borka@.sbcglobal.net> wrote in message news:OiwlJjA4HHA.5740@.TK2MSFTNGP03.phx.gb
l...
> Hi... I tried your idea of unchecking the compress this file box in the da
tabase file and its log
> file. I tried to attach it again and I get the following message:
> Attach database failed for Server 'ANDY\SQLEXPRESS'. (Microsoft.SqlServer.
Express.Smo)
> Additional information:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.Express.ConnectionInfo)
> One or more files do not match the primary file of the database. If you ar
e attempting to attach
> a database, retry the operation with the correct files. If this is an exi
sting database, the file
> may
> be corrupted and should be restored from a backup. (Microsoft SQL Server,
Error: 5173)
> Does this mean I have to redo my database by hand? I don't have any backup
of it and I have no
> idea what is wrong now. Any ideas?
>
> "Sunfire" <a_borka@.sbcglobal.net> wrote in message news:ua7zYRA4HHA.600@.TK
2MSFTNGP05.phx.gbl...
>|||Guess it's back to the drawing board then...sigh... At least the DB wasn't
very huge...grin
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23Hx6l7B4HHA.5844@.TK2MSFTNGP02.phx.gbl...
> You can try sp_attach_db and specify the path & file name for *all* the
> database files (mdf, ldf and possibly ndf). If you are sure you got the
> path correct and still get some strange error, you are most probably in
> trouble. Attaching is only supported if you did a clean detach first, if
> you didn't, well, these things can happen.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
> news:OiwlJjA4HHA.5740@.TK2MSFTNGP03.phx.gbl...
>|||... and you now know to do your backups regularly... ;-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Sunfire" <a_borka@.sbcglobal.net> wrote in message news:%23V$7AlC4HHA.484@.TK2MSFTNGP06.phx.g
bl...
> Guess it's back to the drawing board then...sigh... At least the DB wasn't
> very huge...grin
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n
> message news:%23Hx6l7B4HHA.5844@.TK2MSFTNGP02.phx.gbl...
>

Can't attach database after server crash?

Hi...
I have a database I was working on a few months ago. The server it was on
crashed before I could get backups of it but I managed to get the original
database
file before anything happened to it. When the server was redone, the
usernames were changed a little and I now have a different windows username.
I wouldn't
think this would matter since the sql server uses windows security to sign
in anyways. Either way, I have tried to attach the database and I keep
getting
this error:
Attach database failed for Server 'ANDY\SQLEXPRESS'.
(Microsoft.SqlServer.Express.Smo)
Additional information:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.Express.ConnectionInfo)
The file "C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
compressed but does not reside in a read-only database or filegroup. The
file must be
decompressed.
Could not open new database 'EternityRecords'. CREATE DATABASE is aborted.
(Microsoft SQL
Server, Error: 5118)
Any ideas how to fix this? I suppose I can redo if I had to since there was
only 3 tables in there but it is annoying that I have to redo the whole
thing
anytime something small happens...> The file "C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
> compressed but does not reside in a read-only database or filegroup. The
> file must be
> decompressed.
NTFS compressed files on writable file groups are not supported, hence the
error.
Try decompressing the file. Navigate to the mdf file using Windows Explorer
and select Properties-->Advanced and uncheck the compress option. Same with
the log file (ldf).
Hope this helps.
Dan Guzman
SQL Server MVP
"Sunfire" <a_borka@.sbcglobal.net> wrote in message
news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
> Hi...
> I have a database I was working on a few months ago. The server it was on
> crashed before I could get backups of it but I managed to get the original
> database
> file before anything happened to it. When the server was redone, the
> usernames were changed a little and I now have a different windows
> username. I wouldn't
> think this would matter since the sql server uses windows security to sign
> in anyways. Either way, I have tried to attach the database and I keep
> getting
> this error:
> Attach database failed for Server 'ANDY\SQLEXPRESS'.
> (Microsoft.SqlServer.Express.Smo)
> Additional information:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.Express.ConnectionInfo)
> The file "C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
> compressed but does not reside in a read-only database or filegroup. The
> file must be
> decompressed.
> Could not open new database 'EternityRecords'. CREATE DATABASE is aborted.
> (Microsoft SQL
> Server, Error: 5118)
> Any ideas how to fix this? I suppose I can redo if I had to since there
> was only 3 tables in there but it is annoying that I have to redo the
> whole thing
> anytime something small happens...
>|||I will check it out and let you know what happens. You might have saved my
neck...
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup. The
>> file must be
>> decompressed.
> NTFS compressed files on writable file groups are not supported, hence the
> error.
> Try decompressing the file. Navigate to the mdf file using Windows
> Explorer and select Properties-->Advanced and uncheck the compress option.
> Same with the log file (ldf).
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
> news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
>> Hi...
>> I have a database I was working on a few months ago. The server it was on
>> crashed before I could get backups of it but I managed to get the
>> original database
>> file before anything happened to it. When the server was redone, the
>> usernames were changed a little and I now have a different windows
>> username. I wouldn't
>> think this would matter since the sql server uses windows security to
>> sign in anyways. Either way, I have tried to attach the database and I
>> keep getting
>> this error:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'.
>> (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup. The
>> file must be
>> decompressed.
>> Could not open new database 'EternityRecords'. CREATE DATABASE is
>> aborted. (Microsoft SQL
>> Server, Error: 5118)
>> Any ideas how to fix this? I suppose I can redo if I had to since there
>> was only 3 tables in there but it is annoying that I have to redo the
>> whole thing
>> anytime something small happens...
>>
>|||Hi... I tried your idea of unchecking the compress this file box in the
database file and its log file. I tried to attach it again and I get the
following message:
Attach database failed for Server 'ANDY\SQLEXPRESS'.
(Microsoft.SqlServer.Express.Smo)
Additional information:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.Express.ConnectionInfo)
One or more files do not match the primary file of the database. If you are
attempting to attach
a database, retry the operation with the correct files. If this is an
existing database, the file may
be corrupted and should be restored from a backup. (Microsoft SQL Server,
Error: 5173)
Does this mean I have to redo my database by hand? I don't have any backup
of it and I have no idea what is wrong now. Any ideas?
"Sunfire" <a_borka@.sbcglobal.net> wrote in message
news:ua7zYRA4HHA.600@.TK2MSFTNGP05.phx.gbl...
>I will check it out and let you know what happens. You might have saved my
>neck...
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup. The
>> file must be
>> decompressed.
>> NTFS compressed files on writable file groups are not supported, hence
>> the error.
>> Try decompressing the file. Navigate to the mdf file using Windows
>> Explorer and select Properties-->Advanced and uncheck the compress
>> option. Same with the log file (ldf).
>>
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
>> news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
>> Hi...
>> I have a database I was working on a few months ago. The server it was
>> on crashed before I could get backups of it but I managed to get the
>> original database
>> file before anything happened to it. When the server was redone, the
>> usernames were changed a little and I now have a different windows
>> username. I wouldn't
>> think this would matter since the sql server uses windows security to
>> sign in anyways. Either way, I have tried to attach the database and I
>> keep getting
>> this error:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'.
>> (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup. The
>> file must be
>> decompressed.
>> Could not open new database 'EternityRecords'. CREATE DATABASE is
>> aborted. (Microsoft SQL
>> Server, Error: 5118)
>> Any ideas how to fix this? I suppose I can redo if I had to since there
>> was only 3 tables in there but it is annoying that I have to redo the
>> whole thing
>> anytime something small happens...
>>
>|||You can try sp_attach_db and specify the path & file name for *all* the database files (mdf, ldf and
possibly ndf). If you are sure you got the path correct and still get some strange error, you are
most probably in trouble. Attaching is only supported if you did a clean detach first, if you
didn't, well, these things can happen.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Sunfire" <a_borka@.sbcglobal.net> wrote in message news:OiwlJjA4HHA.5740@.TK2MSFTNGP03.phx.gbl...
> Hi... I tried your idea of unchecking the compress this file box in the database file and its log
> file. I tried to attach it again and I get the following message:
> Attach database failed for Server 'ANDY\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)
> Additional information:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.Express.ConnectionInfo)
> One or more files do not match the primary file of the database. If you are attempting to attach
> a database, retry the operation with the correct files. If this is an existing database, the file
> may
> be corrupted and should be restored from a backup. (Microsoft SQL Server, Error: 5173)
> Does this mean I have to redo my database by hand? I don't have any backup of it and I have no
> idea what is wrong now. Any ideas?
>
> "Sunfire" <a_borka@.sbcglobal.net> wrote in message news:ua7zYRA4HHA.600@.TK2MSFTNGP05.phx.gbl...
>>I will check it out and let you know what happens. You might have saved my neck...
>>
>> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
>> news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
>> The file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup. The file must be
>> decompressed.
>> NTFS compressed files on writable file groups are not supported, hence the error.
>> Try decompressing the file. Navigate to the mdf file using Windows Explorer and select
>> Properties-->Advanced and uncheck the compress option. Same with the log file (ldf).
>>
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
>> Hi...
>> I have a database I was working on a few months ago. The server it was on crashed before I
>> could get backups of it but I managed to get the original database
>> file before anything happened to it. When the server was redone, the usernames were changed a
>> little and I now have a different windows username. I wouldn't
>> think this would matter since the sql server uses windows security to sign in anyways. Either
>> way, I have tried to attach the database and I keep getting
>> this error:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> The file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup. The file must be
>> decompressed.
>> Could not open new database 'EternityRecords'. CREATE DATABASE is aborted. (Microsoft SQL
>> Server, Error: 5118)
>> Any ideas how to fix this? I suppose I can redo if I had to since there was only 3 tables in
>> there but it is annoying that I have to redo the whole thing
>> anytime something small happens...
>>
>>
>|||Guess it's back to the drawing board then...sigh... At least the DB wasn't
very huge...grin
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23Hx6l7B4HHA.5844@.TK2MSFTNGP02.phx.gbl...
> You can try sp_attach_db and specify the path & file name for *all* the
> database files (mdf, ldf and possibly ndf). If you are sure you got the
> path correct and still get some strange error, you are most probably in
> trouble. Attaching is only supported if you did a clean detach first, if
> you didn't, well, these things can happen.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
> news:OiwlJjA4HHA.5740@.TK2MSFTNGP03.phx.gbl...
>> Hi... I tried your idea of unchecking the compress this file box in the
>> database file and its log file. I tried to attach it again and I get the
>> following message:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'.
>> (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> One or more files do not match the primary file of the database. If you
>> are attempting to attach
>> a database, retry the operation with the correct files. If this is an
>> existing database, the file may
>> be corrupted and should be restored from a backup. (Microsoft SQL Server,
>> Error: 5173)
>> Does this mean I have to redo my database by hand? I don't have any
>> backup of it and I have no idea what is wrong now. Any ideas?
>>
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
>> news:ua7zYRA4HHA.600@.TK2MSFTNGP05.phx.gbl...
>>I will check it out and let you know what happens. You might have saved
>>my neck...
>>
>> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
>> news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup.
>> The file must be
>> decompressed.
>> NTFS compressed files on writable file groups are not supported, hence
>> the error.
>> Try decompressing the file. Navigate to the mdf file using Windows
>> Explorer and select Properties-->Advanced and uncheck the compress
>> option. Same with the log file (ldf).
>>
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
>> news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
>> Hi...
>> I have a database I was working on a few months ago. The server it was
>> on crashed before I could get backups of it but I managed to get the
>> original database
>> file before anything happened to it. When the server was redone, the
>> usernames were changed a little and I now have a different windows
>> username. I wouldn't
>> think this would matter since the sql server uses windows security to
>> sign in anyways. Either way, I have tried to attach the database and I
>> keep getting
>> this error:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'.
>> (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or
>> batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup.
>> The file must be
>> decompressed.
>> Could not open new database 'EternityRecords'. CREATE DATABASE is
>> aborted. (Microsoft SQL
>> Server, Error: 5118)
>> Any ideas how to fix this? I suppose I can redo if I had to since
>> there was only 3 tables in there but it is annoying that I have to
>> redo the whole thing
>> anytime something small happens...
>>
>>
>>
>|||... and you now know to do your backups regularly... ;-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Sunfire" <a_borka@.sbcglobal.net> wrote in message news:%23V$7AlC4HHA.484@.TK2MSFTNGP06.phx.gbl...
> Guess it's back to the drawing board then...sigh... At least the DB wasn't
> very huge...grin
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:%23Hx6l7B4HHA.5844@.TK2MSFTNGP02.phx.gbl...
>> You can try sp_attach_db and specify the path & file name for *all* the
>> database files (mdf, ldf and possibly ndf). If you are sure you got the
>> path correct and still get some strange error, you are most probably in
>> trouble. Attaching is only supported if you did a clean detach first, if
>> you didn't, well, these things can happen.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
>> news:OiwlJjA4HHA.5740@.TK2MSFTNGP03.phx.gbl...
>> Hi... I tried your idea of unchecking the compress this file box in the
>> database file and its log file. I tried to attach it again and I get the
>> following message:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'.
>> (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> One or more files do not match the primary file of the database. If you
>> are attempting to attach
>> a database, retry the operation with the correct files. If this is an
>> existing database, the file may
>> be corrupted and should be restored from a backup. (Microsoft SQL Server,
>> Error: 5173)
>> Does this mean I have to redo my database by hand? I don't have any
>> backup of it and I have no idea what is wrong now. Any ideas?
>>
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
>> news:ua7zYRA4HHA.600@.TK2MSFTNGP05.phx.gbl...
>>I will check it out and let you know what happens. You might have saved
>>my neck...
>>
>> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
>> news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup.
>> The file must be
>> decompressed.
>> NTFS compressed files on writable file groups are not supported, hence
>> the error.
>> Try decompressing the file. Navigate to the mdf file using Windows
>> Explorer and select Properties-->Advanced and uncheck the compress
>> option. Same with the log file (ldf).
>>
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
>> news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
>> Hi...
>> I have a database I was working on a few months ago. The server it was
>> on crashed before I could get backups of it but I managed to get the
>> original database
>> file before anything happened to it. When the server was redone, the
>> usernames were changed a little and I now have a different windows
>> username. I wouldn't
>> think this would matter since the sql server uses windows security to
>> sign in anyways. Either way, I have tried to attach the database and I
>> keep getting
>> this error:
>> Attach database failed for Server 'ANDY\SQLEXPRESS'.
>> (Microsoft.SqlServer.Express.Smo)
>> Additional information:
>> An exception occurred while executing a Transact-SQL statement or
>> batch.
>> (Microsoft.SqlServer.Express.ConnectionInfo)
>> The file "C:\Program Files\Microsoft SQL
>> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
>> compressed but does not reside in a read-only database or filegroup.
>> The file must be
>> decompressed.
>> Could not open new database 'EternityRecords'. CREATE DATABASE is
>> aborted. (Microsoft SQL
>> Server, Error: 5118)
>> Any ideas how to fix this? I suppose I can redo if I had to since
>> there was only 3 tables in there but it is annoying that I have to
>> redo the whole thing
>> anytime something small happens...
>>
>>
>>
>>
>sql

Can't attach database after server crash?

Hi...
I have a database I was working on a few months ago. The server it was on
crashed before I could get backups of it but I managed to get the original
database
file before anything happened to it. When the server was redone, the
usernames were changed a little and I now have a different windows username.
I wouldn't
think this would matter since the sql server uses windows security to sign
in anyways. Either way, I have tried to attach the database and I keep
getting
this error:
Attach database failed for Server 'ANDY\SQLEXPRESS'.
(Microsoft.SqlServer.Express.Smo)
Additional information:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.Express.ConnectionInfo)
The file "C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
compressed but does not reside in a read-only database or filegroup. The
file must be
decompressed.
Could not open new database 'EternityRecords'. CREATE DATABASE is aborted.
(Microsoft SQL
Server, Error: 5118)
Any ideas how to fix this? I suppose I can redo if I had to since there was
only 3 tables in there but it is annoying that I have to redo the whole
thing
anytime something small happens...
> The file "C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
> compressed but does not reside in a read-only database or filegroup. The
> file must be
> decompressed.
NTFS compressed files on writable file groups are not supported, hence the
error.
Try decompressing the file. Navigate to the mdf file using Windows Explorer
and select Properties-->Advanced and uncheck the compress option. Same with
the log file (ldf).
Hope this helps.
Dan Guzman
SQL Server MVP
"Sunfire" <a_borka@.sbcglobal.net> wrote in message
news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
> Hi...
> I have a database I was working on a few months ago. The server it was on
> crashed before I could get backups of it but I managed to get the original
> database
> file before anything happened to it. When the server was redone, the
> usernames were changed a little and I now have a different windows
> username. I wouldn't
> think this would matter since the sql server uses windows security to sign
> in anyways. Either way, I have tried to attach the database and I keep
> getting
> this error:
> Attach database failed for Server 'ANDY\SQLEXPRESS'.
> (Microsoft.SqlServer.Express.Smo)
> Additional information:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.Express.ConnectionInfo)
> The file "C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\EternityRecords.mdf" is
> compressed but does not reside in a read-only database or filegroup. The
> file must be
> decompressed.
> Could not open new database 'EternityRecords'. CREATE DATABASE is aborted.
> (Microsoft SQL
> Server, Error: 5118)
> Any ideas how to fix this? I suppose I can redo if I had to since there
> was only 3 tables in there but it is annoying that I have to redo the
> whole thing
> anytime something small happens...
>
|||I will check it out and let you know what happens. You might have saved my
neck...
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
> NTFS compressed files on writable file groups are not supported, hence the
> error.
> Try decompressing the file. Navigate to the mdf file using Windows
> Explorer and select Properties-->Advanced and uncheck the compress option.
> Same with the log file (ldf).
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
> news:uiWHH6$3HHA.4672@.TK2MSFTNGP05.phx.gbl...
>
|||Hi... I tried your idea of unchecking the compress this file box in the
database file and its log file. I tried to attach it again and I get the
following message:
Attach database failed for Server 'ANDY\SQLEXPRESS'.
(Microsoft.SqlServer.Express.Smo)
Additional information:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.Express.ConnectionInfo)
One or more files do not match the primary file of the database. If you are
attempting to attach
a database, retry the operation with the correct files. If this is an
existing database, the file may
be corrupted and should be restored from a backup. (Microsoft SQL Server,
Error: 5173)
Does this mean I have to redo my database by hand? I don't have any backup
of it and I have no idea what is wrong now. Any ideas?
"Sunfire" <a_borka@.sbcglobal.net> wrote in message
news:ua7zYRA4HHA.600@.TK2MSFTNGP05.phx.gbl...
>I will check it out and let you know what happens. You might have saved my
>neck...
>
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:OZCATAA4HHA.5724@.TK2MSFTNGP05.phx.gbl...
>
|||You can try sp_attach_db and specify the path & file name for *all* the database files (mdf, ldf and
possibly ndf). If you are sure you got the path correct and still get some strange error, you are
most probably in trouble. Attaching is only supported if you did a clean detach first, if you
didn't, well, these things can happen.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Sunfire" <a_borka@.sbcglobal.net> wrote in message news:OiwlJjA4HHA.5740@.TK2MSFTNGP03.phx.gbl...
> Hi... I tried your idea of unchecking the compress this file box in the database file and its log
> file. I tried to attach it again and I get the following message:
> Attach database failed for Server 'ANDY\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)
> Additional information:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.Express.ConnectionInfo)
> One or more files do not match the primary file of the database. If you are attempting to attach
> a database, retry the operation with the correct files. If this is an existing database, the file
> may
> be corrupted and should be restored from a backup. (Microsoft SQL Server, Error: 5173)
> Does this mean I have to redo my database by hand? I don't have any backup of it and I have no
> idea what is wrong now. Any ideas?
>
> "Sunfire" <a_borka@.sbcglobal.net> wrote in message news:ua7zYRA4HHA.600@.TK2MSFTNGP05.phx.gbl...
>
|||Guess it's back to the drawing board then...sigh... At least the DB wasn't
very huge...grin
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23Hx6l7B4HHA.5844@.TK2MSFTNGP02.phx.gbl...
> You can try sp_attach_db and specify the path & file name for *all* the
> database files (mdf, ldf and possibly ndf). If you are sure you got the
> path correct and still get some strange error, you are most probably in
> trouble. Attaching is only supported if you did a clean detach first, if
> you didn't, well, these things can happen.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Sunfire" <a_borka@.sbcglobal.net> wrote in message
> news:OiwlJjA4HHA.5740@.TK2MSFTNGP03.phx.gbl...
>
|||... and you now know to do your backups regularly... ;-)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Sunfire" <a_borka@.sbcglobal.net> wrote in message news:%23V$7AlC4HHA.484@.TK2MSFTNGP06.phx.gbl...
> Guess it's back to the drawing board then...sigh... At least the DB wasn't
> very huge...grin
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:%23Hx6l7B4HHA.5844@.TK2MSFTNGP02.phx.gbl...
>

Can't assign connection manager object to DataReader Source

I'm trying to create a DataReader source object using a working ADO.NET Oracle Client connection object that exists in the connection manager.

Problem:

When I open the editor the DataReaderSrc component shows only one row under the Connection Managers tab:

Name=IDbConnection
Connection Manager=blank
Description=Managed connection manager

I cannot assign the ADO.NET connection (or any connections). I see a warning at the bottom of the Connection Managers tab:

"Not all connection managers have been set. Set all connection managers."

When I click refresh the warning message changes to:

"The runtime connection manager with the ID "" cannot be found. Verify that the connection manager collection has a connection manager with that ID."

I am prevented from removing the IDbConnection or assigning my Connection Manager object to the DataReader Source.

Thanks, -- Mike

I also have the same problem, I'm sure it must be some tiny detail somewhere / something very basic, but I have been unable to fix it. Can someone help? Thanks!

Hector

|||

I had the same problem because I was using the wrong Provider when specifying my Data Source.

Hope it helps,

Nuno

|||

I had the same problem. In my case the 'advanced editor for datareader source' is very, very confusing. First of all, you have to create a connection manager, which I did already. But, it was not at all intuitive that you have to click on the box under 'connection manager' and select a connection manager. By default the box is black and grayed out like both the other fields which you cannot change. Gee, thanks redmond.

|||Thanks for taking the time to post this answer. I finally learned this last week at a SQL Server training class. The instructor pointed out that you actually need to change the disabled looking box.|||

Hello.

I read that you found a solution, but I didn't understand it very well.

Could you tell me more how to resolve this problem. I have create the connection manager and a cant set it into the DataReader Source

Thank you.

|||

Data Reader source accepts connection manager of Type ADO.NET only.

so First you have to create a Connection Manager to your Data Base using ADO.net Provider ONLY.

open the advanced editior of data reader source, go to connection managers tab, you will see IdbConnection , beside that there will be another column named connection manger, select your created connection manager there (ADO.Net one). Then go to Component properties tab and in sql command enter your sql query. go to columns mapping tab ..now you can see your columns.

|||thank you for your reply. i resolve the problem.|||

hello,

i thought that I resolve the problem of the connection but there was another problem that didn't permit me to save the connection to the advanced editor.

the error is "Component is already connected. The component needs to be disconnected before attempting to connect it."

Can you help me?

Can't assign connection manager object to DataReader Source

I'm trying to create a DataReader source object using a working ADO.NET Oracle Client connection object that exists in the connection manager.

Problem:

When I open the editor the DataReaderSrc component shows only one row under the Connection Managers tab:

Name=IDbConnection
Connection Manager=blank
Description=Managed connection manager

I cannot assign the ADO.NET connection (or any connections). I see a warning at the bottom of the Connection Managers tab:

"Not all connection managers have been set. Set all connection managers."

When I click refresh the warning message changes to:

"The runtime connection manager with the ID "" cannot be found. Verify that the connection manager collection has a connection manager with that ID."

I am prevented from removing the IDbConnection or assigning my Connection Manager object to the DataReader Source.

Thanks, -- Mike

I also have the same problem, I'm sure it must be some tiny detail somewhere / something very basic, but I have been unable to fix it. Can someone help? Thanks!

Hector

|||

I had the same problem because I was using the wrong Provider when specifying my Data Source.

Hope it helps,

Nuno

|||

I had the same problem. In my case the 'advanced editor for datareader source' is very, very confusing. First of all, you have to create a connection manager, which I did already. But, it was not at all intuitive that you have to click on the box under 'connection manager' and select a connection manager. By default the box is black and grayed out like both the other fields which you cannot change. Gee, thanks redmond.

|||Thanks for taking the time to post this answer. I finally learned this last week at a SQL Server training class. The instructor pointed out that you actually need to change the disabled looking box.|||

Hello.

I read that you found a solution, but I didn't understand it very well.

Could you tell me more how to resolve this problem. I have create the connection manager and a cant set it into the DataReader Source

Thank you.

|||

Data Reader source accepts connection manager of Type ADO.NET only.

so First you have to create a Connection Manager to your Data Base using ADO.net Provider ONLY.

open the advanced editior of data reader source, go to connection managers tab, you will see IdbConnection , beside that there will be another column named connection manger, select your created connection manager there (ADO.Net one). Then go to Component properties tab and in sql command enter your sql query. go to columns mapping tab ..now you can see your columns.

|||thank you for your reply. i resolve the problem.|||

hello,

i thought that I resolve the problem of the connection but there was another problem that didn't permit me to save the connection to the advanced editor.

the error is "Component is already connected. The component needs to be disconnected before attempting to connect it."

Can you help me?

Can't assign connection manager object to DataReader Source

I'm trying to create a DataReader source object using a working ADO.NET Oracle Client connection object that exists in the connection manager.

Problem:

When I open the editor the DataReaderSrc component shows only one row under the Connection Managers tab:

Name=IDbConnection
Connection Manager=blank
Description=Managed connection manager

I cannot assign the ADO.NET connection (or any connections). I see a warning at the bottom of the Connection Managers tab:

"Not all connection managers have been set. Set all connection managers."

When I click refresh the warning message changes to:

"The runtime connection manager with the ID "" cannot be found. Verify that the connection manager collection has a connection manager with that ID."

I am prevented from removing the IDbConnection or assigning my Connection Manager object to the DataReader Source.

Thanks, -- Mike

I also have the same problem, I'm sure it must be some tiny detail somewhere / something very basic, but I have been unable to fix it. Can someone help? Thanks!

Hector

|||

I had the same problem because I was using the wrong Provider when specifying my Data Source.

Hope it helps,

Nuno

|||

I had the same problem. In my case the 'advanced editor for datareader source' is very, very confusing. First of all, you have to create a connection manager, which I did already. But, it was not at all intuitive that you have to click on the box under 'connection manager' and select a connection manager. By default the box is black and grayed out like both the other fields which you cannot change. Gee, thanks redmond.

|||Thanks for taking the time to post this answer. I finally learned this last week at a SQL Server training class. The instructor pointed out that you actually need to change the disabled looking box.|||

Hello.

I read that you found a solution, but I didn't understand it very well.

Could you tell me more how to resolve this problem. I have create the connection manager and a cant set it into the DataReader Source

Thank you.

|||

Data Reader source accepts connection manager of Type ADO.NET only.

so First you have to create a Connection Manager to your Data Base using ADO.net Provider ONLY.

open the advanced editior of data reader source, go to connection managers tab, you will see IdbConnection , beside that there will be another column named connection manger, select your created connection manager there (ADO.Net one). Then go to Component properties tab and in sql command enter your sql query. go to columns mapping tab ..now you can see your columns.

|||thank you for your reply. i resolve the problem.|||

hello,

i thought that I resolve the problem of the connection but there was another problem that didn't permit me to save the connection to the advanced editor.

the error is "Component is already connected. The component needs to be disconnected before attempting to connect it."

Can you help me?

Can't assign connection manager object to DataReader Source

I'm trying to create a DataReader source object using a working ADO.NET Oracle Client connection object that exists in the connection manager.

Problem:

When I open the editor the DataReaderSrc component shows only one row under the Connection Managers tab:

Name=IDbConnection
Connection Manager=blank
Description=Managed connection manager

I cannot assign the ADO.NET connection (or any connections). I see a warning at the bottom of the Connection Managers tab:

"Not all connection managers have been set. Set all connection managers."

When I click refresh the warning message changes to:

"The runtime connection manager with the ID "" cannot be found. Verify that the connection manager collection has a connection manager with that ID."

I am prevented from removing the IDbConnection or assigning my Connection Manager object to the DataReader Source.

Thanks, -- Mike

I also have the same problem, I'm sure it must be some tiny detail somewhere / something very basic, but I have been unable to fix it. Can someone help? Thanks!

Hector

|||

I had the same problem because I was using the wrong Provider when specifying my Data Source.

Hope it helps,

Nuno

|||

I had the same problem. In my case the 'advanced editor for datareader source' is very, very confusing. First of all, you have to create a connection manager, which I did already. But, it was not at all intuitive that you have to click on the box under 'connection manager' and select a connection manager. By default the box is black and grayed out like both the other fields which you cannot change. Gee, thanks redmond.

|||Thanks for taking the time to post this answer. I finally learned this last week at a SQL Server training class. The instructor pointed out that you actually need to change the disabled looking box.|||

Hello.

I read that you found a solution, but I didn't understand it very well.

Could you tell me more how to resolve this problem. I have create the connection manager and a cant set it into the DataReader Source

Thank you.

|||

Data Reader source accepts connection manager of Type ADO.NET only.

so First you have to create a Connection Manager to your Data Base using ADO.net Provider ONLY.

open the advanced editior of data reader source, go to connection managers tab, you will see IdbConnection , beside that there will be another column named connection manger, select your created connection manager there (ADO.Net one). Then go to Component properties tab and in sql command enter your sql query. go to columns mapping tab ..now you can see your columns.

|||thank you for your reply. i resolve the problem.|||

hello,

i thought that I resolve the problem of the connection but there was another problem that didn't permit me to save the connection to the advanced editor.

the error is "Component is already connected. The component needs to be disconnected before attempting to connect it."

Can you help me?

Can't assign connection manager object to DataReader Source

I'm trying to create a DataReader source object using a working ADO.NET Oracle Client connection object that exists in the connection manager.

Problem:

When I open the editor the DataReaderSrc component shows only one row under the Connection Managers tab:

Name=IDbConnection
Connection Manager=blank
Description=Managed connection manager

I cannot assign the ADO.NET connection (or any connections). I see a warning at the bottom of the Connection Managers tab:

"Not all connection managers have been set. Set all connection managers."

When I click refresh the warning message changes to:

"The runtime connection manager with the ID "" cannot be found. Verify that the connection manager collection has a connection manager with that ID."

I am prevented from removing the IDbConnection or assigning my Connection Manager object to the DataReader Source.

Thanks, -- Mike

I also have the same problem, I'm sure it must be some tiny detail somewhere / something very basic, but I have been unable to fix it. Can someone help? Thanks!

Hector

|||

I had the same problem because I was using the wrong Provider when specifying my Data Source.

Hope it helps,

Nuno

|||

I had the same problem. In my case the 'advanced editor for datareader source' is very, very confusing. First of all, you have to create a connection manager, which I did already. But, it was not at all intuitive that you have to click on the box under 'connection manager' and select a connection manager. By default the box is black and grayed out like both the other fields which you cannot change. Gee, thanks redmond.

|||Thanks for taking the time to post this answer. I finally learned this last week at a SQL Server training class. The instructor pointed out that you actually need to change the disabled looking box.|||

Hello.

I read that you found a solution, but I didn't understand it very well.

Could you tell me more how to resolve this problem. I have create the connection manager and a cant set it into the DataReader Source

Thank you.

|||

Data Reader source accepts connection manager of Type ADO.NET only.

so First you have to create a Connection Manager to your Data Base using ADO.net Provider ONLY.

open the advanced editior of data reader source, go to connection managers tab, you will see IdbConnection , beside that there will be another column named connection manger, select your created connection manager there (ADO.Net one). Then go to Component properties tab and in sql command enter your sql query. go to columns mapping tab ..now you can see your columns.

|||thank you for your reply. i resolve the problem.|||

hello,

i thought that I resolve the problem of the connection but there was another problem that didn't permit me to save the connection to the advanced editor.

the error is "Component is already connected. The component needs to be disconnected before attempting to connect it."

Can you help me?

sql

Tuesday, March 20, 2012

can't access report through report manager...

Here is what is happening.
I have a working project PROG created using VS.Net. I create a new
project for reports RPTPROJ under PROJ.
I create several reports RPT1.RDL, RPT2.RDL under the new project
RPTPROJ.
Now I start the REPORT MANAGER and create a new folder (MYREPORTS) and
upload all my reports (RDLs) into this new folder. Now when I click on
any of the reports from here, it doesn't show up. Only shows up an
"Action Canceled" message.
Here is the URL, it generates for one of the reports:
http://localhost/Reports/Pages/Report.aspx?ItemPath=%2fRPTPROJ%2fRPT1
But when I goto,
http://localhost/reportserver?%2fPROJ%2fRPTPROJ
I can see all my reports and run them.
Please can someone explain what I should do to run them from the
report manager?
ThanksWhen you publish to the report server in Report Designer, in the project
properties dialog (where you set your URL to the report server), there is a
target folder property. Set that to MYREPORTS. By default it is the
project name, which is why you're getting link s containing /RPTPROJ/RPT1
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Roy" <nroy@.iastate.edu> wrote in message
news:ad20302f.0408091310.6e20c373@.posting.google.com...
> Here is what is happening.
> I have a working project PROG created using VS.Net. I create a new
> project for reports RPTPROJ under PROJ.
> I create several reports RPT1.RDL, RPT2.RDL under the new project
> RPTPROJ.
> Now I start the REPORT MANAGER and create a new folder (MYREPORTS) and
> upload all my reports (RDLs) into this new folder. Now when I click on
> any of the reports from here, it doesn't show up. Only shows up an
> "Action Canceled" message.
> Here is the URL, it generates for one of the reports:
> http://localhost/Reports/Pages/Report.aspx?ItemPath=%2fRPTPROJ%2fRPT1
> But when I goto,
> http://localhost/reportserver?%2fPROJ%2fRPTPROJ
> I can see all my reports and run them.
> Please can someone explain what I should do to run them from the
> report manager?
> Thanks|||Lukasz,
I made the changes suggested by you but still the same problem. The URL it shows is:
http://localhost/Reports/Pages/Report.aspx?ItemPath=%2fMYREPORTS%2fRPT1
What am I doing wrong?
nroy@.iastate.edu (Roy) wrote in message news:<ad20302f.0408091310.6e20c373@.posting.google.com>...
> Here is what is happening.
> I have a working project PROG created using VS.Net. I create a new
> project for reports RPTPROJ under PROJ.
> I create several reports RPT1.RDL, RPT2.RDL under the new project
> RPTPROJ.
> Now I start the REPORT MANAGER and create a new folder (MYREPORTS) and
> upload all my reports (RDLs) into this new folder. Now when I click on
> any of the reports from here, it doesn't show up. Only shows up an
> "Action Canceled" message.
> Here is the URL, it generates for one of the reports:
> http://localhost/Reports/Pages/Report.aspx?ItemPath=%2fRPTPROJ%2fRPT1
> But when I goto,
> http://localhost/reportserver?%2fPROJ%2fRPTPROJ
> I can see all my reports and run them.
> Please can someone explain what I should do to run them from the
> report manager?
> Thanks

Can't Access Cube Templates

Hello,

I appreciate this is probably a noddy question but I can't find the answer in any of the normal resources.

I'm working through Brian Larsons Business Intelligence with SQL Server 2005.

Chapter 6 requires me to set up a Cube from a Template.

I've chosen the Cube Wizard from the Project Explorer and then clicked next on the welcome page.

Problem is when I select the second radio button (the option that indicates that the source is not a data mart) the chose template checkbox that activates the template drop-down is disabled.

This obviously means I can't chose the template I need. I've continued with the book anyway but now I need to use the Cube that I've failed to build :(

I think this may be something to do with the default template folder as the path indicated int he book did not exist so I have to build it. Does anyone know the default path for OLAP Cube Templates?

I am using the Trial Version of SQL Server 2005 and assocaite Visual Studio components.

Thanks for any help,

James

I see templates installed on my machine into C:\Program Files\Microsoft SQL Server\90\Tools\Templates\olap\1033.

But I think for specific question regarding particular book you should direct your questions to the author.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi James,

Did you solve your problem of being template drop down being not accessible ? I have exactly the same probelm ?

-TIA
Panks

|||

I guess.... I have figured this out..My sql server installtion is in e: where as my windows dir is d: so MSSQL installed common components in d: , when I created the nested dir structure for cube templates in d: Cube wizard did enable the cube template drop down.

I am never able to understand why MS provides an option of specifying directory when windows drive is indeed a requirement anyway.

-Panks

|||

Hi. I am trying to build cube using cube template with help of brian larson book "delivering business intelligence using SQL server 2005". Books asks to copy sales and inventory folder from book web site to the cube template folder in the sql server(page 131).can you please advice me how to do it? which site to go to?

thanx

|||I am having the exact same annoying problem. Have you found anything?|||

The book's web site is at:

http://mhprofessional.com/product.php?cat=112&isbn=0072260904

Use the Code link on the left side of the page to download the zip file with all of the goodies. You will find the sales and inventory folder in there.

|||I had encountered the same problem, but when following a different book. I discovered that irrespective of where SQL Server 2005 is installed, there MUST be a templates folder on the drive where Windows is installed. In my case SQL Server 2005 was installed on E: and the Analysis Services templates folder the installation created was at E:\Microsoft SQL Server\90\Tools\Templates\olap\1033\. For some reason the Cube Wizard in BIDS cannot see this folder and so no templates are visible in the wizard. If you create a folder with a path of C:\Program Files\Microsoft SQL Server\90\Tools and then copy the Templates folder (and all its contents) from (in my case) E:\Microsoft SQL Server\90\Tools\ to C:\Program Files\Microsoft SQL Server\90\Tools you will be able to see the templates in the Cube Wizard.

HTH
Caryl
sql

Can't Access Cube Templates

Hello,

I appreciate this is probably a noddy question but I can't find the answer in any of the normal resources.

I'm working through Brian Larsons Business Intelligence with SQL Server 2005.

Chapter 6 requires me to set up a Cube from a Template.

I've chosen the Cube Wizard from the Project Explorer and then clicked next on the welcome page.

Problem is when I select the second radio button (the option that indicates that the source is not a data mart) the chose template checkbox that activates the template drop-down is disabled.

This obviously means I can't chose the template I need. I've continued with the book anyway but now I need to use the Cube that I've failed to build :(

I think this may be something to do with the default template folder as the path indicated int he book did not exist so I have to build it. Does anyone know the default path for OLAP Cube Templates?

I am using the Trial Version of SQL Server 2005 and assocaite Visual Studio components.

Thanks for any help,

James

I see templates installed on my machine into C:\Program Files\Microsoft SQL Server\90\Tools\Templates\olap\1033.

But I think for specific question regarding particular book you should direct your questions to the author.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi James,

Did you solve your problem of being template drop down being not accessible ? I have exactly the same probelm ?

-TIA
Panks

|||

I guess.... I have figured this out..My sql server installtion is in e: where as my windows dir is d: so MSSQL installed common components in d: , when I created the nested dir structure for cube templates in d: Cube wizard did enable the cube template drop down.

I am never able to understand why MS provides an option of specifying directory when windows drive is indeed a requirement anyway.

-Panks

|||

Hi. I am trying to build cube using cube template with help of brian larson book "delivering business intelligence using SQL server 2005". Books asks to copy sales and inventory folder from book web site to the cube template folder in the sql server(page 131).can you please advice me how to do it? which site to go to?

thanx

|||I am having the exact same annoying problem. Have you found anything?|||

The book's web site is at:

http://mhprofessional.com/product.php?cat=112&isbn=0072260904

Use the Code link on the left side of the page to download the zip file with all of the goodies. You will find the sales and inventory folder in there.

|||I had encountered the same problem, but when following a different book. I discovered that irrespective of where SQL Server 2005 is installed, there MUST be a templates folder on the drive where Windows is installed. In my case SQL Server 2005 was installed on E: and the Analysis Services templates folder the installation created was at E:\Microsoft SQL Server\90\Tools\Templates\olap\1033\. For some reason the Cube Wizard in BIDS cannot see this folder and so no templates are visible in the wizard. If you create a folder with a path of C:\Program Files\Microsoft SQL Server\90\Tools and then copy the Templates folder (and all its contents) from (in my case) E:\Microsoft SQL Server\90\Tools\ to C:\Program Files\Microsoft SQL Server\90\Tools you will be able to see the templates in the Cube Wizard.

HTH
Caryl

Can't Access Cube Templates

Hello,

I appreciate this is probably a noddy question but I can't find the answer in any of the normal resources.

I'm working through Brian Larsons Business Intelligence with SQL Server 2005.

Chapter 6 requires me to set up a Cube from a Template.

I've chosen the Cube Wizard from the Project Explorer and then clicked next on the welcome page.

Problem is when I select the second radio button (the option that indicates that the source is not a data mart) the chose template checkbox that activates the template drop-down is disabled.

This obviously means I can't chose the template I need. I've continued with the book anyway but now I need to use the Cube that I've failed to build :(

I think this may be something to do with the default template folder as the path indicated int he book did not exist so I have to build it. Does anyone know the default path for OLAP Cube Templates?

I am using the Trial Version of SQL Server 2005 and assocaite Visual Studio components.

Thanks for any help,

James

I see templates installed on my machine into C:\Program Files\Microsoft SQL Server\90\Tools\Templates\olap\1033.

But I think for specific question regarding particular book you should direct your questions to the author.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi James,

Did you solve your problem of being template drop down being not accessible ? I have exactly the same probelm ?

-TIA
Panks

|||

I guess.... I have figured this out..My sql server installtion is in e: where as my windows dir is d: so MSSQL installed common components in d: , when I created the nested dir structure for cube templates in d: Cube wizard did enable the cube template drop down.

I am never able to understand why MS provides an option of specifying directory when windows drive is indeed a requirement anyway.

-Panks

|||

Hi. I am trying to build cube using cube template with help of brian larson book "delivering business intelligence using SQL server 2005". Books asks to copy sales and inventory folder from book web site to the cube template folder in the sql server(page 131).can you please advice me how to do it? which site to go to?

thanx

|||I am having the exact same annoying problem. Have you found anything?|||

The book's web site is at:

http://mhprofessional.com/product.php?cat=112&isbn=0072260904

Use the Code link on the left side of the page to download the zip file with all of the goodies. You will find the sales and inventory folder in there.

|||I had encountered the same problem, but when following a different book. I discovered that irrespective of where SQL Server 2005 is installed, there MUST be a templates folder on the drive where Windows is installed. In my case SQL Server 2005 was installed on E: and the Analysis Services templates folder the installation created was at E:\Microsoft SQL Server\90\Tools\Templates\olap\1033\. For some reason the Cube Wizard in BIDS cannot see this folder and so no templates are visible in the wizard. If you create a folder with a path of C:\Program Files\Microsoft SQL Server\90\Tools and then copy the Templates folder (and all its contents) from (in my case) E:\Microsoft SQL Server\90\Tools\ to C:\Program Files\Microsoft SQL Server\90\Tools you will be able to see the templates in the Cube Wizard.

HTH
Caryl

Can't Access Cube Templates

Hello,

I appreciate this is probably a noddy question but I can't find the answer in any of the normal resources.

I'm working through Brian Larsons Business Intelligence with SQL Server 2005.

Chapter 6 requires me to set up a Cube from a Template.

I've chosen the Cube Wizard from the Project Explorer and then clicked next on the welcome page.

Problem is when I select the second radio button (the option that indicates that the source is not a data mart) the chose template checkbox that activates the template drop-down is disabled.

This obviously means I can't chose the template I need. I've continued with the book anyway but now I need to use the Cube that I've failed to build :(

I think this may be something to do with the default template folder as the path indicated int he book did not exist so I have to build it. Does anyone know the default path for OLAP Cube Templates?

I am using the Trial Version of SQL Server 2005 and assocaite Visual Studio components.

Thanks for any help,

James

I see templates installed on my machine into C:\Program Files\Microsoft SQL Server\90\Tools\Templates\olap\1033.

But I think for specific question regarding particular book you should direct your questions to the author.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi James,

Did you solve your problem of being template drop down being not accessible ? I have exactly the same probelm ?

-TIA
Panks

|||

I guess.... I have figured this out..My sql server installtion is in e: where as my windows dir is d: so MSSQL installed common components in d: , when I created the nested dir structure for cube templates in d: Cube wizard did enable the cube template drop down.

I am never able to understand why MS provides an option of specifying directory when windows drive is indeed a requirement anyway.

-Panks

|||

Hi. I am trying to build cube using cube template with help of brian larson book "delivering business intelligence using SQL server 2005". Books asks to copy sales and inventory folder from book web site to the cube template folder in the sql server(page 131).can you please advice me how to do it? which site to go to?

thanx

|||I am having the exact same annoying problem. Have you found anything?|||

The book's web site is at:

http://mhprofessional.com/product.php?cat=112&isbn=0072260904

Use the Code link on the left side of the page to download the zip file with all of the goodies. You will find the sales and inventory folder in there.

|||I had encountered the same problem, but when following a different book. I discovered that irrespective of where SQL Server 2005 is installed, there MUST be a templates folder on the drive where Windows is installed. In my case SQL Server 2005 was installed on E: and the Analysis Services templates folder the installation created was at E:\Microsoft SQL Server\90\Tools\Templates\olap\1033\. For some reason the Cube Wizard in BIDS cannot see this folder and so no templates are visible in the wizard. If you create a folder with a path of C:\Program Files\Microsoft SQL Server\90\Tools and then copy the Templates folder (and all its contents) from (in my case) E:\Microsoft SQL Server\90\Tools\ to C:\Program Files\Microsoft SQL Server\90\Tools you will be able to see the templates in the Cube Wizard.

HTH
Caryl

Can't access an instance installed on same server

About 2 months ago I loaded a new instance on my SQL Server 200 box. I have
been working with the database in that instance. However, now I try to
access the other instance on the server and I get connection failed check
server registration properties. When I check them I get "login failed." I
switch the registration back to SQL and windows - same issue. All services
are running on server and users are able to get to database.
I checked whitepapers and KB but can't find what to do. Any assistance is
greatly appreciated.
Hi
If you login is failing how can your "users are able to get to database"?
If you can access the server using the given login though query analyser
(from the failing client), then check the connection string and check the
network libraries/protocols.
John
"Multitasker" wrote:

> About 2 months ago I loaded a new instance on my SQL Server 200 box. I have
> been working with the database in that instance. However, now I try to
> access the other instance on the server and I get connection failed check
> server registration properties. When I check them I get "login failed." I
> switch the registration back to SQL and windows - same issue. All services
> are running on server and users are able to get to database.
> I checked whitepapers and KB but can't find what to do. Any assistance is
> greatly appreciated.
sql

Can't access an instance installed on same server

About 2 months ago I loaded a new instance on my SQL Server 200 box. I have
been working with the database in that instance. However, now I try to
access the other instance on the server and I get connection failed check
server registration properties. When I check them I get "login failed." I
switch the registration back to SQL and windows - same issue. All services
are running on server and users are able to get to database.
I checked whitepapers and KB but can't find what to do. Any assistance is
greatly appreciated.Hi
If you login is failing how can your "users are able to get to database"?
If you can access the server using the given login though query analyser
(from the failing client), then check the connection string and check the
network libraries/protocols.
John
"Multitasker" wrote:

> About 2 months ago I loaded a new instance on my SQL Server 200 box. I hav
e
> been working with the database in that instance. However, now I try to
> access the other instance on the server and I get connection failed check
> server registration properties. When I check them I get "login failed." I
> switch the registration back to SQL and windows - same issue. All services
> are running on server and users are able to get to database.
> I checked whitepapers and KB but can't find what to do. Any assistance is
> greatly appreciated.

Can't access an instance installed on same server

About 2 months ago I loaded a new instance on my SQL Server 200 box. I have
been working with the database in that instance. However, now I try to
access the other instance on the server and I get connection failed check
server registration properties. When I check them I get "login failed." I
switch the registration back to SQL and windows - same issue. All services
are running on server and users are able to get to database.
I checked whitepapers and KB but can't find what to do. Any assistance is
greatly appreciated.Hi
If you login is failing how can your "users are able to get to database"?
If you can access the server using the given login though query analyser
(from the failing client), then check the connection string and check the
network libraries/protocols.
John
"Multitasker" wrote:
> About 2 months ago I loaded a new instance on my SQL Server 200 box. I have
> been working with the database in that instance. However, now I try to
> access the other instance on the server and I get connection failed check
> server registration properties. When I check them I get "login failed." I
> switch the registration back to SQL and windows - same issue. All services
> are running on server and users are able to get to database.
> I checked whitepapers and KB but can't find what to do. Any assistance is
> greatly appreciated.

Monday, March 19, 2012

Canot Telnet into port 1433 affter intalling SQL Server !

I'm working on a completely virgin install of SQL Server 2k in Windows 2003.
Just after install I check that the TCP/IP protocol is enabled under the
server properties and then I try to Telnet into port 1433. On this one
particular box I get back the following:

C:\>telnet localhost 1433
Connecting to localhost...Could not open connection to the host, on port
1433: Connect failed.

For comparison I tested telnet on a couple other machines and I get back a
blank window ready for my commands, as I'd expect.

I've checked the firewall settings and other IP Filtering settings to see if
any of those were blocking traffic to 1433... nothing. I've triple checked
the SQL Server settings for any "problems" and nothing jumps out at me.Have you configured the server to listen to port 1433? Is it set to Dynamic?|||Try installing SQLServer 2000 SP3 or 3a if you have not already.|||

add to your conecction string: namedPipe=true

i hope this solve your problem

Canot Telnet into port 1433 affter intalling SQL Server !

I'm working on a completely virgin install of SQL Server 2k in Windows 2003.
Just after install I check that the TCP/IP protocol is enabled under the
server properties and then I try to Telnet into port 1433. On this one
particular box I get back the following:

C:\>telnet localhost 1433
Connecting to localhost...Could not open connection to the host, on port
1433: Connect failed.

For comparison I tested telnet on a couple other machines and I get back a
blank window ready for my commands, as I'd expect.

I've checked the firewall settings and other IP Filtering settings to see if
any of those were blocking traffic to 1433... nothing. I've triple checked
the SQL Server settings for any "problems" and nothing jumps out at me.Have you configured the server to listen to port 1433? Is it set to Dynamic?|||Try installing SQLServer 2000 SP3 or 3a if you have not already.|||

add to your conecction string: namedPipe=true

i hope this solve your problem