You searched for the word(s): userid:630829

More Search Options

RSS Available

• Re: An attempt to attach an auto-named database for file <file string> failed....BUT ONLY due to new SSE install

  RESOLVED: DOH! When I rebuilt the OS I changed the Partition ID's on the data partitions....which threw off the connection strings. Not great, but better than continuing to bang head against wall....

  Posted to Getting Started (Forum) by codequest on 9/17/2007

• Re: An attempt to attach an auto-named database for file <file string> failed....BUT ONLY due to new SSE install

  Ok, I found the security tab...I'll try changing the permissions... Changed the permissions for the folder and for each of the .mdf's (and log files) in the folder.... No change in the error message... Also had no problem opening the DB in SSMSE; or in VS2005 Server Explorer; so it probably is something between SSE and ASPNET. No problem opening .aspx pages in IIS. Unless there's something in IIS that connects the SQL Server to ASP.NET? But then, the same problem occurs with Cassini.

  Posted to Getting Started (Forum) by codequest on 9/16/2007

• Re: An attempt to attach an auto-named database for file <file string> failed....BUT ONLY due to new SSE install

  Thanks for the input. That relates to issues I've had around this when I first set it up. One of the problems that I've got with this is that when I open the folder properties, it doesn't have a security tab. I'm using XP Pro, and I'm not sure where to get the security tab in order to try giving that permission. The other thing is that while I have to set the file permissions for the same .mdf's on my hosted site to "everyone, full" (I went through this with Microsoft

  Posted to Getting Started (Forum) by codequest on 9/16/2007

• An attempt to attach an auto-named database for file <file string> failed....BUT ONLY due to new SSE install

  I built an app, works fine. Had the development environment working fine (VS2005 (SP0) and SQL Server Express). It had been stable for months, no problem. Then I had to reinstall XP Pro...(finally threw too many conflicting programs into it, I guess...) I managed to get VS2005 reinstalled ok. However, when I opened and compiled my existing app in VS2005, using Cassini, I got the dreaded error: An attempt to attach an auto-named database for file <file string> failed. A database with the same

  Posted to Getting Started (Forum) by codequest on 9/16/2007

• Re: web.config, app.config Connection strings

  Big help! Problem was bugging me through several instances of updating the DS...easy solution, makes sense. I summarize as: 1) delete the AppSettingsObjectName version of the connectionstring (or the other one) 2) use the properties window to re-add the connectionstring to the TA's that need it

  Posted to Configuration and Deployment (Forum) by codequest on 6/27/2007

• Re: Error using DB name in Stored Procedure

  Thanks for the message. Flexibility to use multiple DB's in an ASP.NET app would seem to be a critical requirement for the tool. I'm surprised there isn't a better known solution to this need. At this point, however, I've built VB code to get around the cross-db table joins, so I'm not going to pursue this except as potentially valuable in the future. Tak!

  Posted to Getting Started (Forum) by codequest on 6/13/2007

• Re: Error using DB name in Stored Procedure

  Tried a simple test case of publishing and using a different connectionstring path to the long DB name, but couldn't get it to work...

  Posted to Getting Started (Forum) by codequest on 6/12/2007

• Re: Error using DB name in Stored Procedure

  That is, is [E:\Folder\Folder\APP_DATA\DB2.mdf] now just a string name used by SQL Server that isn't used as a file path..."that .mdf file" is whatever the web.config connection string points to and says it's "that .mdf file".....?

  Posted to Getting Started (Forum) by codequest on 6/12/2007

• Re: Error using DB name in Stored Procedure

  Thanks for input. SELECT t1.ID FROM [E:\Folder\Folder\APP_DATA\TESTDB.MDF].dbo.Table1 AS t1 INNER JOIN [E:\Folder\Folder\APP_DATA\DB2.mdf].dbo.Tab2 AS t2 ON t1.ID = t2.ID2 gets converted in the Query builder into SELECT t1.ID FROM Table1 AS t1 INNER JOIN [E:\Folder\Folder\APP_DATA\DB2.mdf].dbo.Tab2 AS t2 ON t1.ID = t2.ID2 but then it does execute, so that's a great piece of information. However, I'm trying to figure out how the stored procedure is going to work if the database is moved to

  Posted to Getting Started (Forum) by codequest on 6/12/2007

• Error using DB name in Stored Procedure

  Having problems using DB name in store procedure, VS2005 no SP1 / SQL Express. Built a test web site in VS2005, added SQL DB TESTDB, added Table1, added column ID Built stored procedure SELECT ID FROM dbo.Table1 AS t1 which works, but SELECT ID FROM TESTDB.dbo.Table1 AS t1 gives error "invalid object name TESTDB.dbo.Table1" TESTDB is connected in VS2005 Server Explorer when the test is run. One possible problem is that in VS2005 Server Explorer Properties for TESTDB, the 'Name'

  Posted to Getting Started (Forum) by codequest on 6/12/2007