Hi!I am trying to insert into a sql server 2000 enterprise edition database from a .net application. but I keep getting the error server doesnot exist or access denied. I can connect to the server from query analyzer and sql manager. The database is running on windows 2003. The only thing I don't see is the ASPNET sys account not on the login database. I don't know how to add that.
Here is the connection string that I have always used and worked before.
Network Library=DBMSSOCN; Data Source=DEVELOPERS,1433; Initial Catalog=CMLTODB;User ID=sa;Password=password
HiI'm trying to port some data from one database table to anotherdatabase table on the same server.This is the query I am using:----->INSERT into newdatabase.dbo.contactevents (EventTypeID, UserID,ContactID, DateEntered, EventDate, Description)select '20','1', ContactID, '1/1/2005 00:00', '1/1/2005 00:00',ISNULL(Notes,'')from olddatabase.dbo.contacteventsWHERE Exists (SELECT ContactID FROM newdatabase.dbo.contacts)<-------This is the error I'm getting:----->INSERT statement conflicted with COLUMN FOREIGN KEY constraint'FK_ContactEvents_Contacts'. The conflict occurred in database'newdatabase', table 'Contacts', column 'ContactID'.The statement has been terminated.<-------There is a relationship between the contacts table (Primary keyContactID) and the contactsevent (foreign key ContactID) table. I guessthe error being flagged up here is that some contacts don't exist inthe new database, therefore referential intergretory won't allow itbeing copied. I thought I could get around this using:"WHERE Exists (SELECT ContactID FROM newdatabase.dbo.contacts)"Note I've also tried:"WHERE Exists (SELECT * FROM newdatabase.dbo.contacts)"What am I doing wrong?Many Thanks!Alex
Hi i am trying to bulk insert records from flat file to sql table, but i am getting the following error
Error: 0xC002F304 at Bulk Insert Task, Bulk Insert Task: An error occurred with the following error message: "Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)".The OLE DB provider "BULK" for linked server "(null)" reported an error. The provider did not give any information about the error.Cannot bulk load because the maximum number of errors (10) was exceeded.". Task failed: Bulk Insert Task
Trying to insert a row via Enterprise Manager I get "object does not exist" error.. However it works on another server?!?
The table name is aa.aabc .. So i know what the problem is.. it thinks that aa is the owner.. I can insert using query analyzer by using the following syntax: insert into [aa.aabc] ... but it fails using: insert into aa.abc .. for obvious reasons..
I'm guessing it has something to do with the differences in the server config between the 2 servers as to why one server you can insert via enterprise manager and the other you cant..
The collation is different as the ANSI warning and padding in the connection info..
Can anyone else help me fix this problem, so that I can insert using enterprise manager?
I am trying to insert a row into a table using a stored procedure and Iget the following error if I try this from QA:INSERT failed because the following SET options have incorrectsettings: 'ANSI_NULLS., QUOTED_IDENTIFIER'.If I try to run this from Microsoft Access, I get a slightly differenterror:INSERT failed because the following SET options have incorrectsettings: 'ANSI_NULLS., QUOTED_IDENTIFIER, ARITHABORT'.This is what I'm trying to run in QA:declare @P1 intset @P1=NULLexec stpAddNewDistributionMaster 142, 2, 'INTRODUCTION OF FILTERASSEMBLY', 0, 1, @P1 outputselect @P1===========================Here are the relevant definitions:TABLE:CREATE TABLE [dbo].[tblDistributionMaster] ([fldDistributionID] [int] IDENTITY (1, 1) NOT NULL ,[fldDocumentID] [int] NULL ,[fldDocumentType] [int] NULL ,[fldDocumentTitle] [varchar] (255) COLLATESQL_Latin1_General_CP1_CI_AS NULL ,[fldDocumentSiteID] [int] NULL ,[fldActive] [bit] NOT NULL) ON [PRIMARY]GOALTER TABLE [dbo].[tblDistributionMaster] WITH NOCHECK ADDCONSTRAINT [DF__Temporary__fldDo__2739D489] DEFAULT (0) FOR[fldDocumentID],CONSTRAINT [DF__Temporary__fldDo__282DF8C2] DEFAULT (0) FOR[fldDocumentType],CONSTRAINT [DF__Temporary__fldDo__29221CFB] DEFAULT (0) FOR[fldDocumentSiteID],CONSTRAINT [DF__Temporary__fldAc__2A164134] DEFAULT (1) FOR[fldActive],CONSTRAINT [aaaaatblDistributionMaster_PK] PRIMARY KEY NONCLUSTERED([fldDistributionID]) WITH FILLFACTOR = 90 ON [PRIMARY]GOCREATE INDEX [fldDistributionID] ON[dbo].[tblDistributionMaster]([fldDistributionID]) WITH FILLFACTOR =90 ON [PRIMARY]GOCREATE INDEX [fldDocumentID] ON[dbo].[tblDistributionMaster]([fldDocumentID]) WITH FILLFACTOR = 90 ON[PRIMARY]GOCREATE INDEX [fldDocumentSiteID] ON[dbo].[tblDistributionMaster]([fldDocumentSiteID]) WITH FILLFACTOR =90 ON [PRIMARY]GOCREATE INDEX [fldDocumentType] ON[dbo].[tblDistributionMaster]([fldDocumentType]) WITH FILLFACTOR = 90ON [PRIMARY]GO/****** The index created by the following statement is for internaluse only. ******//****** It is not a real index but exists as statistics only. ******/if (@@microsoftversion > 0x07000000 )EXEC ('CREATE STATISTICS [hind_37575172_1A_3A] ON[dbo].[tblDistributionMaster] ([fldDistributionID], [fldDocumentType])')GO/****** The index created by the following statement is for internaluse only. ******//****** It is not a real index but exists as statistics only. ******/if (@@microsoftversion > 0x07000000 )EXEC ('CREATE STATISTICS [hind_37575172_3A_1A] ON[dbo].[tblDistributionMaster] ([fldDocumentType], [fldDistributionID])')GO/****** The index created by the following statement is for internaluse only. ******//****** It is not a real index but exists as statistics only. ******/if (@@microsoftversion > 0x07000000 )EXEC ('CREATE STATISTICS [hind_37575172_2A_1A] ON[dbo].[tblDistributionMaster] ([fldDocumentID], [fldDistributionID]) ')GO/****** The index created by the following statement is for internaluse only. ******//****** It is not a real index but exists as statistics only. ******/if (@@microsoftversion > 0x07000000 )EXEC ('CREATE STATISTICS [hind_37575172_3A_2A] ON[dbo].[tblDistributionMaster] ([fldDocumentType], [fldDocumentID]) ')GO/****** The index created by the following statement is for internaluse only. ******//****** It is not a real index but exists as statistics only. ******/if (@@microsoftversion > 0x07000000 )EXEC ('CREATE STATISTICS [hind_37575172_2A_3A] ON[dbo].[tblDistributionMaster] ([fldDocumentID], [fldDocumentType]) ')GO/****** The index created by the following statement is for internaluse only. ******//****** It is not a real index but exists as statistics only. ******/if (@@microsoftversion > 0x07000000 )EXEC ('CREATE STATISTICS [hind_37575172_1A_2A_3A] ON[dbo].[tblDistributionMaster] ([fldDistributionID], [fldDocumentID],[fldDocumentType]) ')GOSET QUOTED_IDENTIFIER ONGOSET ANSI_NULLS ONGOCREATE TRIGGER "tblDistributionMaster_UTrig" ONdbo.tblDistributionMaster FOR UPDATE ASSET NOCOUNT ON/* * PREVENT UPDATES IF DEPENDENT RECORDS IN 'tblJobs' */IF UPDATE(fldDistributionID)BEGINIF (SELECT COUNT(*) FROM deleted, tblJobs WHERE(deleted.fldDistributionID = tblJobs.fldDistributionID)) > 0BEGINRAISERROR 44446 'The record can''t be deleted orchanged. Since related records exist in table ''tblJobs'', referentialintegrity rules would be violated.'ROLLBACK TRANSACTIONENDENDGOSET QUOTED_IDENTIFIER OFFGOSET ANSI_NULLS ONGOSET QUOTED_IDENTIFIER ONGOSET ANSI_NULLS ONGOCREATE TRIGGER "tblDistributionMaster_DTrig" ONdbo.tblDistributionMaster FOR DELETE ASSET NOCOUNT ON/* * CASCADE DELETES TO 'tblJobs' */DELETE tblJobs FROM deleted, tblJobs WHERE deleted.fldDistributionID =tblJobs.fldDistributionIDGOSET QUOTED_IDENTIFIER OFFGOSET ANSI_NULLS ONGO===========================SPROC:CREATE PROCEDURE stpAddNewDistributionMaster@DocumentID int,@DocumentType int,@Title varchar(255),@SiteID int,@Active bit,@DistributionID int OUTPUTASINSERT INTO tblDistributionMaster(fldDocumentID,fldDocumentType,fldDocumentTitle,fldActive,fldDocumentSiteID)VALUES(@DocumentID,@DocumentType,@Title,@Active,@SiteID)SET @DistributionID = IDENT_CURRENT('tblDistributionMaster')GO==============================Thanks in advanceEdward
I?m getting an error when I execute a stored procedure which is try to insert a row to a table.The error is:Server: Msg 1934, Level 16, State 1, Procedure SRV_SP_IS_EMRI_SATIRI_EKLE, Line 32INSERT failed because the following SET options have incorrect settings: 'ANSI_NULLS.'.In my sp, I insert an row to a table. But also I created a view which is select some fields from this table.(Note: Some fields are calculated fields in this view. To see if calculated fields cause this error , I didnt selec calculated fields in the view, but I?m still getting this insert error.One more note: My indexed field is an identity field also.) I think, index causes this error. But I cant find my error.Thank you for your help...To do this view, I execute this code:drop view SRV_V_GARANTILI_IS_EMRI_SATIRLARI_TgoCREATE VIEW dbo.ViewTwith SCHEMABINDING ASSELECTS.FieldA,....S. FieldHFROMdbo.TABLE SWHERE(S.FieldA = 1) AND (S. FieldB IS NULL) AND (S.FieldH IN (0,1))goSET NUMERIC_ROUNDABORT OFFGOSET ANSI_PADDING,ANSI_WARNINGS,CONCAT_NULL_YIELDS_NULL ,ARITHABORT,QUOTED_IDENTIFIER,ANSI_NULLS ONGOcreate unique clustered index ViewT_IX_FieldA on ViewT (FieldA)go****************************************** This message was posted via http://www.sqlmonster.com** Report spam or abuse by clicking the following URL:* http://www.sqlmonster.com/Uwe/Abuse...d4cddba67ade8b6*****************************************
Wrote this snipet of code to use Insert Into. I have an ODBC connection to Oracle with the Tables linked. I can edit, add write querries and do everything I need to do except do an Insert Into. So I am thinking it is my code and seeking guidance.
I select add data from a button on the form. It then calls the code below. I know it is making it up to the db.execute statement and failing at that point. Funny thing is I only get the error "ODBC Call Failed" and no other snippets of information. On top of that I can not relink to the tables as they are now unaccessible and I have to completely close down the program and restart. Any help/assistance will be greatly appreciated. Thank you, Here is the code:
Code Start:
Private Sub btn_add_rca_record_Click() On Error GoTo Err_btn_add_rca_record_Click Dim db As Database Dim rsCust As Recordset Dim strSQL As String Dim nbrRcaTicketId As Long
The reason why cust_id started at #4 and not #1 is because I failed to insert property three times in a row for having "Tatoine" instead of "WI" or a state less than 5chars nchar(5) correct? Then when I did a valid statement, the row was created at the starting number of four. I imagine this prevents users from having duplicate cust_ids. This however is also where rollback and similar commands could be handy correct or is there something more obvious I'm missing on a failed "insert into" to not increment the cust_id. The three rows 1,2 and 3 do not exist I believe and are not null. Â Having null values would of contradicted the table where two columns "not null" are a requirement.
I have the folowing problem that I could use some help with :
I have an SQL server database acting as a back end to an access dbase. The SQL srv table contains over 32 million records and I am trying to use an append query (in access) to import a further 2 million records to the SQLSRV table. The append query fails with the message 'Insert on table bcdsales failed' followed by an ODBC timeout error message. I can append one record fine but a mass import fails.
Unfortunately i can't use SQL srv to do the import (internal policy says we must stick with access front end for now).
One of my database transaction log backup jobs failed this morning, although the log backup was still taken, the job reported failure. The job has run successfully a number of times since. The job reported a primary key violation error on the msdb.dbo.backupmediaset table. The full error message was
Violation of PRIMARY KEY constraint 'PK__backupme__DAC69E4D599F1693'. Cannot insert duplicate key in object 'dbo.backupmediaset'. The duplicate key value is (401862). Msg 3009, Level 16, State 1, Server myservername, Line 1
Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful.
After investigating the backupset and backupmediaset tables in msdb I can see that value used for the failed insert was used previously for the last database log backup in the previous log backup run. The failure was reported for the first database log backup attempted. The SQL Log shows an entry for the log being backed up successfully.
I have checked the identify value in the backupmediaset table using DBCC CHECKIDENT and all looks OK.
I am currently running the following query from Query Analyser, I am connected to Server_A and inserting records into Server_B.Database_B.dbo.MyTable from Server_A .Database_A.dbo.TableRef
Insert into Server_B.Database_B.dbo.MyTable(Field1,Field2,Field3) Select Field1_Ref,
Field2_Ref, Field3_Ref from Server_A .Database_A.dbo.TableRef
However Server_B.Database_B.dbo.MyTable is referenced within an Indexed View and whenever I run this query I get the following error:
Msg 1934, Level 16, State 1, Line 1
INSERT failed because the following SET options have incorrect settings: 'ARITHABORT'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or query notifications and/or xml data type methods.
I have tried setting ARITHABORT to ON & OFF within the Query and within the database properties but still recieve the same error.
Does anyone have any ideas on why this would not work?
So, I've written an Instead of Trigger to update a foreign key field based on information in another field of the same record.
To add some error handling to the process I updated the Trigger to insert any records that don't have legitimate foreign keys into a second table.
This process works great when I test it by just adding a record using the table view in the SQL Management Studio or through a query run in the query browser.
However, when a record is added via an ODBC connection I get foreign key constraint errors and records are not added to the second table. If the foreign key is legit the record is added and the part of trigger that updates that keyed field executes just fine.
Is anyone aware of this issue? Is there a way around it?
I found the following MSKB article but I'm not sure if it applies to my situation: http://support.microsoft.com/kb/304096
Here's my current code, if that track the problem in anyway:
Code:
ALTER TRIGGER UpdateTicketID ON Email Instead of INSERT AS IF ((Select charindex('{', [subject]) FROM Inserted) = 0) BEGIN INSERT INTO BadEmail ([Subject], Sender, Body, EntryID, LastModificationTime, AttachmentLInk, SendTo, Cc, ContactID) Select [Subject], Sender, Body, EntryID, LastModificationTime, AttachmentLink, SendTo, Cc, ContactID From Inserted END ELSE IF ((Select substring([subject], charindex('{', [subject])+1, (charindex('}', [subject]) - charindex('{', [subject]))-1) From Inserted) NOT In (Select TicketID From Ticket)) BEGIN INSERT INTO BadEmail ([Subject], Sender, Body, EntryID, LastModificationTime, AttachmentLInk, SendTo, Cc, ContactID) Select [Subject], Sender, Body, EntryID, LastModificationTime, AttachmentLink, SendTo, Cc, ContactID From Inserted END ELSE BEGIN INSERT INTO Email ([Subject], Sender, Body, ticketID, EntryID, LastModificationTime, AttachmentLink, SendTo, Cc, ContactID) Select [Subject] , Sender , Body , substring([subject], charindex('{', [subject])+1, (charindex('}', [subject]) - charindex('{', [subject]))-1) , EntryID , LastModificationTime , AttachmentLink , SendTo , Cc , ContactID From Inserted END
Hi,I'm new at asp .net and am having a problem. On a linkbutton click event, I want to insert into my db a row of data which includes two parameters. Param1 is the id of the logged in user, and Param2 is <%#DataBinder.Eval(Container.DataItem, 'UserId')%> which is the username of a user given through a datalist.When I execute the query: "insert into aspnet_friendship (userId, buddyId) values (@Param1, @Param2)"I get the error: Conversion failed when converting from a character string to uniqueidentifier.I am trying to insert these into my table aspnet_friendship into the columns userId and buddyId which are both uniqueidentifier fields. I tested the query using the same values (@Param1, @Param1) and (@Param2, @Param2) and found out that the problem is with Param2 because when I use Param1 the insert works perfectly. The value passed by Param2 is supposed to be the id of a user which I get from the datalist which selects * from aspnet_Users, so that <%#DataBinder.Eval(Container.DataItem, 'UserId')%> should also be an Id like Param1 is. Since both params are in the form of .toString(), I don't understand why one works but the other doesn't.As you can see in the code below, both of these parameters are dimmed as strings, so I don't understand why Param2 doesn't work. Can anyone please help? Protected Sub LinkButton1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Dim MyConnection As SqlConnection MyConnection = New SqlConnection("Data Source=.SQLEXPRESS;AttachDbFilename=|DataDirectory|ASPNETDB.MDF;Integrated Security=True;User Instance=True") Dim MyCommand2 As SqlCommand Dim CurrentUser As String CurrentUser = Membership.GetUser.ProviderUserKey.ToString() Dim add As String add = "<%#DataBinder.Eval(Container.DataItem, 'UserId')%>".ToString() Session("username") = User.Identity.Name Dim InsertCmd As String = "insert into aspnet_friendship (userId, buddyId) values (@Param1, @Param2)" MyCommand2 = New SqlCommand(InsertCmd, MyConnection) MyCommand2.Parameters.AddWithValue("@Param1", CurrentUser) MyCommand2.Parameters.AddWithValue("@Param2", add) MyCommand2.Connection.Open() MyCommand2.ExecuteNonQuery() MyCommand2.Connection.Close() End Sub Thank you.
I get this error when trying to alter a stored procedure that has an insert statement referencing a new linked server I created:
INSERT INTO [servername].databasename.dbo.DirectReport ...
Msg 18456, Level 14, State 1, Procedure Get_Direct_Pay_Move_Data, Line 17 Login failed for user 'NT AUTHORITYANONYMOUS LOGON'.
I added Administrators and my logon to the permissions of my linked server but still get this error when it tries to save my stored proc...the one which has that insert.
I've built SSIS package and made a job to execute it automatically but it always returns an error. The job returns OK but when we looked at the Log File viewer, it conatins this error log :
Key not valid for use in specified state
Failed to decrypt protected XML node "DTS Password" with error
What's wrong with the package ? Thanks in advance.
I wrote an application using Visual Studio 2005 beta 2 which uses a SQL Express .mdf file, included in the project, for the database. After installing Visual Studio 2005 RC and the SQL Express that comes with it (I followed all of the uninstall instructions first) I can no longer add a SQL Express database to any of my projects, nor can I open the SQL Express database in my original project. When I try either of these tasks, I get the "Failed to generate user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed." I read the thread which dealt with this error, and changed the connection string for the database file that had worked before to User Instance = false. The moment I click Test Connection or OK, I get the error: "An attempt to attach an auto-named database for file C:<path to project>EngSQL.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share." (<path to project> is actually a full path, I didn't want to type the whole thing out. :) ). A search for this error turns up a solution of setting User Instance = false, which puts me in a catch 22 position.
I have log shipping set up between 2 SQL 2000 SP1 Servers on Win 2000. The db is small 10 meg, and when the restore job on the backup server fails I am getting "sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed." as the message, the maint paln on the primary server show no error. Anyone seen this before? The restore has worked 3 out of 5 times
Many a times see the below error in SQL Error log.
Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: ]
Is this something to do here?
Note: If I run the below statement I know that the SQL Error log entry will go off, but wanted to know the real significance of this error?
CREATE LOGIN [NT AUTHORITYANONYMOUS LOGON] FROM WINDOWS
I am administering several SQL Servers running SQL Server 2005 SP2 Build 3042. I have a common maintenance plan that runs on each of the servers. The maintenance plan runs fine on all the servers except for one. On the one server the Database Integrity check fails with the following error:
Check Database integrity on Local server connection Databases: <list of databases> Include indexes Task start: 2008-02-21T00:05:42. Task end: 2008-02-21T00:05:46. Failed0) Alter failed for Server €˜XYZ€™
I created a test maintenance plan to just do the integrity check and selected one database only and this also failed with the same error message. I ran this test maintenance plan and configured it for each of the databases in question and it failed each time. If I run the DBCC manually against the databases they all report fine.
I read some of the post that talked about the €œAllow Updates€? being set incorrectly but that does not apply to my problem since my configured and run values are set to 0.
I have a re-indexing stored procedure,yester day night it got failed "Executed as user: CONNECTSRVmyadmin. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed." what may be the reason..
[Source - chn_employee_vew_test_txt [1]] Error: Data conversion failed. The data conversion for column "Column 42" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
[Source - chn_employee_vew_test_txt [1]] Error: The "output column "Column 42" (136)" failed because truncation occurred, and the truncation row disposition on "output column "Column 42" (136)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
I using Locale (People's Republic of China) and code page of 936 (Simplied Chinese GBK) with header row delimiter {CR}{LF}.
I am using flat file import method.
Whenever the server process the Column 42 with value "11,Nanjing Rd.W, China" which contain 'comma' or '.' it will hit error importing with above message. When i manually change the column value to non comma or '.' (11 Nanjing Rd W China) in the flat file it is ok.
I am using SQL server 2005.
Please advise what need to be done to avoid this error ?
Thanks in advance and any idea or suggestion is very much appreciated as i have try to solve this issue for over a week but still not able to find any answer on it.
I am running the Sept CTP. I have created a SSIS package that pulls data from a text file and inserts into a database. When I run the package on the DB server it runs fine. I have moved the package the the web server (we are attempting to kick off the package from a web site) and we get connections errors. We are running the package using dtexec from the command line.
[Source - chn_employee_vew_test_txt [1]] Error: Data conversion failed. The data conversion for column "Column 42" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
[Source - chn_employee_vew_test_txt [1]] Error: The "output column "Column 42" (136)" failed because truncation occurred, and the truncation row disposition on "output column "Column 42" (136)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
I using Locale (People's Republic of China) and code page of 936 (Simplied Chinese GBK) with header row delimiter {CR}{LF}.
I am using flat file import method.
Whenever the server process the Column 42 with value "11,Nanjing Rd.W, China" which contain 'comma' or '.' it will hit error importing with above message. When i manually change the column value to non comma or '.' (11 Nanjing Rd W China) in the flat file it is ok.
I am using SQL server 2005.
Please advise what need to be done to avoid this error ?
Thanks in advance and any idea or suggestion is very much appreciated as i have try to solve this issue for over a week but still not able to find any answer on it.
when i right click and execute the package from the Management Studio, it runs fine, everytime. When i schedule a job to execute it, it fails, everytime.
"The package execution failed. The step failed."
i have made sure that the package and job ran using credentials with more than enough access to everything. Still, with no luck. PLEASE! I am at my wits ends here, and the boss is getting antsey...
Im trying to installed SQL SP1 and I get 'cancelled' status on the Database Services product.
If I open the SQL9_Hotfix_KB913090.log I see a bunch of 'Failed to read" errors. Im not very good at debugging SQL Logs, could you please assists me or tell me where to look?
02/15/2007 15:09:58.436 ================================================================================ 02/15/2007 15:09:58.436 Hotfix package launched 02/15/2007 15:09:59.405 Product discovery successfully completed during the install process for MSSQLSERVER 02/15/2007 15:09:59.405 SP Level check successfully completed during the install process for MSSQLSERVER 02/15/2007 15:09:59.421 Product language check successfully completed during the install process for MSSQLSERVER 02/15/2007 15:09:59.421 Product version check successfully completed during the install process for MSSQLSERVER 02/15/2007 15:09:59.421 Command-line instance name check completed during the install process 02/15/2007 15:09:59.421 Baseline build check completed during the install process 02/15/2007 15:10:21.892 Attempting to install instance: MSSQLSERVER 02/15/2007 15:10:21.892 Attempting to install target: DEV08 02/15/2007 15:10:21.892 Attempting to stop service: SQLSERVERAGENT 02/15/2007 15:10:25.893 Successfully stopped service: SQLSERVERAGENT 02/15/2007 15:10:25.893 Attempting to stop service: MSSQLServer 02/15/2007 15:10:27.893 Successfully stopped service: MSSQLServer 02/15/2007 15:10:27.893 Attempting to check for locked files: sqlrun_sql.msp 02/15/2007 15:10:27.909 Attempting to check for locked files: \DEV08D$KitsSQL2005_StandardSP1HotFixSQLFilessqlrun_sql.msp 02/15/2007 15:10:27.909 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out 02/15/2007 15:10:39.520 MSP returned 1602: The user cancels installation. 02/15/2007 15:10:39.567 Successfully checked file: \DEV08D$KitsSQL2005_StandardSP1HotFixSQLFilessqlrun_sql.msp 02/15/2007 15:10:39.567 Successfully opened registry key: SystemCurrentControlSetControlSession Manager 02/15/2007 15:10:39.567 Failed to read registry key: PendingFileRenameOperations 02/15/2007 15:10:39.567 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll 02/15/2007 15:10:39.567 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll 02/15/2007 15:10:39.567 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnlhtml.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll 02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplrec.dll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM plisapi.dll 02/15/2007 15:10:39.598 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 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources10332005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall plhtfin.sql 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMsnapshot.exe 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplmerg.exe 02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90COM ablediff.exe 02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources30822005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources2052sqlevn70.rll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10422005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1041sqlevn70.rll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10402005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1036sqlevn70.rll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10332005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1031sqlevn70.rll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10282005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033XPStar90.RLL 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn6.6.3.5 C:Program FilesMicrosoft SQL Server90Sharedmsxmlsql.dll 02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2.0.3609.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlrw.dll 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 02/15/2007 15:10:39.629 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLBOOT.dll 02/15/2007 15:10:39.629 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxplog70.dll 02/15/2007 15:10:39.629 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnatchp~1.dll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 02/15/2007 15:10:39.645 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90SharedResources10339.0.2047.0 C:Program FilesMicrosoft SQL Server90Sharedmsmdrdir.dll 02/15/2007 15:10:39.645 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0 C:Program FilesCommon FilesSystemole dbxmlrw.dll 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 02/15/2007 15:10:39.676 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll 02/15/2007 15:10:39.676 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033 C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 02/15/2007 15:10:39.692 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0 C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 02/15/2007 15:10:39.692 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0 C:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe 02/15/2007 15:10:39.692 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsvc~1.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 02/15/2007 15:10:39.723 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe 02/15/2007 15:10:39.723 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0 C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL 02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlSAC.exe 02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedMicrosoft.SqlSac.Public.dll 02/15/2007 15:10:51.256 The following exception occurred: User canceled patch install Date: 02/15/2007 15:10:51.256 File: depotsqlvaultsetupmainsetupsqlsesqlsedllfilegroup.cpp Line: 865 02/15/2007 15:10:51.256 Restarting SQL Service MSSQLServer since it was previously running 02/15/2007 15:10:51.256 Attempting to start service: MSSQLServer 02/15/2007 15:10:54.944 Successfully started service: MSSQLServer 02/15/2007 15:10:54.944 Restarting SQL Agent Service SQLSERVERAGENT since it was previously running 02/15/2007 15:10:54.959 Attempting to start service: SQLSERVERAGENT 02/15/2007 15:10:58.350 Successfully started service: SQLSERVERAGENT 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product Status Summary: 02/15/2007 15:10:58.350 Product: SQL Server Native Client 02/15/2007 15:10:58.350 SQL Server Native Client (RTM ) - Success 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product: Setup Support Files 02/15/2007 15:10:58.350 Setup Support Files (RTM ) - Success 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product: Database Services 02/15/2007 15:10:58.350 Database Services (RTM 1399 ENU) - Cancelled 02/15/2007 15:10:58.350 Reporting Services (SP1 2047 ENU) - Not Applied 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product: Integration Services 02/15/2007 15:10:58.350 Integration Services (SP1 2047 ENU) - Not Selected 02/15/2007 15:10:58.350 02/15/2007 15:10:58.350 Product: Client Components 02/15/2007 15:10:58.366 Client Components (SP1 2047 ENU) - Not Selected 02/15/2007 15:10:58.366 02/15/2007 15:10:58.366 Product: MSXML 6.0 Parser 02/15/2007 15:10:58.366 MSXML 6.0 Parser (RTM ) - Not Selected 02/15/2007 15:10:58.366 02/15/2007 15:10:58.366 Product: SQLXML4 02/15/2007 15:10:58.366 SQLXML4 (RTM ) - Not Selected 02/15/2007 15:10:58.366 02/15/2007 15:10:58.366 Product: Backward Compatibility 02/15/2007 15:10:58.366 Backward Compatibility (RTM ) - Not Selected 02/15/2007 15:10:58.366 02/15/2007 15:10:58.366 Product: Microsoft SQL Server VSS Writer 02/15/2007 15:10:58.366 Microsoft SQL Server VSS Writer (RTM ) - Not Selected 02/15/2007 15:10:58.366
hello friends my one insert code lines is below :) what does int32 mean ? AND WHAT IS DIFFERENT BETWEEN ONE CODE LINES AND SECOND CODE LINES :)Dim conn As New SqlConnection(ConfigurationManager.ConnectionStrings("ConnectionString").ConnectionString) Dim cmd As New SqlCommand("Insert into table1 (UserId) VALUES (@UserId)", conn) 'you should use sproc instead cmd.Parameters.AddWithValue("@UserId", textbox1.text) 'your value Try conn.Open()Dim rows As Int32 = cmd.ExecuteNonQuery() conn.Close()Trace.Write(String.Format("You have {0} rows inserted successfully!", rows.ToString())) Catch sex As SqlExceptionThrow sex Finally If conn.State <> Data.ConnectionState.Closed Then conn.Close() End If End Try MY SECOND INSERT CODE LINES IS BELOWDim SglDataSource2, yeni As New SqlDataSource() SglDataSource2.ConnectionString = ConfigurationManager.ConnectionStrings("ConnectionString").ToString SglDataSource2.InsertCommandType = SqlDataSourceCommandType.Text SglDataSource2.InsertCommand = "INSERT INTO urunlistesi2 (kategori1) VALUES (@kategori1)" SglDataSource2.InsertParameters.Add("kategori1", kategoril1.Text)Dim rowsaffected As Integer = 0 Try rowsaffected = SglDataSource2.Insert()Catch ex As Exception Server.Transfer("yardim.aspx") Finally SglDataSource2 = Nothing End Try If rowsaffected <> 1 ThenServer.Transfer("yardim.aspx") ElseServer.Transfer("urunsat.aspx") End If
We have a SQL 2000 Active/Passive cluster running on Windows 2000. On one node, everything logs in fine (second node is powered off). I can use local authentication fine in OSQL (-E) and even see my connection in SQLEM current activity as [DomainUser] for the NT account which I am logged in as. Then I bring the second node online and initiate a failover. SQL Server starts but Cluster Admin cannot connect and starts throwing this Anonymous Logon error. I open a command prompt and try the same OSQL (-E) local login and sure enough it is also giving the Anonymous Logon connection user. I do not understand why the failover to a second node is causing the Trusted Connection Local authentication to switch to Anonymous instead of the [DomainUser] which I am using. Any help is appreciated. John.
Sir i am trying to connect sql from my LAN to my networked computers but whenever i tried to register it through Enterprise manager i get following "SQL Server registration failed because of the conection failure displayed below.Do you wish to Register anyway? Login failed for user 'SW17/Guest'
where SW17/ is my another computer name... i have checked tcp and named pipes and confirm username for sql authentication too please help me as i being late submit my project
Hi when i try and open a database in sql server management studio i get the error "Cannot open user default database. Login failed. Login failed for user 'DOMAINUser'. (.Net SqlClient Data Provider)", what can i do to rectify this, i have googled around and still havent found no answers.
hi, so i have a new box and I'm trying to get my websites and SQL Server 2005 Standard Edition working on it, but the pages give me the following error when I try to load them: "Cannot Open Database "XXXX" requested by login. The login failed. Login failed for user 'xxx'" Everything seems exactly the same settings and user-wise from my old box to my new one, but nevertheless everything I've tried gives me the same error. I've tried creating new users in SQL Server and giving them appropriate permissions to my database. I've even tried just using the built in 'sa' account. Nothing seems to change the error, except when I give it the incorrect password then it just says 'login failed' This leads me to believe that i'm successfully logging into the SQL Server, but it doesn't want to give me access to the database I'm requesting access too. But "apparently" the account i'm using should have access to the database. If nothing else the 'sa' account should, but that didn't work either. I'm stumped. Any ideas?
