error attaching single db .mdf file

Hi,
The dev deleted some of the ldf files mistakenly and are unable to attach the mdf file.
How can i re-create the db with the existing mdf file and a new ldf file. Can someone suggest.
Thanks,
Arzan
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf
Andrew J. Kelly SQL MVP
"Arzan" <Arzan@.discussions.microsoft.com> wrote in message
news:8A81A4E5-F699-4552-A0C0-8310527A7EA5@.microsoft.com...
> Hi,
> The dev deleted some of the ldf files mistakenly and are unable to attach
the mdf file.
> How can i re-create the db with the existing mdf file and a new ldf file.
Can someone suggest.
> Thanks,
> Arzan
|||Hi,
Try using the procedure "sp_attach_single_file_db" to attach the database
with specifying the MDF file only.
EXEC sp_attach_single_file_db 'dbname', 'c:\mssql\data\dbname.mdf'
THis will create a new database with exiting mdf and new ldf file.
This command will fail in below scenarios:-
1. If the database is not detached using sp_detach_db
2. If you have multiple LDF files in your old database.
If your sp_attach_single_file_db command fails then probaly you have to
restore the database from good backup available.
Thanks
Hari
MCDBA
"Arzan" <Arzan@.discussions.microsoft.com> wrote in message
news:8A81A4E5-F699-4552-A0C0-8310527A7EA5@.microsoft.com...
> Hi,
> The dev deleted some of the ldf files mistakenly and are unable to attach
the mdf file.
> How can i re-create the db with the existing mdf file and a new ldf file.
Can someone suggest.
> Thanks,
> Arzan
|||Thanks Hari, the problem has been resolved.
"Hari Prasad" wrote:

> Hi,
> Try using the procedure "sp_attach_single_file_db" to attach the database
> with specifying the MDF file only.
> EXEC sp_attach_single_file_db 'dbname', 'c:\mssql\data\dbname.mdf'
> THis will create a new database with exiting mdf and new ldf file.
> This command will fail in below scenarios:-
> 1. If the database is not detached using sp_detach_db
> 2. If you have multiple LDF files in your old database.
> If your sp_attach_single_file_db command fails then probaly you have to
> restore the database from good backup available.
> Thanks
> Hari
> MCDBA
>
> "Arzan" <Arzan@.discussions.microsoft.com> wrote in message
> news:8A81A4E5-F699-4552-A0C0-8310527A7EA5@.microsoft.com...
> the mdf file.
> Can someone suggest.
>
>

error attaching single db .mdf file

Hi,
The dev deleted some of the ldf files mistakenly and are unable to attach th
e mdf file.
How can i re-create the db with the existing mdf file and a new ldf file. Ca
n someone suggest.
Thanks,
Arzanhttp://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
Andrew J. Kelly SQL MVP
"Arzan" <Arzan@.discussions.microsoft.com> wrote in message
news:8A81A4E5-F699-4552-A0C0-8310527A7EA5@.microsoft.com...
> Hi,
> The dev deleted some of the ldf files mistakenly and are unable to attach
the mdf file.
> How can i re-create the db with the existing mdf file and a new ldf file.
Can someone suggest.
> Thanks,
> Arzan|||Hi,
Try using the procedure "sp_attach_single_file_db" to attach the database
with specifying the MDF file only.
EXEC sp_attach_single_file_db 'dbname', 'c:\mssql\data\dbname.mdf'
THis will create a new database with exiting mdf and new ldf file.
This command will fail in below scenarios:-
1. If the database is not detached using sp_detach_db
2. If you have multiple LDF files in your old database.
If your sp_attach_single_file_db command fails then probaly you have to
restore the database from good backup available.
Thanks
Hari
MCDBA
"Arzan" <Arzan@.discussions.microsoft.com> wrote in message
news:8A81A4E5-F699-4552-A0C0-8310527A7EA5@.microsoft.com...
> Hi,
> The dev deleted some of the ldf files mistakenly and are unable to attach
the mdf file.
> How can i re-create the db with the existing mdf file and a new ldf file.
Can someone suggest.
> Thanks,
> Arzan|||Thanks Hari, the problem has been resolved.
"Hari Prasad" wrote:

