Attached Db Successful In QA But Not Showing In EM
Nov 13, 2001
I used Query Analyser to De-tach a SQL 7 database and that worked fine. The database became 'invisible' in Enterprise Manager and the entry was removed from the sysdatabases in Master. The mdf and ldf file remain in the file system. However, when I ran the sp to Attach the database QA said successful but it does not show in Enterprise Manager or in sysdatabases in Master. I'm going to run through the procedure again and if problems I'll check the logs but has anyone else had difficulty with this. Also with attaching the db to a SQL2000 install I believe the logins on the SQL7 install are not brought over. In my case, the client is using trusted logins with their database application so their is probably not a lot to manually recreate on the SQL 2000 install but doees anyone have nay sample code/script that can give me an idea of what is required in the area of getting logins out of the Master of SQL7 and into SQL2000.
I attached my database to SQL 2005 but it's showing up as read-only for some reason. I've attached this before just fine in another instance of the Vista OS. Why would it attach differently this time compared to all other times and show read only?
The .mdb and .ldf files are not read only if you right-click and check out their properties.
I got the following error message when the scheduled DTS run for copiying the records from one server to another server.Actually it has copied successfully,but still returned this error?!There is a similar job on a different server doing the same thing returns a success message properly.?!! Thanks for any help.
''...ding... DTSRun: Executing... DTSRun OnStart: Create Table request124 Step DTSRun OnError: Create Table request124 Step, Error = -2147217900 (80040E14) Error string: There is already an object named 'request124' in the database. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 Error Detail Records: Error: -2147217900 (80040E14); Provider Error: 2714 (A9A) Error string: There is already an object named 'request124' in the database. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0 DTSRun OnFinish: Create Table request124 Step DTSRun OnStart: Copy Data from Results to request124 Step DTSRun OnProgress: Copy Data from Results to request124 Step; 10 Rows have been transformed or copied.; PercentComplete = 0; ProgressCount = 10 DTSRun OnFinish: Copy Data from Results to request124 Step DTSRun: Package execution complete. Process Exit Code 1. The step failed.''
I have a Job that runs a DTS package. This package in turns call several other packages. All individual packages run fines. When the main package is run manually it also runs fine. The jobs that calls the main package should be runnning for at least a couple of Hours maybe more and updtae several tables. It actually run nightly for only 20 minutes and doesn't update any tables. Yet it is in "successful"? Any thougts?
Hi. I am using VS 2005 and I want to create a database file (mdf) and have it on my server, but not have it attach to an instance of SQL server. Is this possible? The hosting I am using only allows for 1 SQL DB, and obviously doesn't allow you to attach instances of a DB. I would rather go with an mdf file that access, but not sure if this is possible. If anyone knows if it is and how to pull it off it would be GREAT!!
vb8 (in vs2005) generated the following connection string which works well in the vb8 application:
Data Source=.MyServerInstanceName;AttachDbFilename='C:MyDbPathMyDbName.mdf';Integrated Security=True
Within their own programs each connection string works well. However, if I use one program and then the other (e.g., vb8 program then vb6), I get an error message:
Unable to open the physical file "C:MyDbPathMyDbName.mdf". Operating system error 32: "32(The process cannot acces the file because it is being used by another process.)".
If I detach the database using SSMS, I can then access it with the other program. Obviously, this is not an ideal situation and not something I would want the end user to have to do.
Also, when using the vb6 connection string, SSMS lists the database in Object Explorer as: MyDbName. When using the vb8, the database is listed as C:MyDbPathMyDbName.mdf. BTW, the database is set for multi-user.
How can I get the two programs to place nice together?
Hi All,I have a DTS package that runs calling a few stored procedures and anactiveX module. The package does some data cleanup and load. It takesan hour to complete. I have emails sent at the beginning and end ofthe package execution along with error notifications if any of thestep fails.The issue is that, the DTS runs successfully. I ran the package fromthe server and it completes. If I schedule it, it has been running forover a few months without any issues. One fine day hell broke looseand it started to give an attitude!!When the job is invoked automatically on the scheduled time, it runsthe package. Does what its supposed to do including sending out thefinal email. but is not finishing the job. The job says its stillexecuting but the final step has completed. I have tried logging thepackage, and it says completed the last step.. But the JOB Log hasn'twritten anything to the log file.. (Job Log is where I am logging thestep where I am calling the DTS).Has anyone have any idea what this issue is? I am at a dead end andhave no clue why this is happening. I am thinking of changing thewhole process but before that I want to try posting this.Any ideas, suggestions will be much appreciated. Please feel free tolet me know if there is any additional information you need in orderto troubleshoot this issue.Thanks in advance..Aravin.
I have a standard Login ASP.NET 2.0 control on a login Page, a LoginName and LoginStatus controls on the member's page. once the user login successfully I am redirecting the user to Member.aspx page. The following is my machine configuration
Windows XP Pro Service Pack2 IIS 5.1 SQL Server 2000 visual Studio 2005 DISABLE ANONMYOUS ACCESS IN IIS ENABLE WINDOWS AUTHENTICATION
I am Using form authentication, and I am getting following error "Your login attempt was not successful. Please try again".
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head runat="server"> <title>Untitled Page</title> </head> <body> <form id="form1" runat="server"> <div> You are back ........ <asp:LoginName ID="LoginName1" runat="server" /> <asp:LoginStatus ID="LoginStatus1" runat="server" LogoutAction="Redirect" LogoutPageUrl="~/Login.aspx" />
</div> </form> </body> </html>
Member.aspx.cs
using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls;
public partial class Member : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { Response.Write("<br/>Page.User.Identity.Name: " + Page.User.Identity.Name); Response.Write("<br/>Page.User.Identity.IsAuthenticated: " + Page.User.Identity.IsAuthenticated); Response.Write("<br/>Page.User.Identity.AuthenticationType: " + Page.User.Identity.AuthenticationType);
Hi, I was trying to figure out how to back up a database that has been attached to the SQL Express instance. I found on the web this tutorial and tried to use it, however it seems like it cannot find the database. The DB is attached by the web application using AttachDbFilename in the connectionstring. http://www.sqldbatips.com/showarticle.asp?ID=27 Any ideas? thanks
If you re-attach a db to a different server, presumably you are shutting out your users (by them not having logins to the new server). If you are moving to a different domain I can only think that having the sa pwd and switching to "Mixed Authentication" would be the only way to get back in to start adding new logins/users, is that correct?
Is there a stored procedure to list attached databases? You can do this: use Master exec sp_helpfile go
Which shows you the config files for the current DB. What if you want to do a multiple sp_detach_db? If you could get a list of the attached DB's you could recursilvely or conditioinaly detach.
Hello all, I'm using SQL 2005 Express edition. I'm currently connecting to the database file directrly (from ASP.NET) and that db file is not attached to the server. My question is this: What is the difference ? Will the performance improve if the db is attached and I connect to it throught the server ? I'm really not sure what the difference is. Thanks
I need help getting all the users that are "attached" or "allowed" to access a given database and their login information. I do not know if this is even possible but I had tried to do my own research and cant figure it out/find any info on it. Any help is greatly appreciated!
Ok, here is the deal. In T-SQL, an error is handled depending on its severity. For example, a severity of 15 or less (or is it 10 or less? doesn't matter) will only raise a warning that can be caught through the message event. 16 or higher (or whatever) will cause an exception to be thrown on the .NET side, and 20 or higher causes the connection to be closed.So far so good.Now here's my issue: I have a stored procedure that does 2 queries (inside the same SP). Sometimes, the first query will succeed, while the second one will cause an error of severity 16. Again, in .NET that will throw an exception, making me unable to fetch the first resultset (which I require for logging purpose). If the error was, let say, severity 9, I could simply subscribe to the message event to get my error, yet still be able to get the first result set. But unfortunately life isn't perfect, and the error is indeed a severity 16.Anyone know of a way to be able to get the first result set, even if the second query (within the same SP) completly fails?
I'm running a pretty standard insert command on a button (myCommand.ExecuteNonQuery();) I have a few other methods that run, but I only want them to proceed if the above was inserted successfully, how would i check that?
After a successful transaction (after committing), I found that i sent wrong records of one the column (wrongly updated). How do I get back my initial stage? I mean, how do I get back all the previous results? Is there a way to retrieve my previous data which were before committing a transaction?
I've installed 2005 / RS on my testing server several times, no problem.
My production server throws an error when Reporting Services is installed. There are a few threads on this error:Microsoft SQL Server 2005 Reporting Services -- Error 29528. The setup has encountered an unexpected error while Setting reporting service and share point exclusion path. The error is: Fatal error during installation. I've Googled several similar complaints which discuss any of: Ensure IIS default web site is set to "All Unassigned" Ip[/*]Delete the RS Web services pool and retry[/*]Install RS separately[/*] The first two do nothing for the problem. While installing RS separately doesn't generate an error, it also doesn't create the RS databases.
Can the databases be created separately after installation?
I run XP Professional on a home machine. I recently installed VB 2003 with MSDE. When I go to the server explorer window, right click to add a connection, the Data Link properties dialog box pops up as it should. I select the name of home server, indicate integrated security, and select a sample database such as model or master from the list. The test connection is successful and clicking OK causes the connection to appear in the Server Explorer window. Yet when I go to open the connection, there is no data. The folders for Tables, Stored Procedures and so forth appear but they are empty. I have another 2000 database that a friend sent me. If I try to indicate in the Data Link propetries dialog box that I would like to attach this database, I get the same symptom. Test connection successful, yet when I create and open this connection, the folders are empty. I am a newbie to ADO .NET and I am not sure where to begin. Can someone help?
I keep receiving the error message below when I try to connect to SQL Management Studio
"A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)"
I have tried all of the suggestions in Google, in the forum, etc with not success.
I have enabled the
Named Pipe protocol/ Shared Memory protocol
SQL Server browser is enables
I even tried changing the SQL Server 2005 Shared Surface Configuration with no success.
I did not have this problem until the day light saving time change. I know this may having nothing to do with it but I need some help pronto.
In the error log I have the following error
Could not connect because the maximum number of '2' user connections has already been reached. The system administrator can use sp_configure to increase the maximum value. The connection has been closed. [CLIENT: <local machine>]
Error: 17809, Severity: 20, State: 1.
Not sure what to do or if the problems are related.
When you have SQL Server Express installed, and you drop a database in App_Code it will be attached and you can browse it with Server Explorer in Visual Studio. Same when you choose Website -> ASP.NET Configuration, you get a new ASPNETDB database in App_Code and it will be attached.My question: is it normal behaviour that I cannot see these databases in the Object Browser in SQL Server Management Studio?For the record: I also have SQL Server 2005 Dev installed, so the Management Studio I have is not the Express edition.
i'm building a web page to help our support staff run and export their sql queries faster and more easily than going through the sql server manager. i found an article at codeproject [1] that i was able to customize to be more flexible, but i'm not sure how to get it to export the results of a query along with the comments that preceed the query.
for example, i have the following sql file: -- this query does a certain thing, and the comment can be pretty long at times, depending on how complicated the query is select * from table where columnid > 100would anyone be able to tell me how to edit Kolluri's export function to allow for a comment section? alternatively if his way of doing an export is out of date, i'd be interested in a newer way. most importantly, though, i need to be able to export the comments along with query results.my ultimate goal is to have a drop down list of databases on the server, a list of query files (from a certain consolodated folder) for them to run on the chosen database, a "test query" function, and an export function that exports the comments and results.[1] http://www.codeproject.com/aspnet/ExportClassLibrary.asp
I attach my SQL Server Express data file to my host. I would like to copy all of my member information back to my local computer. How can I do this? My host won't allow my to physically copy the data file over. My host is discountasp.net. Thanks,Jeff
I need to get a unique value to use for a record *before* the record is added to a table. It doesn't have to be contiguous with existing records, but it must always be unique, has to be persistent over multiple instantiations of an ASP.NET application, and has to work in that sort of a multi-session environment (where other sessions could need additional unique values before the first session gets around to actually adding a record to the table).
I considered generating and using unique CLSIDs for this, but the resulting value also needs to become part of the filename of some files that are being saved to the disk (and those names also saved in the table), and including text CLSIDs along with other filename data would make for some unpleasantly long and difficult to work with filenames.
I also don't think there's a practical way for me to use a trigger associated with an identity column for this, because I need to save files to disk using the unique value before I even know if the record will in fact end up being added to the table, and what's more, the numbers and names of those files will vary in ways that might be difficult to handle in a stored procedure.
What I'm thinking I will have to do is create a separate database table called something like "UniqueIDGen". This table would have a single record in it with a single integer value, initialized to a value of 1. Then, each time an ID is needed, this one record would be locked, read and incremented by 1. The only reason for doing it this way instead of with an application variable, as I see it, is that the values need to be unique and continue incrementing in perpetuity, no matter how many times the ASP.NET application is recycled or the server is rebooted.
But I still have to wonder if there might be a more efficient method provided by SQL Server for this type of unique value generation ... something that is equally as persistent without requiring an entire table with only a single record to be allocated to such a basic task. Does anyone know of a more elegant solution for this?
I'm having some problems with SQL Server 2005. I installed the Personal Starter kit but don't have the Express edition installed so I attached the .mdf file to SQL Server 2005. That's ok and I also changed the connection string to integrated security.<add name="Personal" connectionString="Data Source=MyTestServer;Initial Catalog=Personal;Integrated Security=True" providerName="System.Data.SqlClient"/>I tried setting the security settings in the Management studio under Security | Logins | BUILTINAdministrators where I select the User mapping and check the checkbox before the Personal.mdf file. But this doesn't seem to do the trick. How can I set the correct security settings?
Hi, paws. My server crashed recently, I didn't give to much importance because I knew that having access to the partitions I could recover my DB files and attach my database to my new server, and everything was fine until ... I found that my DTS Packages and Jobs where not in my Attached DB. Now, where can I find these ? Can you help a tormented man ? Thanks in advance.
The upgrade to SQL 2k5 SP1 fails to upgraede the Database Services. Attached is the log. Will work for help.
05/24/2006 16:19:47.500 ================================================================================ 05/24/2006 16:19:47.500 Hotfix package launched 05/24/2006 16:19:53.687 Product discovery successfully completed during the install process for MSSQLSERVER 05/24/2006 16:19:53.687 SP Level check successfully completed during the install process for MSSQLSERVER 05/24/2006 16:19:53.687 Product language check successfully completed during the install process for MSSQLSERVER 05/24/2006 16:19:53.687 Product version check successfully completed during the install process for MSSQLSERVER 05/24/2006 16:19:53.687 Command-line instance name check completed during the install process 05/24/2006 16:19:53.687 Baseline build check completed during the install process 05/24/2006 17:08:03.187 Attempting to install instance: MSSQLSERVER 05/24/2006 17:08:03.281 Attempting to install target: TERRANCE 05/24/2006 17:08:03.375 Attempting to stop service: SQLSERVERAGENT 05/24/2006 17:08:11.093 Successfully stopped service: SQLSERVERAGENT 05/24/2006 17:08:11.109 Attempting to stop service: MSSQLServer 05/24/2006 17:08:18.625 Successfully stopped service: MSSQLServer 05/24/2006 17:08:19.031 Attempting to check for locked files: sqlrun_sql.msp 05/24/2006 17:08:21.390 Attempting to check for locked files: \TERRANCEe$6d48928b5baeb824319ba523e3fdHotFixSQLFilessqlrun_sql.msp 05/24/2006 17:08:21.406 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out 05/24/2006 17:09:22.343 MSP returned 1602: The user cancels installation. 05/24/2006 17:09:22.375 Successfully checked file: \TERRANCEe$6d48928b5baeb824319ba523e3fdHotFixSQLFilessqlrun_sql.msp 05/24/2006 17:09:22.468 Successfully opened registry key: SystemCurrentControlSetControlSession Manager 05/24/2006 17:09:22.468 Failed to read registry key: PendingFileRenameOperations 05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll 05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll 05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll 05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll 05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnlhtml.dll 05/24/2006 17:09:22.500 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll 05/24/2006 17:09:22.500 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe 05/24/2006 17:09:22.500 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll 05/24/2006 17:09:22.500 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe 05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll 05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll 05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll 05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll 05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll 05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL 05/24/2006 17:09:22.531 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll 05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll 05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplrec.dll 05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM plisapi.dll 05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:WINDOWSassemblyGAC_32Microsoft.SqlServer.Replication9.0.242.0__89845dcd8080cc91Repl.dll 05/24/2006 17:09:22.531 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll 05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources10332005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall plhtfin.sql 05/24/2006 17:09:22.531 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe 05/24/2006 17:09:22.546 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMsnapshot.exe 05/24/2006 17:09:22.546 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplmerg.exe 05/24/2006 17:09:22.546 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90COM ablediff.exe 05/24/2006 17:09:22.546 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe 05/24/2006 17:09:22.609 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe 05/24/2006 17:09:22.609 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources30822005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources2052sqlevn70.rll 05/24/2006 17:09:22.609 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10422005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1041sqlevn70.rll 05/24/2006 17:09:22.609 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10402005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1036sqlevn70.rll 05/24/2006 17:09:22.625 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10332005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1031sqlevn70.rll 05/24/2006 17:09:22.625 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10282005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033XPStar90.RLL 05/24/2006 17:09:22.625 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 05/24/2006 17:09:22.625 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 05/24/2006 17:09:22.625 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 05/24/2006 17:09:22.625 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn6.6.3.5 C:Program FilesMicrosoft SQL Server90Sharedmsxmlsql.dll 05/24/2006 17:09:22.640 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2.0.3609.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlrw.dll 05/24/2006 17:09:22.640 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 05/24/2006 17:09:22.640 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 05/24/2006 17:09:22.640 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 05/24/2006 17:09:22.640 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLBOOT.dll 05/24/2006 17:09:22.640 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxplog70.dll 05/24/2006 17:09:22.640 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnatchp~1.dll 05/24/2006 17:09:22.640 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 05/24/2006 17:09:22.671 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 05/24/2006 17:09:22.687 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 05/24/2006 17:09:22.703 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 05/24/2006 17:09:22.703 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 05/24/2006 17:09:22.718 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 05/24/2006 17:09:22.718 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90SharedResources10339.0.2047.0 C:Program FilesMicrosoft SQL Server90Sharedmsmdrdir.dll 05/24/2006 17:09:22.734 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0 C:Program FilesCommon FilesSystemole dbxmlrw.dll 05/24/2006 17:09:22.750 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 05/24/2006 17:09:22.750 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 05/24/2006 17:09:22.765 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 05/24/2006 17:09:22.781 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 05/24/2006 17:09:22.781 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 05/24/2006 17:09:22.796 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 05/24/2006 17:09:22.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 05/24/2006 17:09:22.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 05/24/2006 17:09:22.828 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 05/24/2006 17:09:22.859 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml 05/24/2006 17:09:22.875 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll 05/24/2006 17:09:22.875 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll 05/24/2006 17:09:22.875 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033 E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml 05/24/2006 17:09:22.890 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 05/24/2006 17:09:22.890 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 05/24/2006 17:09:22.906 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 05/24/2006 17:09:22.906 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 05/24/2006 17:09:22.921 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 05/24/2006 17:09:22.937 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 05/24/2006 17:09:22.953 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 05/24/2006 17:09:22.953 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 05/24/2006 17:09:22.968 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 05/24/2006 17:09:22.968 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0 E:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 05/24/2006 17:09:22.984 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0 E:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe 05/24/2006 17:09:22.984 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsvc~1.dll 05/24/2006 17:09:22.984 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 05/24/2006 17:09:23.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 05/24/2006 17:09:23.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 05/24/2006 17:09:23.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 05/24/2006 17:09:23.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 05/24/2006 17:09:23.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 05/24/2006 17:09:23.031 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe 05/24/2006 17:09:23.031 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0 C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll 05/24/2006 17:09:23.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll 05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL 05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL 05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll 05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll 05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll 05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll 05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll 05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll 05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlSAC.exe 05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedMicrosoft.SqlSac.Public.dll 05/24/2006 17:09:57.218 Attempting to install file: sqlrun_sql.msp 05/24/2006 17:09:57.609 Attempting to install file: \TERRANCEe$6d48928b5baeb824319ba523e3fdHotFixSQLFilessqlrun_sql.msp 05/24/2006 17:09:57.609 Creating MSP install log file at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log 05/24/2006 17:09:57.609 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 05/24/2006 17:09:57.609 Failed to read registry key: Debug 05/24/2006 17:15:25.375 MSP returned 1603: A fatal error occurred during installation. 05/24/2006 17:15:25.390 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 05/24/2006 17:15:25.406 Failed to read registry key: Debug 05/24/2006 17:15:25.593 Unable to install MSP file: \TERRANCEe$6d48928b5baeb824319ba523e3fdHotFixSQLFilessqlrun_sql.msp 05/24/2006 17:15:25.593 The following exception occurred: Unable to install Windows Installer MSP file Date: 05/24/2006 17:15:25.593 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 856 05/24/2006 17:15:25.937 05/24/2006 17:15:25.937 Product Status Summary: 05/24/2006 17:15:25.937 Product: SQL Server Native Client 05/24/2006 17:15:25.953 SQL Server Native Client (RTM ) - Success 05/24/2006 17:15:25.953 05/24/2006 17:15:25.953 Product: Setup Support Files 05/24/2006 17:15:25.953 Setup Support Files (RTM ) - Success 05/24/2006 17:15:25.953 05/24/2006 17:15:25.953 Product: Database Services 05/24/2006 17:15:25.953 Database Services (RTM 1399 ENU) - Failure 05/24/2006 17:15:25.953 Details: Unable to install Windows Installer MSP file 05/24/2006 17:15:25.953 Analysis Services (SP1 2047 ENU) - Not Applied 05/24/2006 17:15:25.953 Reporting Services (SP1 2047 ENU) - Not Applied 05/24/2006 17:15:25.953 05/24/2006 17:15:25.953 Product: Notification Services 05/24/2006 17:15:25.953 Notification Services (SP1 2047 ENU) - Not Applied 05/24/2006 17:15:25.953 05/24/2006 17:15:25.953 Product: Integration Services 05/24/2006 17:15:25.953 Integration Services (SP1 2047 ENU) - Not Applied 05/24/2006 17:15:25.968 05/24/2006 17:15:25.968 Product: Client Components 05/24/2006 17:15:25.968 Client Components (SP1 2047 ENU) - Not Applied 05/24/2006 17:15:25.968 05/24/2006 17:15:25.968 Product: MSXML 6.0 Parser 05/24/2006 17:15:25.968 MSXML 6.0 Parser (RTM ) - Not Applied 05/24/2006 17:15:25.968 05/24/2006 17:15:25.968 Product: SQLXML4 05/24/2006 17:15:25.968 SQLXML4 (RTM ) - Not Applied 05/24/2006 17:15:25.968 05/24/2006 17:15:25.968 Product: Backward Compatibility 05/24/2006 17:15:25.968 Backward Compatibility (RTM ) - Not Applied 05/24/2006 17:15:25.968 05/24/2006 17:15:25.968 Product: Microsoft SQL Server VSS Writer 05/24/2006 17:15:25.968 Microsoft SQL Server VSS Writer (RTM ) - Not Applied 05/24/2006 17:15:25.984
I attached .mdf and .ldf from the app_data folder in an asp.net web site. I set the configuration to SSPI. The trouble is, I get this error requested by the login. The login failed. Login failed for user 'IN-XYZmattaniah'.
If I create a database and connect to it using SSPI I do not get this error. I assume there is something I am missing.