> Hi,
> Try using the procedure "sp_attach_single_file_db" to attach the database
> with specifying the MDF file only.
> EXEC sp_attach_single_file_db 'dbname', 'c:\mssql\data\dbname.mdf'
> THis will create a new database with exiting mdf and new ldf file.
> This command will fail in below scenarios:-
> 1. If the database is not detached using sp_detach_db
> 2. If you have multiple LDF files in your old database.
> If your sp_attach_single_file_db command fails then probaly you have to
> restore the database from good backup available.
> Thanks
> Hari
> MCDBA
>
> "Arzan" <Arzan@.discussions.microsoft.com> wrote in message
> news:8A81A4E5-F699-4552-A0C0-8310527A7EA5@.microsoft.com...
> the mdf file.
> Can someone suggest.
>
>

error attaching single db .mdf file

Hi,
The dev deleted some of the ldf files mistakenly and are unable to attach the mdf file.
How can i re-create the db with the existing mdf file and a new ldf file. Can someone suggest.
Thanks,
Arzanhttp://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
--
Andrew J. Kelly SQL MVP
"Arzan" <Arzan@.discussions.microsoft.com> wrote in message
news:8A81A4E5-F699-4552-A0C0-8310527A7EA5@.microsoft.com...
> Hi,
> The dev deleted some of the ldf files mistakenly and are unable to attach
the mdf file.
> How can i re-create the db with the existing mdf file and a new ldf file.
Can someone suggest.
> Thanks,
> Arzan|||Hi,
Try using the procedure "sp_attach_single_file_db" to attach the database
with specifying the MDF file only.
EXEC sp_attach_single_file_db 'dbname', 'c:\mssql\data\dbname.mdf'
THis will create a new database with exiting mdf and new ldf file.
This command will fail in below scenarios:-
1. If the database is not detached using sp_detach_db
2. If you have multiple LDF files in your old database.
If your sp_attach_single_file_db command fails then probaly you have to
restore the database from good backup available.
Thanks
Hari
MCDBA
"Arzan" <Arzan@.discussions.microsoft.com> wrote in message
news:8A81A4E5-F699-4552-A0C0-8310527A7EA5@.microsoft.com...
> Hi,
> The dev deleted some of the ldf files mistakenly and are unable to attach
the mdf file.
> How can i re-create the db with the existing mdf file and a new ldf file.
Can someone suggest.
> Thanks,
> Arzan

error attaching db...

Hello,

I tried to attach my database (SQL Server 2000 w/ SP3) at work after taking it home to work on it and it gave me an error.

I tried to attaching my backup one as one (which use to work) and now does not. I treid to attach other DB's and they are fine.

The error message displayed on the screen is:

----
Microsoft SQL-DMO (ODBC SQLState:HY000)

X Error 3264
Location: recbase.cpp:1374
Expression: m_nVars > 0
SPID: 51
Process ID: 1004
----

The error message recorded in Event Viewer is:

------
Event ID: 17055

17066 :
SQL Server Assertion: File: <recbase.cpp>, line=1374
Failed Assertion = 'm_nVars > 0'.

------

Any ideas what could have gone wrong? or is it simply a matter of reinstalling SQL server.

thanks,

JPCheck this SQLMAG forum link (http://www.sqlmag.com/Forums/messageview.cfm?catid=5&threadid=4702) for information.

HTH|||Originally posted by Satya
Check this SQLMAG forum link (http://www.sqlmag.com/Forums/messageview.cfm?catid=5&threadid=4702) for information.

HTH

Hey satya,

thanks for the heads up. I don't understand why it should be a SP issue because both of them are the same and it use to work before. Last week, I did the same... detach the DB, worked on it at home and rettached it back at work... no problem.

Oh well, such is life ... full of disappointments. I'll reintall the SP and see what happens. Maybe I'll do a windows update as well cuz we never know if it does affect anything else.

I'll report back should I get the problem fixed.

thanks,

JP|||Originally posted by globeuser
Hey satya,

thanks for the heads up. I don't understand why it should be a SP issue because both of them are the same and it use to work before. Last week, I did the same... detach the DB, worked on it at home and rettached it back at work... no problem.

Oh well, such is life ... full of disappointments. I'll reintall the SP and see what happens. Maybe I'll do a windows update as well cuz we never know if it does affect anything else.

I'll report back should I get the problem fixed.

thanks,

JP

Nope.. same error result. did not work. I've reapplied SP3 and unfortunately I'm still getting this error.

One factor though... I ftp'd down the DB instead of making a copy on the CD but I've downloaded them a number of times and still the same error appears.

any other ideas anyone?

kinda desperate ;-) Guess I'll have to reinstall?

JP|||Originally posted by Satya
Check this SQLMAG forum link (http://www.sqlmag.com/Forums/messageview.cfm?catid=5&threadid=4702) for information.

HTH

Yup... looks like a reinstall is the only option because I am now getting another error message:

--------

Microsoft SQL-DMO (ODBC SQLState:42000)

X Error 1813: Cound not opne new database 'MyProject'. CREATE DATABASE is aborterd.
SQlDumpExceptionHandler: Process 51 genrated fatal exception c0000005 EXCEPTION_ACCESS_violation
Server is terminating this process.

--------

any other ideas?

JP|||Last resort to contact MS PSS for any fix on this EAV issues.|||Originally posted by Satya
Last resort to contact MS PSS for any fix on this EAV issues.

I had a hunch that it might just be as simple s this but I remembered that when I tried to detach it, it took some time because there were stilll some connections to it and I "forced it" to disconnect. It should not take that long because I have a very fast machine.

Lucky for me that the database was still there and I reattached it again first thing before any connections or apps have access to it.

The detachment is now clean and was able to attach it now to another machine.

The lesson learned is that the detach process was dirty or forced and all I had to do was to do it again before any other applications has a lock on it.

JP|||Thats fine, but before you detach make sure to run health checks and DBCC against the database to make sure its lively.|||Originally posted by Satya
Thats fine, but before you detach make sure to run health checks and DBCC against the database to make sure its lively.

Sorry, but how do you do that? I noticed that when I tried to run one of my stored procedures or view the properties in the DB, i get an error displayed...

And when I tried to delete the stored procedure to recreate it won't allow me to or can't delete it!

------
Microsoft SQL-DMO (ODBC SQLState:HY000)

X Error 605: Attempt to to fetch logical page (1:0) in database 'MyProject' belongs to object 'ALLOCATION', not to object 'syscomments'.
------

I am running ColdFusion 5 and this was what was displayed.

------
ODBC Error Code = S1000 (General error)

[Microsoft][ODBC SQL Server Driver][SQL Server]Attempt to fetch logical page (1:0) in database 'MyProject' belongs to object 'ALLOCATION', not to object 'syscomments'.
------

As I said, the SP works in my other machine and only when I move it over to this one that the error pops up.

ideas anyone?

JP|||This error occurs when SQL detcts any database corruption and to determine the full extent of the corruption, execute DBCC CHECKDB as soon as possible. Also check the error log for other errors, which often accompany a 605 error.

For more information on CHECKDB refer to books online.

My suggestion is to keep database in DBO Use only until you resolve the corruption on the database, do not allow any other process to deal with until this gets fixed.

HTH|||Originally posted by Satya
This error occurs when SQL detcts any database corruption and to determine the full extent of the corruption, execute DBCC CHECKDB as soon as possible. Also check the error log for other errors, which often accompany a 605 error.

For more information on CHECKDB refer to books online.

My suggestion is to keep database in DBO Use only until you resolve the corruption on the database, do not allow any other process to deal with until this gets fixed.

HTH

I tried correcting the db is single-user mode but when i tried to execute

dbcc checkdb ('MyProject', REPAIR_ALLOW_DATA_LOSS )

it notifies me that I should be in single-user mode which I already am and won't continue.!

perhaps I should just reinstall SQL... good thing I keep a script of table creation and sp procedures.

JP|||Make sure you haven't opened or accessed same DB in EM and QA.
Its not necessarily to have DB in singel-user mode when running DBCC CHECKDB, you can kill any other process which is involved to access during this execution.|||Originally posted by Satya
Make sure you haven't opened or accessed same DB in EM and QA.
Its not necessarily to have DB in singel-user mode when running DBCC CHECKDB, you can kill any other process which is involved to access during this execution.

I'm sure i haven't got any connections to it. I just finished installing it and still same errors... *sigh*|||I downloaded the same DB from another machine and to my surprise this was not corrupt at all. Perhaps its the target machine where I uploaded it to that caused the error. There are so many factors that I would not be surprised a simple thing such as these may be the cause in the first place.

thanks for the checkdb info.

JP|||If the problem persists from Database there is no use if SQL Server is reinstalled. Try to fix the corruption on the database level.

As you've scripts for the database, export important data using DTS to a text file and recreate the DB using scripts and import using DTS, it may work.

Meanwhile have a sneak thru SQL Error log for any information.

All the best.|||the good thing is that my main development machine is at my home office and the test box is here at work.

I'm not too concerned about the data for now because I'm still writing the program but I have tried to fix the corruption at the db level but quite honestly, the error log doesn't tell me anything more than what was displayed when I ran the cehckdb script anyway and even if I tried, i can't get it to fix it.

JP|||For the database corruption its suggested to use DBCC CHECKDB and check for event viewer also for any hardware issues or harddisk problems.|||I understand. I did mention it in my original post along with what the event viewer recorded.

anyway, when i have some time, I'll investigate further.

thanks,

JP

Error attaching database file

When I tried to attach a database it failed with:
Error 3624:
Location: recbase.cpp:1374
Expression: m_nVars > 0
SPID: 55
Process ID: 952
Some ideas to recover the file?
Marco,
Could be a corrupt file.
Did you perform a DBCC CHECKDB prior to detaching? Did you detach the
database before or...? What method are you using to attach i.e.,
sp_attach_db or sp_attach_single_file_db? Do you have admin permissions to
do this?
HTH
Jerry
"Marco Frontini" <iunknown@.libero.it> wrote in message
news:es5ZY5QyFHA.2652@.TK2MSFTNGP14.phx.gbl...
> When I tried to attach a database it failed with:
> Error 3624:
> Location: recbase.cpp:1374
> Expression: m_nVars > 0
> SPID: 55
> Process ID: 952
> Some ideas to recover the file?
>

Error attaching database file

When I tried to attach a database it failed with:
Error 3624:
Location: recbase.cpp:1374
Expression: m_nVars > 0
SPID: 55
Process ID: 952
Some ideas to recover the file?Marco,
Could be a corrupt file.
Did you perform a DBCC CHECKDB prior to detaching? Did you detach the
database before or...? What method are you using to attach i.e.,
sp_attach_db or sp_attach_single_file_db? Do you have admin permissions to
do this?
HTH
Jerry
"Marco Frontini" <iunknown@.libero.it> wrote in message
news:es5ZY5QyFHA.2652@.TK2MSFTNGP14.phx.gbl...
> When I tried to attach a database it failed with:
> Error 3624:
> Location: recbase.cpp:1374
> Expression: m_nVars > 0
> SPID: 55
> Process ID: 952
> Some ideas to recover the file?
>

Error attaching database file

When I tried to attach a database it failed with:
Error 3624:
Location: recbase.cpp:1374
Expression: m_nVars > 0
SPID: 55
Process ID: 952
Some ideas to recover the file?Marco,
Could be a corrupt file.
Did you perform a DBCC CHECKDB prior to detaching? Did you detach the
database before or...? What method are you using to attach i.e.,
sp_attach_db or sp_attach_single_file_db? Do you have admin permissions to
do this?
HTH
Jerry
"Marco Frontini" <iunknown@.libero.it> wrote in message
news:es5ZY5QyFHA.2652@.TK2MSFTNGP14.phx.gbl...
> When I tried to attach a database it failed with:
> Error 3624:
> Location: recbase.cpp:1374
> Expression: m_nVars > 0
> SPID: 55
> Process ID: 952
> Some ideas to recover the file?
>

Error attaching database

I detached a database to copy the files and when I tried to re-attach it
failed with:
/ ****************************************
/
Server: Msg 3624, Level 20, State 1, Line 1
Location: recbase.cpp:1374
Expression: m_nVars > 0
SPID: 55
Process ID: 952
Connection Broken
/ ****************************************
/
I'm pretty sure this is a disk problem. Is there anyway to re-attach this db
in emergency mode? Like you can with a suspect database.
Any help would be appreciated,
DougSIf going back to backup is not an option, then you may want to contact
Microsoft PSS. They maybe able to help you rebuild the transaction log.
However, the database may still be corrupted and depending on the extent of
the corruption, you may or may not be able to repair or extract data out.
Yih-Yoon Lee
On Wed, 24 Mar 2004 11:51:24 -0500, Doug Stiers wrote:

> I detached a database to copy the files and when I tried to re-attach it
> failed with:
> / ****************************************
/
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recbase.cpp:1374
> Expression: m_nVars > 0
> SPID: 55
> Process ID: 952
> Connection Broken
> / ****************************************
/
> I'm pretty sure this is a disk problem. Is there anyway to re-attach this
db
> in emergency mode? Like you can with a suspect database.
> Any help would be appreciated,
> DougS

error attaching adventureworks database and SSIS training database

Hi there,

I got this error when i tried to attach the adventureworks database and SSIS training database.

an exception occurred while executing a transact-sql statement or batch
(microsoft.sqlserver.connectioninfo)

could not find row in sysindexes for database ID 17, object ID 1, index ID 1. Run DBCC
checktable on sysindexes.

I join join a network domain for my computer. Previously it doesnt have this problem.

Hello,

It appears that you are trying to attach a SQL Server 2005 database to an instance of SQL Server 2000 or earlier. Please try to attach the AV database to a SQL Server 2005 instance.

Derrick VanArnam - MSFT

Error attaching a database

Hello:
When attaching a database that was detached from another SQL Server instance
and copied over to this machine, I got the error message below:
Error 602: Could not find row in sysindexes for database ID 7, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
Can somebody guide me on the steps I have to follow to resolve this issue?
Thanks.
VenkiHi
On the original server, run DBCC CHECKDB as during the attach, SQL Server is
finding possible corruption in the DB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"vvenk" <vvenk@.discussions.microsoft.com> wrote in message
news:8F0E56C4-F250-465A-A86E-D9DB92BFF9A7@.microsoft.com...
> Hello:
> When attaching a database that was detached from another SQL Server
> instance
> and copied over to this machine, I got the error message below:
> Error 602: Could not find row in sysindexes for database ID 7, object ID
> 1,
> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> Can somebody guide me on the steps I have to follow to resolve this issue?
> Thanks.
> Venki|||Mike:
The source DB Server has been retired and not available.
Is there any other option available to get the database back online?
Please say yes!
venki
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> On the original server, run DBCC CHECKDB as during the attach, SQL Server
is
> finding possible corruption in the DB.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:8F0E56C4-F250-465A-A86E-D9DB92BFF9A7@.microsoft.com...
>
>|||
>
What are the results of DBCC CHECKTABLE sysindexes?
Regards
JTC ^..^|||As I said, I don't have access to the source DB instance anymore. Since my
understanding was that DBCC should be run on the source DB instance, I have
not done it.
"JTC ^..^" wrote:

>
> What are the results of DBCC CHECKTABLE sysindexes?
> --
> Regards
> JTC ^..^
>|||Hi,
Try the below steps. If it fails restore from a good database backup.
Steps:
1. Create a new database with the same name and same MDF and LDF files
2. Stop sql server and rename the existing MDF to a new one and copy the
original MDF to this location and delete the LDF files.
3. Start SQL Server
4. Now your database will be marked suspect
5. Update the sysdatabases to update to Emergency mode. This will not use
LOG files in start up
Sp_configure "allow updates", 1
go
Reconfigure with override
GO
Update sysdatabases set status = 32768 where name = "BadDbName"
go
Sp_configure "allow updates", 0
go
Reconfigure with override
GO
6. Restart sql server. now the database will be in emergency mode
7. Create a new database and use DTS to copy the objects and data to new
database. You can use this new database.
Note:
If you have the backup file, it is always recommended to use the backup file
to restore the database. SO that data integrity will be maintained.
.
Thanks
Hari
SQL Server MVP
"vvenk" <vvenk@.discussions.microsoft.com> wrote in message
news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...[vbcol=seagreen]
> As I said, I don't have access to the source DB instance anymore. Since my
> understanding was that DBCC should be run on the source DB instance, I
> have
> not done it.
> "JTC ^..^" wrote:
>|||Hari:
Thank you. When following the steps, when I tried to execute the statement,
Update sysdatabases set status = 32768 where name = "BadDbName"
I got an error, "Invalid column nam". However, I found what the dbid was for
that particular row and updated the row with that column in the Where clause
.
I will now try to see if the data is accessible.
"Hari Prasad" wrote:

> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup fi
le
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
>
>|||Hari:
Also, I executed the statements after I was logged into master database; I
could not log onto the badDBName.
I hope that was fine.
Venki
"Hari Prasad" wrote:

> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup fi
le
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
>
>|||Hari:
Yes, the database is in emergency mode.
When I tried to create a DTS job to import, it does not show up in the list
of databases available as a source.
Any ideas?
venki
"Hari Prasad" wrote:

> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup fi
le
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
>
>

Error attaching a database

Hello:
When attaching a database that was detached from another SQL Server instance
and copied over to this machine, I got the error message below:
Error 602: Could not find row in sysindexes for database ID 7, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
Can somebody guide me on the steps I have to follow to resolve this issue?
Thanks.
VenkiHi
On the original server, run DBCC CHECKDB as during the attach, SQL Server is
finding possible corruption in the DB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"vvenk" <vvenk@.discussions.microsoft.com> wrote in message
news:8F0E56C4-F250-465A-A86E-D9DB92BFF9A7@.microsoft.com...
> Hello:
> When attaching a database that was detached from another SQL Server
> instance
> and copied over to this machine, I got the error message below:
> Error 602: Could not find row in sysindexes for database ID 7, object ID
> 1,
> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> Can somebody guide me on the steps I have to follow to resolve this issue?
> Thanks.
> Venki|||Mike:
The source DB Server has been retired and not available.
Is there any other option available to get the database back online?
Please say yes!
venki
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> On the original server, run DBCC CHECKDB as during the attach, SQL Server is
> finding possible corruption in the DB.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:8F0E56C4-F250-465A-A86E-D9DB92BFF9A7@.microsoft.com...
> > Hello:
> >
> > When attaching a database that was detached from another SQL Server
> > instance
> > and copied over to this machine, I got the error message below:
> >
> > Error 602: Could not find row in sysindexes for database ID 7, object ID
> > 1,
> > index ID 1. Run DBCC CHECKTABLE on sysindexes.
> >
> > Can somebody guide me on the steps I have to follow to resolve this issue?
> >
> > Thanks.
> >
> > Venki
>
>|||>> Error 602: Could not find row in sysindexes for database ID 7, object
>> ID 1,
>> index ID 1. Run DBCC CHECKTABLE on sysindexes.
>> Can somebody guide me on the steps I have to follow to resolve this
>> issue?
>> Thanks.
>> Venki
>
What are the results of DBCC CHECKTABLE sysindexes?
--
Regards
JTC ^..^|||As I said, I don't have access to the source DB instance anymore. Since my
understanding was that DBCC should be run on the source DB instance, I have
not done it.
"JTC ^..^" wrote:
> >> Error 602: Could not find row in sysindexes for database ID 7, object
> >> ID 1,
> >> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> >>
> >> Can somebody guide me on the steps I have to follow to resolve this
> >> issue?
> >>
> >> Thanks.
> >>
> >> Venki
> >
> >
> What are the results of DBCC CHECKTABLE sysindexes?
> --
> Regards
> JTC ^..^
>|||Hi,
Try the below steps. If it fails restore from a good database backup.
Steps:
1. Create a new database with the same name and same MDF and LDF files
2. Stop sql server and rename the existing MDF to a new one and copy the
original MDF to this location and delete the LDF files.
3. Start SQL Server
4. Now your database will be marked suspect
5. Update the sysdatabases to update to Emergency mode. This will not use
LOG files in start up
Sp_configure "allow updates", 1
go
Reconfigure with override
GO
Update sysdatabases set status = 32768 where name = "BadDbName"
go
Sp_configure "allow updates", 0
go
Reconfigure with override
GO
6. Restart sql server. now the database will be in emergency mode
7. Create a new database and use DTS to copy the objects and data to new
database. You can use this new database.
Note:
If you have the backup file, it is always recommended to use the backup file
to restore the database. SO that data integrity will be maintained.
.
Thanks
Hari
SQL Server MVP
"vvenk" <vvenk@.discussions.microsoft.com> wrote in message
news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
> As I said, I don't have access to the source DB instance anymore. Since my
> understanding was that DBCC should be run on the source DB instance, I
> have
> not done it.
> "JTC ^..^" wrote:
>> >> Error 602: Could not find row in sysindexes for database ID 7, object
>> >> ID 1,
>> >> index ID 1. Run DBCC CHECKTABLE on sysindexes.
>> >>
>> >> Can somebody guide me on the steps I have to follow to resolve this
>> >> issue?
>> >>
>> >> Thanks.
>> >>
>> >> Venki
>> >
>> >
>> What are the results of DBCC CHECKTABLE sysindexes?
>> --
>> Regards
>> JTC ^..^|||Hari:
Thank you. When following the steps, when I tried to execute the statement,
Update sysdatabases set status = 32768 where name = "BadDbName"
I got an error, "Invalid column nam". However, I found what the dbid was for
that particular row and updated the row with that column in the Where clause.
I will now try to see if the data is accessible.
"Hari Prasad" wrote:
> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup file
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
> > As I said, I don't have access to the source DB instance anymore. Since my
> > understanding was that DBCC should be run on the source DB instance, I
> > have
> > not done it.
> >
> > "JTC ^..^" wrote:
> >
> >>
> >> >> Error 602: Could not find row in sysindexes for database ID 7, object
> >> >> ID 1,
> >> >> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> >> >>
> >> >> Can somebody guide me on the steps I have to follow to resolve this
> >> >> issue?
> >> >>
> >> >> Thanks.
> >> >>
> >> >> Venki
> >> >
> >> >
> >>
> >> What are the results of DBCC CHECKTABLE sysindexes?
> >>
> >> --
> >> Regards
> >> JTC ^..^
> >>
>
>|||Hari:
Also, I executed the statements after I was logged into master database; I
could not log onto the badDBName.
I hope that was fine.
Venki
"Hari Prasad" wrote:
> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup file
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
> > As I said, I don't have access to the source DB instance anymore. Since my
> > understanding was that DBCC should be run on the source DB instance, I
> > have
> > not done it.
> >
> > "JTC ^..^" wrote:
> >
> >>
> >> >> Error 602: Could not find row in sysindexes for database ID 7, object
> >> >> ID 1,
> >> >> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> >> >>
> >> >> Can somebody guide me on the steps I have to follow to resolve this
> >> >> issue?
> >> >>
> >> >> Thanks.
> >> >>
> >> >> Venki
> >> >
> >> >
> >>
> >> What are the results of DBCC CHECKTABLE sysindexes?
> >>
> >> --
> >> Regards
> >> JTC ^..^
> >>
>
>|||Hari:
Yes, the database is in emergency mode.
When I tried to create a DTS job to import, it does not show up in the list
of databases available as a source.
Any ideas?
venki
"Hari Prasad" wrote:
> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup file
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
> > As I said, I don't have access to the source DB instance anymore. Since my
> > understanding was that DBCC should be run on the source DB instance, I
> > have
> > not done it.
> >
> > "JTC ^..^" wrote:
> >
> >>
> >> >> Error 602: Could not find row in sysindexes for database ID 7, object
> >> >> ID 1,
> >> >> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> >> >>
> >> >> Can somebody guide me on the steps I have to follow to resolve this
> >> >> issue?
> >> >>
> >> >> Thanks.
> >> >>
> >> >> Venki
> >> >
> >> >
> >>
> >> What are the results of DBCC CHECKTABLE sysindexes?
> >>
> >> --
> >> Regards
> >> JTC ^..^
> >>
>
>

Error attaching a database

Hello:
When attaching a database that was detached from another SQL Server instance
and copied over to this machine, I got the error message below:
Error 602: Could not find row in sysindexes for database ID 7, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
Can somebody guide me on the steps I have to follow to resolve this issue?
Thanks.
Venki
Hi
On the original server, run DBCC CHECKDB as during the attach, SQL Server is
finding possible corruption in the DB.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"vvenk" <vvenk@.discussions.microsoft.com> wrote in message
news:8F0E56C4-F250-465A-A86E-D9DB92BFF9A7@.microsoft.com...
> Hello:
> When attaching a database that was detached from another SQL Server
> instance
> and copied over to this machine, I got the error message below:
> Error 602: Could not find row in sysindexes for database ID 7, object ID
> 1,
> index ID 1. Run DBCC CHECKTABLE on sysindexes.
> Can somebody guide me on the steps I have to follow to resolve this issue?
> Thanks.
> Venki
|||Mike:
The source DB Server has been retired and not available.
Is there any other option available to get the database back online?
Please say yes!
venki
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> On the original server, run DBCC CHECKDB as during the attach, SQL Server is
> finding possible corruption in the DB.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:8F0E56C4-F250-465A-A86E-D9DB92BFF9A7@.microsoft.com...
>
>
|||
>
What are the results of DBCC CHECKTABLE sysindexes?
Regards
JTC ^..^
|||As I said, I don't have access to the source DB instance anymore. Since my
understanding was that DBCC should be run on the source DB instance, I have
not done it.
"JTC ^..^" wrote:

>
> What are the results of DBCC CHECKTABLE sysindexes?
> --
> Regards
> JTC ^..^
>
|||Hi,
Try the below steps. If it fails restore from a good database backup.
Steps:
1. Create a new database with the same name and same MDF and LDF files
2. Stop sql server and rename the existing MDF to a new one and copy the
original MDF to this location and delete the LDF files.
3. Start SQL Server
4. Now your database will be marked suspect
5. Update the sysdatabases to update to Emergency mode. This will not use
LOG files in start up
Sp_configure "allow updates", 1
go
Reconfigure with override
GO
Update sysdatabases set status = 32768 where name = "BadDbName"
go
Sp_configure "allow updates", 0
go
Reconfigure with override
GO
6. Restart sql server. now the database will be in emergency mode
7. Create a new database and use DTS to copy the objects and data to new
database. You can use this new database.
Note:
If you have the backup file, it is always recommended to use the backup file
to restore the database. SO that data integrity will be maintained.
..
Thanks
Hari
SQL Server MVP
"vvenk" <vvenk@.discussions.microsoft.com> wrote in message
news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...[vbcol=seagreen]
> As I said, I don't have access to the source DB instance anymore. Since my
> understanding was that DBCC should be run on the source DB instance, I
> have
> not done it.
> "JTC ^..^" wrote:
|||Hari:
Thank you. When following the steps, when I tried to execute the statement,
Update sysdatabases set status = 32768 where name = "BadDbName"
I got an error, "Invalid column nam". However, I found what the dbid was for
that particular row and updated the row with that column in the Where clause.
I will now try to see if the data is accessible.
"Hari Prasad" wrote:

> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup file
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
>
>
|||Hari:
Also, I executed the statements after I was logged into master database; I
could not log onto the badDBName.
I hope that was fine.
Venki
"Hari Prasad" wrote:

> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup file
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
>
>
|||Hari:
Yes, the database is in emergency mode.
When I tried to create a DTS job to import, it does not show up in the list
of databases available as a source.
Any ideas?
venki
"Hari Prasad" wrote:

> Hi,
> Try the below steps. If it fails restore from a good database backup.
>
> Steps:
> 1. Create a new database with the same name and same MDF and LDF files
> 2. Stop sql server and rename the existing MDF to a new one and copy the
> original MDF to this location and delete the LDF files.
> 3. Start SQL Server
> 4. Now your database will be marked suspect
> 5. Update the sysdatabases to update to Emergency mode. This will not use
> LOG files in start up
>
> Sp_configure "allow updates", 1
> go
> Reconfigure with override
> GO
> Update sysdatabases set status = 32768 where name = "BadDbName"
> go
> Sp_configure "allow updates", 0
> go
> Reconfigure with override
> GO
> 6. Restart sql server. now the database will be in emergency mode
>
> 7. Create a new database and use DTS to copy the objects and data to new
> database. You can use this new database.
>
> Note:
> If you have the backup file, it is always recommended to use the backup file
> to restore the database. SO that data integrity will be maintained.
> ..
>
> --
> Thanks
> Hari
> SQL Server MVP
>
>
> "vvenk" <vvenk@.discussions.microsoft.com> wrote in message
> news:4EE00CBA-DB2F-4177-A5C2-B78DA315F97A@.microsoft.com...
>
>

error attaching .mdf

I have been asked to edit a web based database and have been given the site on cd.

I have installed IIS, sql server express and Visual Web Developer express.

I am having problems getting the mdf database connected. It works at the school where they have it installed and as far as I know I have mirrored the configuration they have on one of my test servers.

The database is in App_Data

the connection string is "Data Source=.\SQLEXPRESS;AttachDbFilename=c:\inetpub\wwwroot\App_Data\campbell.mdf;Integrated Security=True;User Instance=True"

And the state is closed.

When I view one of the aspx pages in IE I get the following.

Server Error in '/' Application.

---

Configuration Error

Description:An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message:It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.

Source Error:

Line 6: <compilation defaultLanguage="vb" debug="true" />Line 7: <customErrors mode="Off" />Line 8: <authentication mode="Windows" />Line 9: <trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" />Line 10: <sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa;password=" cookieless="false" timeout="20" />

Source File:c:\inetpub\wwwroot\app\campbell_house\web.config Line:8

The common error is:

"Error 1 It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. c:\inetpub\wwwroot\App\Campbell_House\Web.config 8 "

When I test the database connection I get a message

The header file for 'c:\inetpub\wwwroot\App_Data\campbell.mdf ' is not a valid database file header. The File Size property is incorrect. An attempt to attach an auto named database for file 'c:\inetpub\wwwroot\App_Data\campbell.mdf ' failed.A database with the same name existsor the specified file cannot be opened or it is located on a UNC share

Any help would be great.

Ok so I am pretty new to this but I am making progress. I had tried all afternoon and it wasn't until after I posted here that I had a brainwav.

Stage Two

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +173 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +199 System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +1069 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +606 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +193 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +501 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +429 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +70 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +510 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +85 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +89 System.Data.SqlClient.SqlConnection.Open() +160 CampbellHouse.CommonFunctions.GetConnection() +55 CampbellHouse.search.Page_Load(Object sender, EventArgs e) +347 System.Web.UI.Control.OnLoad(EventArgs e) +80 System.Web.UI.Control.LoadRecursive() +49 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3745

Once again, hope someon can help me out here.

|||

Hi,

I believe the cause of the problem is due to the web.config file being located in a folder that isn't marked in IIS as an application.

Your web.config currently appears to be located in:

c:\inetpub\wwwroot\app\campbell_house

It contains settings which ASP.NET requires being declared for the entire web application (e.g. the <authentication ...> section).

Try making 'campbell_house' an application using IIS management console.

Good luck :)

Wayne.

|||I'we got the same problem, might this be because i'aint got an Internet Connection at my Home?