Sql Server 2005 Write Error 18210

Dec 18, 2007

I am trying to backup two 40 GB database on server A and server B.

Server A is SAN attached and has 70GB free space for the backup.

Server B is NOT SAN attached and uses a local drive with 113GB free space.

Both backup's result in the same problem. The below is an extract from sql server log file regarding the errors.




Code Block12/18/2007 12:24:01,spid64,Unknown,BackupDiskFile::OpenMedia: Backup device 'H:MSSQL.1BackupfiveDWfiveDWfiveDW_backup_200712181200.bak' failed to open. Operating system error 2(error not found).,
12/18/2007 12:24:01,spid64,Unknown,Error: 18204<c/> Severity: 16<c/> State: 1.,
12/18/2007 12:23:54,Backup,Unknown,BACKUP failed to complete the command BACKUP DATABASE fiveDW. Check the backup application log for detailed messages.,
12/18/2007 12:23:54,Backup,Unknown,Error: 3041<c/> Severity: 16<c/> State: 1.,
12/18/2007 12:23:54,spid64,Unknown,BackupMedium::ReportIoError: write failure on backup device 'H:MSSQL.1BackupfiveDWfiveDWfiveDW_backup_200712181200.bak'. Operating system error 33(error not found).,
12/18/2007 12:23:54,spid64,Unknown,Error: 18210<c/> Severity: 16<c/> State: 1.,


Please note timings in log extract.

All help is appreciated

Thanks, Chris

View 4 Replies


ADVERTISEMENT

Error 18210 Backup Up SQL Server 2005 Database To Network Drive

Aug 1, 2007

I have 2 different servers that run nightly backup jobs to a network drive using the UNC format. I am noticing the larger databases encountering the following errors on a regular basis

Error: 18210, Severity: 16, State: 1.
'\fnfssql3SQLBackupsMNSQL05<database>.BAK'. Operating system error 64(The specified network name is no longer available.).
BACKUP failed to complete the command BACKUP DATABASE <database>. Check the backup application log for detailed messages.



There are 5 databases on this server all backed up by the same job and 3 of them wortk fine and 2 of them fail so it is not a permissions problem. Have there been any problems with backing up to a network drive in 2005?

View 4 Replies View Related

Need To Write From Asp.net To XML Type In SQL Server 2005

Nov 3, 2007

Hello, I have worked with SQL Server 2000 but now we have a requirement where I need to write values from an asp.net form into an XML type in SQL Server 2005.
I have never used XML as a type in SQL Server 2005. How do we write xml into xml type.
For example the structure of XML is something like:
<application>
<applicationID = "value"></applicationID>
<customerName="value></customerName>
</application>
I have to write this kind of XML into the XML type and later retrieve these XML values and populate the form again.
Kindly suggest. Thanks a lot. 
 

View 1 Replies View Related

Performance To Write Data In SQL Server 2005

May 25, 2007

Dear friends,

A simple question to you... witch of this dataflow destination is better for performance to write data in a SQL Server 2005:



1. SQL Server Destination?

2. OLEDB Destination?

3. Other?



Thanks!

View 1 Replies View Related

How To Write Batch Program In SQL Server 2005?

Sep 10, 2007



Hello All,
I want to write Batch Program which will insert Data into Table every day based on some conditions.
can anyone please let me know how to write Batch Process in SQL server 2005??
Thanks.

View 5 Replies View Related

SQL Server 2005 Crashing On Write Access - ARGH!

May 30, 2006

Hi,I'm accessing a pair of databases with ASP/ADO,and using stored procedures on the first access.The first access works OK - everything gets writtento where it's supposed to be.On attempting to write to a pair of database tablesin the second database (second access attempt),the server crashes, as does the app, and I get the following error:--------------------------------------------------------------------Server Error in '/Webfolder01' Application.Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)--------------------------------------------------------------------After this, I have to go into the services panel and restart SQL 2005.This doesn't happen if I use small test data sets in the first access,and I can comment out the second access attempt, and the first accessexecutes just fine with both the large and small data sets,so I'm thinking that this has something to do with synchronisation:Perhaps the second attempt is being made before the server is ready.Is there something that I need to do to make certain that SQL 2005is ready to receive data?I'm using SqlBulkCopy with both accesses, but I don't see how thatcould be a problem.--------------------------------------------------------------------[SqlException (0x80131904): A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)]   System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +857370   System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +734982   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188   System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error) +556   System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj) +164   System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected) +34   System.Data.SqlClient.TdsParserStateObject.ReadBuffer() +30   System.Data.SqlClient.TdsParserStateObject.ReadByte() +17   System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler,                     TdsParserStateObject stateObj) +59   System.Data.SqlClient.SqlBulkCopy.WriteToServerInternal() +1327   System.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServer (Int32 columnCount) +916   System.Data.SqlClient.SqlBulkCopy.WriteToServer(DataTable table, DataRowState rowState) +176   System.Data.SqlClient.SqlBulkCopy.WriteToServer(DataTable table) +6   Database_control.DB_ctrl_class.load_datatable_to_DB_table(DB_ref_class src_table) in i:Virtual WebfoldersDBctrl.cs:978--------------------------------------------------------------------THANK YOU VERY MUCH!!!

View 4 Replies View Related

SQL Server Hot Fix Install Error - Dbmslpcn.dll Is WRITE LOCKED

Jul 23, 2005

Hi-I've been trying to install SS2K Hot Fix # 818095 for one of my clientsand it keeps terminating - the Log for the install contains an errormessage that reads "...dbmslpcn.dll is WRITE LOCKED".I stopped all but a few of the services on the box, but still can'tseem to get it installed.Any suggesions??Thanks in advance for any help on this issue, it's been a royal PITA!Pete

View 1 Replies View Related

Am Using Sql Server 2005, Column Data Type Is Varchar, How To Write A Query To Sort

Aug 2, 2006

this data. need help
Sort following numbers by asc and desc order

Before query sort
-1.1
-8.8
-15.5
0.0
+0.5
+0.2

Sort asc
+0.5
+0.2
0.0
-1.1
-8.8

Sort Desc
-8.8
-1.1
0.0
+0.2
+0.5












View 5 Replies View Related

SQL 2000 Reovery Fails Sometimes. Error Code (Error 3136). How To Make Database Write Mode?

Jan 7, 2008

Hello,

I am applying hourly differential backup to the backup server from production with the following command. This command makes the database on standby server into read only mode.


RESTORE DATABASE ARSYSTEM FROM DISK = 'E:SQL backup from productionsql_full_backup'
WITH MOVE 'arsystem' TO
'd:ardataarsystem.mdf' ,
MOVE 'arsystem_log' TO 'D:ARLOGARsystem' ,
STANDBY = 'E:SQL backup from productionSQL daily diff back up'


Now I want to run a command which will put the database in write mode. I have created a job which would make the datbase Write mode. This job runs successfully sometimes and fails sometimes. I need to ensure that the job always succeeds. When it fails, how do I troubleshoot and what is the possible fix?

Thanks in advance.

The error message is

Cannot apply the backup on device 'E:SQL backup from productionSQL daily diff back up' to database 'ARSYSTEM'. [SQLSTATE 42000] (Error 3136) RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.


The steps for the job are as follows with the failing step highlighted in bold.


copy /y "\172.31.9.12Remedy BackupackupSQL backupsql_full_backup" "E:SQL backup from productionsql_full_backup"

copy /y "\172.31.9.12Remedy BackupackupSQL backupSQL daily diff back up" "E:SQL backup from productionSQL daily diff back up"

xp_cmdshell 'net stop "bmc remedy action request system server"'

exec rp_kill_db_processes 'ARSYSTEM'

RESTORE DATABASE ARSYSTEM

FROM DISK = 'E:SQL backup from productionsql_full_backup'

WITH

MOVE 'arsystem' TO 'd:ardataarsystem.mdf' ,

MOVE 'arsystem_log' TO 'D:ARLOGARsystem' ,

NORECOVERY


Failing step

RESTORE DATABASE ARSYSTEM

FROM DISK = 'E:SQL backup from productionSQL daily diff back up'

WITH

MOVE 'arsystem' TO 'd:ardataarsystem.mdf' ,

MOVE 'arsystem_log' TO 'D:ARLOGARsystem' ,

RECOVERY



xp_cmdshell 'del /f "E:SQL backup from productionsql_full_backup"'

xp_cmdshell 'del /f "E:SQL backup from productionsql daily diff back up"'

xp_cmdshell 'net start "bmc remedy action request system server"'





I have scheduled the following hourly diffential restore job too which never fails.

RESTORE DATABASE ARSYSTEM FROM DISK = 'E:SQL backup from productionsql_full_backup'
WITH MOVE 'arsystem' TO
'd:ardataarsystem.mdf' ,
MOVE 'arsystem_log' TO 'D:ARLOGARsystem' ,
STANDBY = 'E:SQL backup from productionSQL daily diff back up'
EXEC MASTER..XP_CMDSHELL 'del /f "E:SQL backup from productionSQL daily diff back up"'

View 12 Replies View Related

SQL Server 2005 Install Error (Error 29528. Unexpected Error While Installing Performance Counters. )

Jun 12, 2007

I'm currently receiving the following error message whilst attempting to install SQL Server 2005 Standard Edition on Windows Server 2003 (32 Bit):
Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.

This server already has an install of SQL Server 2000 as the default instance. I'm attempting to install a new named instance of SQL Server 2005.

Extract from log:

<Func Name='LaunchFunction'>
Function=Do_sqlPerfmon2
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_sqlPerfmon2
PerfTime Start: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
<Func Name='Do_sqlPerfmon2'>
<EndFunc Name='Do_sqlPerfmon2' Return='0' GetLastError='2'>
PerfTime Stop: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
MSI (s) (4C:FC) [10:20:02:833]: Executing op: ActionStart(Name=Rollback_Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Removing performance counters,)
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (4C:FC) [10:20:02:849]: Executing op: CustomActionSchedule(Action=Rollback_Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1281,Source=BinaryData,Target=Rollback_Do_sqlPerfmon2,CustomActionData=100Removing performance counters200000DTSPipelineC:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.INI)
MSI (s) (4C:FC) [10:20:02:849]: Executing op: ActionStart(Name=Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Installing performance counters,)
MSI (s) (4C:FC) [10:20:02:849]: Executing op: CustomActionSchedule(Action=Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1025,Source=BinaryData,Target=Do_sqlPerfmon2,CustomActionData=100Installing performance counters200000C:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.INIC:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.HC:Program FilesMicrosoft SQL Server90DTSBinnDTSPipelinePerf.dllDTSPipeline0DTSPipelinePrfData_OpenPrfData_CollectPrfData_Close)
MSI (s) (4C:94) [10:20:02:864]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI1683.tmp, Entrypoint: Do_sqlPerfmon2
<Func Name='LaunchFunction'>
Function=Do_sqlPerfmon2
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_sqlPerfmon2
PerfTime Start: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
<Func Name='Do_sqlPerfmon2'>
<EndFunc Name='Do_sqlPerfmon2' Return='2' GetLastError='2'>
PerfTime Stop: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
Gathering darwin properties for failure handling.
Error Code: 2
MSI (s) (4C!F0) [10:23:46:381]: Product: Microsoft SQL Server 2005 Integration Services -- Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.

You can ignore this and it will complete the installation, but subsequently trying to patch with SP2 will fail on the same sections - Hotfix.exe crashes whilst attempting to patch Database Services, Integration Services and Client Components (3 separate crashes).

I've removed SQL Server 2005 elements and tried to re-install, but it's not improved the situation.

Any ideas?

View 3 Replies View Related

How To Write Sp Into .Net 2005?

Jun 5, 2007

Hi, all!

I need to write sql procs into .net for debugging. When i create SQL DataProject in C# reference i catch a message "SQL server specefied this connection doesn't support managed objects. choose different server". Why? I have sql 2005 standard edition, indeed. But I dare say one remark i have 2 SQL instances on machine (2000 and 2005). so i see trouble in this. does anybode know how to sort out this trouble?
thanks in advance!

View 2 Replies View Related

DB Write Error

Aug 10, 2005

Hi, Any info will be greatly appreciated to fix this issue.

I am getting the following errors in my event log.
Error: 823, Severity: 24, State: 2
I/O error 2(The system cannot find the file specified.) detected during read at offset 0x00000004f7e000 in file 'F:Program FilesMicrosoft SQL ServerMSSQLDataPENANGwiptrack_targetpng_data2.ndf'.

I am getting these error when I run DBCC:

Server: Msg 8966, Level 16, State 2, Line 1
Could not read and latch page (3:9944) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:9945) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:9946) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:9947) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:9948) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:9949) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:9950) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:9951) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10168) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10169) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10170) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10171) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10173) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10174) with latch type UP. 2(The system cannot find the file specified.) failed.
DBCC results for 'PNG_TARGET'.
Server: Msg 8966, Level 16, State 2, Line 1
Could not read and latch page (3:10175) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10176) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10177) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10178) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10179) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10180) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10181) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10182) with latch type UP. 2(The system cannot find the file specified.) failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (3:10183) with latch type UP. 2(The system cannot find the file specified.) failed.
CHECKDB found 0 allocation errors and 23 consistency errors not associated with any single object.
DBCC results for 'sysobjects'.
There are 215 rows in 10 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 220 rows in 14 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 1390 rows in 78 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 187 rows in 64 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 4 rows in 1 pages for object 'sysfiles1'.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 421576540, index ID 8. Page (1:87967) is missing a reference from previous page (3:10176). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 421576540, index ID 8. Page (1:88969) is missing a reference from previous page (3:10183). Possible chain linkage problem.
DBCC results for 'syspermissions'.
There are 221 rows in 4 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 255 rows in 4 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 570 rows in 8 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 0 rows in 1 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 1 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
DBCC results for 'TblReject'.
There are 396620 rows in 10949 pages for object 'TblReject'.
DBCC results for 'TblBoxGroup'.
There are 22669 rows in 380 pages for object 'TblBoxGroup'.
DBCC results for 'TblCustShipment'.
There are 4425 rows in 83 pages for object 'TblCustShipment'.
DBCC results for 'TblFlowDetail'.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10176) allocated to object ID 421576540, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 421576540, index ID 8. Index node page (1:90702), slot 10 refers to child page (3:10176) and previous child (3:10177), but they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10177) allocated to object ID 421576540, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 421576540, index ID 8. Page (3:10177) was not seen in the scan although its parent (1:90702) and previous (1:87966) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10178) allocated to object ID 421576540, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 421576540, index ID 8. Index node page (1:90702), slot 13 refers to child page (3:10178) and previous child (3:10179), but they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10179) allocated to object ID 421576540, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 421576540, index ID 8. Page (3:10179) was not seen in the scan although its parent (1:90702) and previous (1:87967) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10180) allocated to object ID 421576540, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 421576540, index ID 8. Index node page (1:90702), slot 14 refers to child page (3:10180) and previous child (3:10178), but they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10181) allocated to object ID 421576540, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 421576540, index ID 8. Index node page (1:90702), slot 15 refers to child page (3:10181) and previous child (3:10180), but they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10182) allocated to object ID 421576540, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 421576540, index ID 8. Index node page (1:90702), slot 16 refers to child page (3:10182) and previous child (3:10181), but they were not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10183) allocated to object ID 421576540, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 421576540, index ID 8. Index node page (1:90702), slot 17 refers to child page (3:10183) and previous child (3:10182), but they were not encountered.
There are 523629 rows in 9233 pages for object 'TblFlowDetail'.
CHECKDB found 0 allocation errors and 18 consistency errors in table 'TblFlowDetail' (object ID 421576540).
DBCC results for 'TblJob'.
There are 18895 rows in 623 pages for object 'TblJob'.
DBCC results for 'TblRejectDetailCross'.
There are 0 rows in 0 pages for object 'TblRejectDetailCross'.
DBCC results for 'TblStationChkPoint'.
There are 298610 rows in 6273 pages for object 'TblStationChkPoint'.
DBCC results for 'ci_control_TblBoxGroup'.
There are 0 rows in 1 pages for object 'ci_control_TblBoxGroup'.
DBCC results for 'ci_control_TblCustomer'.
There are 0 rows in 0 pages for object 'ci_control_TblCustomer'.
DBCC results for 'TblLine'.
There are 7 rows in 1 pages for object 'TblLine'.
DBCC results for 'ci_control_TblCustShipment'.
There are 0 rows in 1 pages for object 'ci_control_TblCustShipment'.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (1:65650) is missing a reference from previous page (3:9950). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (1:80141) is missing a reference from previous page (3:9949). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (1:81931) is missing a reference from previous page (3:9948). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (1:88745) is missing a reference from previous page (3:9944). Possible chain linkage problem.
DBCC results for 'ci_control_TblDefect'.
There are 0 rows in 1 pages for object 'ci_control_TblDefect'.
DBCC results for 'ci_control_TblFlowDetail'.
There are 0 rows in 1 pages for object 'ci_control_TblFlowDetail'.
DBCC results for 'TblStationQty'.
There are 487814 rows in 8946 pages for object 'TblStationQty'.
DBCC results for 'TblMachine'.
There are 5 rows in 1 pages for object 'TblMachine'.
DBCC results for 'ci_control_TblJob'.
There are 0 rows in 1 pages for object 'ci_control_TblJob'.
DBCC results for 'ci_control_TblJobDetail'.
There are 0 rows in 1 pages for object 'ci_control_TblJobDetail'.
DBCC results for 'TblOperator'.
There are 470 rows in 7 pages for object 'TblOperator'.
DBCC results for 'ci_control_TblLine'.
There are 0 rows in 0 pages for object 'ci_control_TblLine'.
DBCC results for 'TblOperatorGroup'.
There are 22 rows in 1 pages for object 'TblOperatorGroup'.
DBCC results for 'TblTransaction'.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (1:91159) is missing a reference from previous page (3:9945). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (1:95791) is missing a reference from previous page (3:9951). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (1:857249) is missing a reference from previous page (3:9946). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (3:9630) is missing a reference from previous page (3:9947). Possible chain linkage problem.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:9944) allocated to object ID 768057822, index ID 4 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (3:9944) was not seen in the scan although its parent (1:86516) and previous (3:10996) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:9945) allocated to object ID 768057822, index ID 4 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (3:9945) was not seen in the scan although its parent (1:862260) and previous (1:81719) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:9946) allocated to object ID 768057822, index ID 4 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (3:9946) was not seen in the scan although its parent (1:2888) and previous (1:39804) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:9947) allocated to object ID 768057822, index ID 4 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (3:9947) was not seen in the scan although its parent (1:858889) and previous (1:84220) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:9948) allocated to object ID 768057822, index ID 4 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (3:9948) was not seen in the scan although its parent (1:51120) and previous (1:81279) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:9949) allocated to object ID 768057822, index ID 4 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (3:9949) was not seen in the scan although its parent (1:81180) and previous (1:79351) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:9950) allocated to object ID 768057822, index ID 4 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (3:9950) was not seen in the scan although its parent (1:51120) and previous (1:65448) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:9951) allocated to object ID 768057822, index ID 4 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 4. Page (3:9951) was not seen in the scan although its parent (1:60668) and previous (1:87177) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Page (1:921) is missing a reference from previous page (3:10169). Possible chain linkage problem.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:17475) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:55333) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:58600) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:66724) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:73049) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:73183) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:77526) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:80853) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:82680) was not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Page (1:83104) is missing a reference from previous page (3:10170). Possible chain linkage problem.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:83310) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:85752) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:87603) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:91416) was not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Page (1:91418) is missing a reference from previous page (3:10173). Possible chain linkage problem.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:92037) was not encountered.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Page (1:92278) is missing references from parent (unknown) and previous (page (3:10168)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:94476) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:98109) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:99231) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:100289) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:103626) was not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Page (1:104154) is missing a reference from previous page (3:10175). Possible chain linkage problem.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:104303) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:107339) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:110106) was not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Page (1:985785) is missing a reference from previous page (3:10174). Possible chain linkage problem.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989636) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989637) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989638) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989639) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989640) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989641) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989642) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989643) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989644) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989645) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989646) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989647) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989648) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989649) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989650) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989651) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989652) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989653) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989654) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989655) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989656) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989657) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989658) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989659) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989660) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989661) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989662) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989663) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989664) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989665) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989666) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989667) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989668) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989669) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989670) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989671) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989672) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989673) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989674) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989675) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989676) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (1:989677) was not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Page (1:990949) is missing a reference from previous page (3:10171). Possible chain linkage problem.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (3:4460) was not encountered.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10168) allocated to object ID 768057822, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8981, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. The next pointer of (1:83310) refers to page (3:10168). Neither (3:10168) nor its parent were encountered. Possible bad chain linkage.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10169) allocated to object ID 768057822, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Page (3:10169) was not seen in the scan although its parent (1:9152) and previous (1:989626) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10170) allocated to object ID 768057822, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Page (3:10170) was not seen in the scan although its parent (1:76565) and previous (1:83980) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10171) allocated to object ID 768057822, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Page (3:10171) was not seen in the scan although its parent (1:925) and previous (1:34912) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10173) allocated to object ID 768057822, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Page (3:10173) was not seen in the scan although its parent (1:76565) and previous (1:78785) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10174) allocated to object ID 768057822, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Page (3:10174) was not seen in the scan although its parent (1:985742) and previous (1:80575) refer to it. Check any previous errors.
Server: Msg 2533, Level 16, State 1, Line 1
Table error: Page (3:10175) allocated to object ID 768057822, index ID 8 was not seen. Page may be invalid or have incorrect object ID information in its header.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Page (3:10175) was not seen in the scan although its parent (1:88169) and previous (1:83978) refer to it. Check any previous errors.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 768057822, index ID 8. Parent node for page (3:10339) was not encountered.
There are 4277643 rows in 97804 pages for object 'TblTransaction'.
CHECKDB found 0 allocation errors and 111 consistency errors in table 'TblTransaction' (object ID 768057822).
DBCC results for 'ci_control_TblLot'.
There are 0 rows in 1 pages for object 'ci_control_TblLot'.
DBCC results for 'ci_control_TblMachine'.
There are 0 rows in 0 pages for object 'ci_control_TblMachine'.
DBCC results for 'ci_control_TblOperator'.
There are 0 rows in 1 pages for object 'ci_control_TblOperator'.
DBCC results for 'ci_control_TblOperatorGroup'.
There are 0 rows in 0 pages for object 'ci_control_TblOperatorGroup'.
DBCC results for 'TtmpTransaction'.
There are 0 rows in 0 pages for object 'TtmpTransaction'.
DBCC results for 'TblCPQWeekNbr'.
There are 53 rows in 1 pages for object 'TblCPQWeekNbr'.
DBCC results for 'ci_control_TblPartDetail'.
There are 0 rows in 1 pages for object 'ci_control_TblPartDetail'.
DBCC results for 'TblCPQYearNbr'.
There are 180 rows in 1 pages for object 'TblCPQYearNbr'.
DBCC results for 'TblKitModSNRship'.
There are 472666 rows in 5462 pages for object 'TblKitModSNRship'.
DBCC results for 'ci_control_TblPartSupplier'.
There are 0 rows in 0 pages for object 'ci_control_TblPartSupplier'.
DBCC results for 'TblShift'.
There are 3 rows in 1 pages for object 'TblShift'.
DBCC results for 'ci_control_TblReject'.
There are 0 rows in 1 pages for object 'ci_control_TblReject'.
DBCC results for 'ci_control_TblRejectDetail'.
There are 0 rows in 1 pages for object 'ci_control_TblRejectDetail'.
DBCC results for 'ci_control_TblShift'.
There are 0 rows in 0 pages for object 'ci_control_TblShift'.
DBCC results for 'ci_control_TblStation'.
There are 0 rows in 1 pages for object 'ci_control_TblStation'.
DBCC results for 'ci_control_TblStationChkPoint'.
There are 0 rows in 1 pages for object 'ci_control_TblStationChkPoint'.
DBCC results for 'ci_control_TblStationQty'.
There are 3 rows in 1 pages for object 'ci_control_TblStationQty'.
DBCC results for 'ci_control_TblTester'.
There are 0 rows in 0 pages for object 'ci_control_TblTester'.
DBCC results for 'ci_control_TblTransaction'.
There are 0 rows in 1 pages for object 'ci_control_TblTransaction'.
DBCC results for 'TblCustomer'.
There are 7 rows in 1 pages for object 'TblCustomer'.
DBCC results for 'TblTester'.
There are 16 rows in 1 pages for object 'TblTester'.
DBCC results for 'ci_control_TblKitModSNRship'.
There are 0 rows in 1 pages for object 'ci_control_TblKitModSNRship'.
DBCC results for 'ci_control_TblSystemBuild'.
There are 1 rows in 1 pages for object 'ci_control_TblSystemBuild'.
DBCC results for 'TblRejectDetail'.
There are 104402 rows in 2403 pages for object 'TblRejectDetail'.
DBCC results for 'TblJobDetail'.
There are 1107946 rows in 23608 pages for object 'TblJobDetail'.
DBCC results for 'TblPartSupplier'.
There are 79 rows in 1 pages for object 'TblPartSupplier'.
DBCC results for 'TblDefect'.
There are 21113 rows in 337 pages for object 'TblDefect'.
DBCC results for 'png_ci_TblRowCount'.
There are 24 rows in 1 pages for object 'png_ci_TblRowCount'.
DBCC results for 'TblTbSetup'.
There are 1 rows in 1 pages for object 'TblTbSetup'.
DBCC results for 'TblStationQty1'.
There are 61755 rows in 974 pages for object 'TblStationQty1'.
DBCC results for 'TtmpStationProdLoad'.
There are 57 rows in 1 pages for object 'TtmpStationProdLoad'.
DBCC results for 'TblPartDetail'.
There are 3053 rows in 93 pages for object 'TblPartDetail'.
DBCC results for 'TblLot'.
There are 515677 rows in 11268 pages for object 'TblLot'.
DBCC results for 'TblStation'.
There are 474 rows in 11 pages for object 'TblStation'.
DBCC results for 'TblSystemBuild'.
There are 128623 rows in 2362 pages for object 'TblSystemBuild'.
DBCC results for 'dtproperties'.
There are 0 rows in 1 pages for object 'dtproperties'.
DBCC results for 'TblEqMaster'.
There are 0 rows in 1 pages for object 'TblEqMaster'.
DBCC results for 'TblEqMasterSNRShip'.
There are 0 rows in 1 pages for object 'TblEqMasterSNRShip'.
CHECKDB found 0 allocation errors and 152 consistency errors in database 'PNG_TARGET'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (PNG_TARGET ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

View 4 Replies View Related

Unable To Connect To SQL Server 2005 (error: 26 - Error Locating Server/Instance Specified)

Jun 5, 2007

I've installed SQL2005 on a server already running SQL2K on my laptop. SQL2K is the default instance, so I'm trying to connect to SQL2005 using MYSERVERSQL2005 as the instance.

The steps that I've taken are to apply SP2 and enable remote connections (TCP & Named pipes). I've also made sure the SQL Server Browser service is running and enabled.

The error message that I get via SQL2005 client tools is "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)"

I dont understand as to why i am unable to connect to 2005.

Any ideas?

View 4 Replies View Related

I Can't Write Data To Sql 2005

Dec 20, 2007



I have big problem now, can somebody help me?
I have a program used ASP+SQL2000 ,the connection string is :
strConnection = "Provider=SQLOLEDB;Server=BOUNwindows,1005;User ID=training;Password=training22;Database=ourtraining;"
Everything works fine, I can insert data, delete or modify.
But since we changed sql2000 server to sql 2005 express, then I can read data but can't insert data(write data into sql 2005)
I checked all permission are correct on sql 2005, program are correct, everything looks good, but only can't write data into sql2005

Can somebody help me????

View 5 Replies View Related

Error Trying To Write File

Aug 3, 2004

I don't have direct access to the SQL server. I have to write/read through a class I recieved from the IT department. The class also had an example in it but I can't get it to work correctly.

I get an error: Object reference not set to an instance of an object. Line 35


Dim clsWDD As New WebDevDB.WebDevDB
Dim intLeng As Int32
Dim intLock As Int32

Dim strAppl As String = "MyApplication"
Dim strData As String = "This is my text data!"

Dim strFile As String = "MyFile"

intLock = clsWDD.LockTextFile(strAppl, strFile) 'line 35
intLeng = clsWDD.WriteTextFile(strAppl, strFile, strData, WriteAction.Create)
intLock = clsWDD.UnlockTextFile(intLock)

View 2 Replies View Related

Capturing WARNINGS To Write To Error Log?

Jul 23, 2004

Hey y'all...

Anyone know how to capture SQL Warnings so I can write them to an error log? I can't seem to find any info on it in Books Online...

I can capture the errors just fine by using @@ERROR after a select, but what about warnings such as "Warning: Null value is eliminated by an aggregate or other SET operation."

Thanks!

View 4 Replies View Related

How To Write Error Logs In Notepad

Nov 27, 2013

how to write a error logs in notepad in sql server 2008

View 3 Replies View Related

Could You Write A Special Stored Procedure For Me In SQL 2005?

Apr 6, 2006

Could you write a special stored procedure for me in SQL 2005?
When I execute the SQL "select TagName from Th_TagTable where IDTopic=@IDTopic" , it return several rows such as TagName= SportTagName= NewTagName= Health
I hope there is a stored procedure which can join all TagName into a single string and return,it means when I pass @IDTopic to the stored procedure, it return "Sport,New,Health"
How can write the stored procedure?

View 2 Replies View Related

How To Write A Function For MS SQL 2005 To Save Value After Underscore?

Apr 14, 2008

Hi Gurus,

How do I write a T-SQL function for a string before a underscore is found?


Thanks Gurus.

View 2 Replies View Related

Could You Write A Special Stored Procedure For Me In SQL 2005?

Aug 19, 2007



When I execute the SQL "select TagName from Th_TagTable where IDTopic=@IDTopic" , it return several rows such as
TagName= http://www.hothelpdesk.com
TagName= http://www.hellocw.com
TagName= http://www.supercoolbookmark.com


I hope there is a stored procedure which can join all TagName into a single string and return,
it means when I pass @IDTopic to the stored procedure, it return "http://www.hothelpdesk.com, http://www.hellocw.com, http://www.supercoolbookmark.com"

How can write the stored procedure?

View 1 Replies View Related

Help. When Using Profile GetPropertyValue, I Get The Following Connection Error: An Error Has Occurred While Establishing A Connection To The Server. When Connecting To SQL Server 2005, This Failure May Be Caused By The Fact That Under The Default Sett

May 3, 2008

 Hi,I need some help. I am getting this error after I complete the asp.net register control and click on the continue button. It crashed when it tries to get it calls this Profile property((string)(this.GetPropertyValue("Address1")));When I look at the stack, it is coming from my ProfileWrapper class which adds user address, city, etc.. from a class which inherits fromSystem.Web.Profile.ProfileBase. From the stack, it is calling the System.Web.Profile and crashed when it tries to open a connection atSystem.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject). I already migrated all aspnet_user, aspnet_roles, etc.. and don't get any connection errors. It is only when I try to get the profile data. This works on  my pc, but throws an error on my lunarpage website.Any help is greatly appreciated.Thanks,AJAn error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)Source Error:Line 100:    public virtual string Address2 {Line 101:        get {Line 102:            return ((string)(this.GetPropertyValue("Address2")));Line 103:        }Line 104:        set {Source File: c:windowsMicrosoft.NETFrameworkv2.0.50727Temporary ASP.NET Files
oot021d50639a6858cApp_Code.54nvluyo.1.cs    Line: 102Stack Trace:[SqlException (0x80131904): An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]   System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +435   System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82   System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105   System.Data.SqlClient.SqlConnection.Open() +111   System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84   System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197   System.Web.Profile.SqlProfileProvider.GetPropertyValuesFromDatabase(String userName, SettingsPropertyValueCollection svc) +782   System.Web.Profile.SqlProfileProvider.GetPropertyValues(SettingsContext sc, SettingsPropertyCollection properties) +428   System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider) +404   System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName) +117   System.Configuration.SettingsBase.get_Item(String propertyName) +89   System.Web.Profile.ProfileBase.GetInternal(String propertyName) +36   System.Web.Profile.ProfileBase.get_Item(String propertyName) +68   System.Web.Profile.ProfileBase.GetPropertyValue(String propertyName) +4   ProfileCommon.get_Address2() in c:windowsMicrosoft.NETFrameworkv2.0.50727Temporary ASP.NET Files
oot021d50639a6858cApp_Code.54nvluyo.1.cs:102   ProfileWrapper..ctor() in d:inetpubvhostsjavcentral.comhttpdocsApp_CodeProfileWrapper.cs:242   ProfileDataSource.GetData() in d:inetpubvhostsjavcentral.comhttpdocsApp_CodeProfileDataSource.cs:17[TargetInvocationException: Exception has been thrown by the target of an invocation.]   System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) +0   System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) +72   System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) +308   System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) +29   System.Web.UI.WebControls.ObjectDataSourceView.InvokeMethod(ObjectDataSourceMethod method, Boolean disposeInstance, Object& instance) +480   System.Web.UI.WebControls.ObjectDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments) +1960   System.Web.UI.DataSourceView.Select(DataSourceSelectArguments arguments, DataSourceViewSelectCallback callback) +17   System.Web.UI.WebControls.DataBoundControl.PerformSelect() +149   System.Web.UI.WebControls.BaseDataBoundControl.DataBind() +70   System.Web.UI.WebControls.FormView.DataBind() +4   System.Web.UI.WebControls.BaseDataBoundControl.EnsureDataBound() +82   System.Web.UI.WebControls.FormView.EnsureDataBound() +163   System.Web.UI.WebControls.CompositeDataBoundControl.CreateChildControls() +69   System.Web.UI.Control.EnsureChildControls() +87   System.Web.UI.Control.FindControl(String id, Int32 pathOffset) +21   System.Web.UI.Control.FindControl(String id) +9   CustomerDetailsEdit.OnPreRender(EventArgs e) in d:inetpubvhostsjavcentral.comhttpdocsUserControlsCustomerDetailsEdit.ascx.cs:60   System.Web.UI.Control.PreRenderRecursiveInternal() +86   System.Web.UI.Control.PreRenderRecursiveInternal() +170   System.Web.UI.Control.PreRenderRecursiveInternal() +170   System.Web.UI.Control.PreRenderRecursiveInternal() +170   System.Web.UI.Control.PreRenderRecursiveInternal() +170   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2041 

View 1 Replies View Related

Error Msg: Login Failed For A User . For VS 2005 Websites With SQL Server 2005

May 30, 2008

Just installed SQL Server 2005 and tested my old VS 2005 ASPnet websites, which were connected toSQL Server 2000 databases before.  All my websites were created for local HTTP applications, coded with a connection string with User ID and Password.   The SQL Server 2000 was configured as mixed authentication (i.e. with User ID and Password).  These websites worked very well with SQL Server 2000 database server.Testing my old VS 2005 websites with SQL Server 2005 database, showed a 'Login failed for a User ''.' error msgalthough the 'Test Connection' on VS 2005 design showed a perfect query for e.g. a GridView control.  I have assured that the UserID/Password were correct for Management Studio Security object'slogin and Database Security's user.  The server instance was configured with mixed authentication mode.  One thing I am not sure of is, when clicking the Management Studio icon, a Connection dialog showed up, asking for a Windows or MIxed authentication?  I just stayed with the Windows authentication.  What does the authenticationmode have anything to do with the VS 2005 website connection?  Should I change to mixed authetnication mode?TIA,Jeffrey  

View 3 Replies View Related

Sql 2005 Sp2 Install Error Microsoft SQL Server 2005 -- Errore 29506

May 16, 2007

Sp2 cannot be install

can someone help me



this is hotfix log



05/16/2007 13:05:30.583 ================================================================================
05/16/2007 13:05:30.599 Hotfix package launched
05/16/2007 13:05:30.630 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:30.646 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:30.662 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:30.677 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:30.693 Local Computer:
05/16/2007 13:05:30.708 Target Details: DC-01
05/16/2007 13:05:30.724 commonfilesdir = C:ProgrammiFile comuni
05/16/2007 13:05:30.740 lcidsupportdir = e:3f798aa49a0102c6d1f049aa36bd359d1040
05/16/2007 13:05:30.755 programfilesdir = C:Programmi
05/16/2007 13:05:30.771 programfilesdir_wow = C:Programmi
05/16/2007 13:05:30.771 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:30.802 supportdirlocal = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:30.818 windir = C:WINDOWS
05/16/2007 13:05:30.833 winsysdir = C:WINDOWSsystem32
05/16/2007 13:05:30.849 winsysdir_wow = C:WINDOWSSysWOW64
05/16/2007 13:05:30.865
05/16/2007 13:05:30.958 Enumerating applicable products for this patch
05/16/2007 13:05:31.005 Found Redist 2005 product definition
05/16/2007 13:05:31.021 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.036 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:31.052 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.068 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:31.442 Found Redist 2005 product definition
05/16/2007 13:05:31.458 Found Redist 2005 product definition
05/16/2007 13:05:31.474 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.489 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:31.505 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.521 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:31.677 Found SQL 2005 product definition
05/16/2007 13:05:32.270 Enumeration: Determining QFE level for product instance MSSQLSERVER
05/16/2007 13:05:32.286 Enumeration: Associated hotfix build information not found for the following file: C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLServr.exe
05/16/2007 13:05:32.286 Enumeration: Found following QFE level for product instance MSSQLSERVER: 1399
05/16/2007 13:05:32.302 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
05/16/2007 13:05:32.317 Enumeration: Associated hotfix build information not found for the following file: C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLServr.exe
05/16/2007 13:05:32.333 Enumeration: No GDR branch Hotfix found for product instance MSSQLSERVER
05/16/2007 13:05:32.348 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:32.348 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:32.364 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:32.380 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:32.395 Product discovery completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.411 SP Level check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.411 Product language check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.426 Product version check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.442 Command-line instance name check completed during the install process
05/16/2007 13:05:32.458 SKU check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.473 Baseline build check completed during the installation process for MSSQLSERVER
05/16/2007 13:05:32.489 Baseline build check completed during the install process
05/16/2007 13:05:32.505 Found OLAP Server 2005 product definition
05/16/2007 13:05:33.004 Command-line instance name check completed during the install process
05/16/2007 13:05:33.004 Baseline build check completed during the install process
05/16/2007 13:05:33.036 Found Notification Services 2005 product definition
05/16/2007 13:05:33.520 Baseline build check completed during the install process
05/16/2007 13:05:33.551 Found Report Server 2005 product definition
05/16/2007 13:05:34.051 Command-line instance name check completed during the install process
05/16/2007 13:05:34.066 Baseline build check completed during the install process
05/16/2007 13:05:34.082 Found DTS 2005 product definition
05/16/2007 13:05:34.582 Baseline build check completed during the install process
05/16/2007 13:05:34.613 Found SQL 2005 Tools product definition
05/16/2007 13:05:35.113 Enumeration: Determining GDR branching Hotfix for product instance
05/16/2007 13:05:35.144 Enumeration: Associated hotfix build information not found for the following file: C:ProgrammiMicrosoft SQL Server90Tools\BinnVSShellCommon7IDESQLWB.EXE
05/16/2007 13:05:35.160 Enumeration: No GDR branch Hotfix found for product instance
05/16/2007 13:05:35.175 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.191 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.207 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.207 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:35.222 Product discovery completed during the install process for SQL Tools
05/16/2007 13:05:35.238 SP Level check completed during the install process for SQL Tools
05/16/2007 13:05:35.253 Product language check completed during the install process for SQL Tools
05/16/2007 13:05:35.253 Product version check completed during the install process for SQL Tools
05/16/2007 13:05:35.269 SKU check completed during the install process for SQL Tools
05/16/2007 13:05:35.285 Baseline build check completed during the install process
05/16/2007 13:05:35.300 Found Redist 2005 product definition
05/16/2007 13:05:35.316 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.332 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.347 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.363 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:35.597 Found Redist 2005 product definition
05/16/2007 13:05:35.613 Found Redist 2005 product definition
05/16/2007 13:05:35.628 Found Redist 2005 product definition
05/16/2007 13:05:35.644 Found Redist 2005 product definition
05/16/2007 13:05:35.660 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.675 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.675 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.691 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:35.909 Found Redist 2005 product definition
05/16/2007 13:05:35.925 Found Redist 2005 product definition
05/16/2007 13:05:35.941 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.941 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.956 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.972 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:36.128 Found Redist 2005 product definition
05/16/2007 13:05:36.191 Product Enumeration Results:
05/16/2007 13:05:36.206 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlncli.inf
05/16/2007 13:05:36.222 baselinebuild = 1399
05/16/2007 13:05:36.237 build = 3042
05/16/2007 13:05:36.253 description = SQL Server Native Client
05/16/2007 13:05:36.269 details = Service Pack per Microsoft SQL Server Native Client.
05/16/2007 13:05:36.284 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:36.300 kbarticle = KB921896
05/16/2007 13:05:36.316 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:36.331 lcid = 1040
05/16/2007 13:05:36.347 legalproductname = Microsoft SQL Native Client
05/16/2007 13:05:36.362 machinetype = x86
05/16/2007 13:05:36.362 package = HotFixSqlncli
05/16/2007 13:05:36.378 packagetype = Hotfix
05/16/2007 13:05:36.394 productcode = {BA06B694-0CFE-4A3E-81A7-9CED25B74E2B}
05/16/2007 13:05:36.409 productname = Redist9
05/16/2007 13:05:36.425 recommendinstall = 1
05/16/2007 13:05:36.441 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:36.456 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:36.472 splevel = 2
05/16/2007 13:05:36.487 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:36.519 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:36.519 upgradecode = {A6B19337-7392-4765-8675-5C25B758BA37}
05/16/2007 13:05:36.534 version = 9
05/16/2007 13:05:36.550
05/16/2007 13:05:36.581 File Group Details: MSI
05/16/2007 13:05:36.597 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:36.612 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:36.628 File Details: sqlncli.msi
05/16/2007 13:05:36.644
05/16/2007 13:05:36.659 Instance Details: SQL Server Native Client
05/16/2007 13:05:36.690 fullversion = 9.00.3042.00
05/16/2007 13:05:36.706 lcid = 1040
05/16/2007 13:05:36.722 productcode = {BA06B694-0CFE-4A3E-81A7-9CED25B74E2B}
05/16/2007 13:05:36.753 qfelevel = 3042
05/16/2007 13:05:36.769 sp = -1
05/16/2007 13:05:36.784
05/16/2007 13:05:36.800 Product Enumeration Results:
05/16/2007 13:05:36.831 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlncli_x64.inf
05/16/2007 13:05:36.847 baselinebuild = 1399
05/16/2007 13:05:36.862 build = 3042
05/16/2007 13:05:36.878 description = SQL Server Native Client
05/16/2007 13:05:36.893 details = Service Pack per Microsoft SQL Server Native Client.
05/16/2007 13:05:36.909 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:36.940 kbarticle = KB921896
05/16/2007 13:05:36.956 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:36.972 lcid = 1040
05/16/2007 13:05:36.987 legalproductname = Microsoft SQL Native Client (64 bit)
05/16/2007 13:05:37.018 machinetype = x64
05/16/2007 13:05:37.034 package = HotFixSqlncli_x64
05/16/2007 13:05:37.050 packagetype = Hotfix
05/16/2007 13:05:37.081 productname = Redist9
05/16/2007 13:05:37.097 recommendinstall = 1
05/16/2007 13:05:37.112 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:37.128 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:37.159 splevel = 2
05/16/2007 13:05:37.175 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:37.190 upgradecode = {6EC3319D-84BE-4C32-AA91-7D6057CF05A5}
05/16/2007 13:05:37.206 version = 9
05/16/2007 13:05:37.237
05/16/2007 13:05:37.253 File Group Details: MSI
05/16/2007 13:05:37.268 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:37.284 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:37.315 File Details: sqlncli_x64.msi
05/16/2007 13:05:37.331
05/16/2007 13:05:37.346 Product Enumeration Results:
05/16/2007 13:05:37.362 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlSupport.inf
05/16/2007 13:05:37.393 alwaysinstall = 1
05/16/2007 13:05:37.409 baselinebuild = 1399
05/16/2007 13:05:37.425 build = 3042
05/16/2007 13:05:37.456 description = File di supporto dell'installazione
05/16/2007 13:05:37.534 details = Service Pack per i file di supporto dell'installazione di SQL Server.
05/16/2007 13:05:37.565 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:37.581 kbarticle = KB921896
05/16/2007 13:05:37.596 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:37.612 keyqualifier = 1
05/16/2007 13:05:37.643 lcid = 1040
05/16/2007 13:05:37.659 legalproductname = File di supporto dell'installazione di SQL Server 2005
05/16/2007 13:05:37.674 machinetype = x86
05/16/2007 13:05:37.690 package = HotFixSqlSupport
05/16/2007 13:05:37.690 packagetype = Hotfix
05/16/2007 13:05:37.706 productcode = {6379FD0A-8964-4A50-80A6-B20B65117905}
05/16/2007 13:05:37.737 productname = Redist9
05/16/2007 13:05:37.753 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:37.768 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:37.784 splevel = 2
05/16/2007 13:05:37.815 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:37.831 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:37.846 upgradecode = {3A91FA19-A197-467C-850F-0AFE90899371}
05/16/2007 13:05:37.862 version = 9
05/16/2007 13:05:37.877
05/16/2007 13:05:37.893 File Group Details: MSI
05/16/2007 13:05:37.909 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCacheSQLSupport<MachineType><LCID>
05/16/2007 13:05:37.940 parameters = REINSTALL=ALL
05/16/2007 13:05:37.956 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:37.971 File Details: SqlSupport.msi
05/16/2007 13:05:37.987
05/16/2007 13:05:38.002 Instance Details: File di supporto dell'installazione
05/16/2007 13:05:38.018 fullversion = 9.2.3042
05/16/2007 13:05:38.049 lcid = 1040
05/16/2007 13:05:38.065 productcode = {6379FD0A-8964-4A50-80A6-B20B65117905}
05/16/2007 13:05:38.081 qfelevel = 3042
05/16/2007 13:05:38.096 sp = -1
05/16/2007 13:05:38.112
05/16/2007 13:05:38.143 Product Enumeration Results:
05/16/2007 13:05:38.159 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQL.inf
05/16/2007 13:05:38.174 baselinebuild = 1399
05/16/2007 13:05:38.190 baselinebuildmax = 3042
05/16/2007 13:05:38.205 build = 3042
05/16/2007 13:05:38.221 description = Servizi di database
05/16/2007 13:05:38.237 details = Service Pack per il Motore di database e gli strumenti di SQL Server per la gestione di dati relazionali e XML, per la replica e per la ricerca full-text.
05/16/2007 13:05:38.252 installer = Hotfix
05/16/2007 13:05:38.268 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:38.284 kbarticle = KB921896
05/16/2007 13:05:38.299 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:38.330 lcid = 1040
05/16/2007 13:05:38.346 legalproductname = Servizi di database SQL Server 2005
05/16/2007 13:05:38.362 machinetype = x86
05/16/2007 13:05:38.393 package = HotFixSQL
05/16/2007 13:05:38.409 packagetype = Hotfix
05/16/2007 13:05:38.424 productname = SQL9
05/16/2007 13:05:38.440 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:38.471 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:38.487 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/16/2007 13:05:38.502 splevel = 2
05/16/2007 13:05:38.518 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:38.549 sqlutility = sqlcmd.exe
05/16/2007 13:05:38.565 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:38.580 validateauthentication = true
05/16/2007 13:05:38.596 version = 9
05/16/2007 13:05:38.612
05/16/2007 13:05:38.627 File Group Details: MSP
05/16/2007 13:05:38.658 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:38.674 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:38.690 File Details: sqlrun_sql.msp
05/16/2007 13:05:38.705
05/16/2007 13:05:38.721 Instance Details: MSSQLSERVER
05/16/2007 13:05:38.752 agentservicename = SQLSERVERAGENT
05/16/2007 13:05:38.768 clustername =
05/16/2007 13:05:38.783 default = TRUE
05/16/2007 13:05:38.815 ftsservicename = MSFTESQL
05/16/2007 13:05:38.830 fullversion = 2005.090.1399.00
05/16/2007 13:05:38.846 hiveregpath = SoftwareMicrosoftMicrosoft SQL ServerMSSQL.1
05/16/2007 13:05:38.877 id = MSSQL.1
05/16/2007 13:05:38.893 installsqldatadir = C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQL
05/16/2007 13:05:38.908 installsqldir = C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQL
05/16/2007 13:05:38.924 lcid = 1040
05/16/2007 13:05:38.940 name = MSSQLSERVER
05/16/2007 13:05:38.971 productcode = {E0BB3923-308B-4BE9-B3A3-FD5517481E48}
05/16/2007 13:05:39.002 qfelevel = 1399
05/16/2007 13:05:39.018 servicename = MSSQLServer
05/16/2007 13:05:39.033 sku = STANDARD
05/16/2007 13:05:39.049 sp = 0
05/16/2007 13:05:39.065 type = SQL Server Standalone Product
05/16/2007 13:05:39.096 vermajbld = 1399
05/16/2007 13:05:39.111 version = 9
05/16/2007 13:05:39.127
05/16/2007 13:05:39.143 Product Enumeration Results:
05/16/2007 13:05:39.174 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixAS.inf
05/16/2007 13:05:39.189 baselinebuild = 1399
05/16/2007 13:05:39.205 baselinebuildmax = 3042
05/16/2007 13:05:39.236 build = 3042
05/16/2007 13:05:39.252 description = Analysis Services
05/16/2007 13:05:39.268 details = Service Pack per Analysis Services e per gli strumenti per il supporto dell'elaborazione analitica in linea (OLAP) e del data mining.
05/16/2007 13:05:39.283 installer = Hotfix
05/16/2007 13:05:39.299 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:39.330 kbarticle = KB921896
05/16/2007 13:05:39.346 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:39.361 lcid = 1040
05/16/2007 13:05:39.377 legalproductname = SQL Server Analysis Services 2005
05/16/2007 13:05:39.408 machinetype = x86
05/16/2007 13:05:39.424 package = HotFixAS
05/16/2007 13:05:39.455 packagetype = Hotfix
05/16/2007 13:05:39.471 productname = OLAP9
05/16/2007 13:05:39.486 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:39.502 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:39.533 splevel = 2
05/16/2007 13:05:39.549 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:39.564 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:39.580 version = 9
05/16/2007 13:05:39.611
05/16/2007 13:05:39.627 File Group Details: MSP
05/16/2007 13:05:39.642 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:39.674 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:39.689 File Details: sqlrun_as.msp
05/16/2007 13:05:39.705
05/16/2007 13:05:39.736 Product Enumeration Results:
05/16/2007 13:05:39.752 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixNS.inf
05/16/2007 13:05:39.767 baselinebuild = 1399
05/16/2007 13:05:39.799 baselinebuildmax = 3042
05/16/2007 13:05:39.814 build = 3042
05/16/2007 13:05:39.830 description = Notification Services
05/16/2007 13:05:39.861 details = Service Pack per Notification Services, una piattaforma per lo sviluppo e la distribuzione di applicazioni per l'invio di notifiche personalizzate e tempestive a un'ampia gamma di dispositivi o applicazioni.
05/16/2007 13:05:39.877 installer = Hotfix
05/16/2007 13:05:39.892 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:39.908 kbarticle = KB921896
05/16/2007 13:05:39.924 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:39.939 lcid = 1040
05/16/2007 13:05:39.970 legalproductname = Istanze di SQL Server Notification Services 2005
05/16/2007 13:05:39.986 machinetype = x86
05/16/2007 13:05:40.002 package = HotFixNS
05/16/2007 13:05:40.017 packagetype = Hotfix
05/16/2007 13:05:40.033 productname = NS9
05/16/2007 13:05:40.064 recommendinstall = 1
05/16/2007 13:05:40.080 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:40.095 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:40.111 splevel = 2
05/16/2007 13:05:40.142 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:40.158 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:40.189 version = 9
05/16/2007 13:05:40.205
05/16/2007 13:05:40.220 File Group Details: MSP
05/16/2007 13:05:40.236 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:40.267 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:40.283 File Details: sqlrun_ns.msp
05/16/2007 13:05:40.298
05/16/2007 13:05:40.330 Product Enumeration Results:
05/16/2007 13:05:40.345 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixRS.inf
05/16/2007 13:05:40.361 baselinebuild = 1399
05/16/2007 13:05:40.376 baselinebuildmax = 3042
05/16/2007 13:05:40.408 build = 3042
05/16/2007 13:05:40.423 description = Reporting Services
05/16/2007 13:05:40.439 details = Service Pack per Server report e Generatore report, utilizzati per la gestione, l'esecuzione, il rendering e la distribuzione dei report.
05/16/2007 13:05:40.455 installer = Hotfix
05/16/2007 13:05:40.486 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:40.501 kbarticle = KB921896
05/16/2007 13:05:40.517 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:40.548 lcid = 1040
05/16/2007 13:05:40.564 legalproductname = SQL Server Reporting Services 2005
05/16/2007 13:05:40.580 machinetype = x86
05/16/2007 13:05:40.611 package = HotFixRS
05/16/2007 13:05:40.626 packagetype = Hotfix
05/16/2007 13:05:40.642 productname = RS9
05/16/2007 13:05:40.658 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:40.673 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:40.689 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/16/2007 13:05:40.720 splevel = 2
05/16/2007 13:05:40.736 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:40.751 sqlutility = sqlcmd.exe
05/16/2007 13:05:40.767 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:40.798 validateauthentication = 1
05/16/2007 13:05:40.814 version = 9
05/16/2007 13:05:40.829
05/16/2007 13:05:40.861 File Group Details: MSP
05/16/2007 13:05:40.876 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:40.892 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:40.908 File Details: sqlrun_rs.msp
05/16/2007 13:05:40.939
05/16/2007 13:05:40.954 Product Enumeration Results:
05/16/2007 13:05:40.970 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixDTS.inf
05/16/2007 13:05:41.001 baselinebuild = 1399
05/16/2007 13:05:41.017 baselinebuildmax = 3042
05/16/2007 13:05:41.032 build = 3042
05/16/2007 13:05:41.064 description = Integration Services
05/16/2007 13:05:41.079 details = Service Pack per Integration Services, una serie di strumenti e oggetti programmabili per la creazione e la gestione di pacchetti per l'estrazione, la trasformazione e il caricamento dei dati, nonché per l'esecuzione di attività .
05/16/2007 13:05:41.095 installer = Hotfix
05/16/2007 13:05:41.126 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:41.142 kbarticle = KB921896
05/16/2007 13:05:41.157 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:41.173 lcid = 1040
05/16/2007 13:05:41.189 legalproductname = SQL Server Integration Services 2005
05/16/2007 13:05:41.220 machinetype = x86
05/16/2007 13:05:41.236 package = HotFixDTS
05/16/2007 13:05:41.251 packagetype = Hotfix
05/16/2007 13:05:41.282 productname = DTS9
05/16/2007 13:05:41.298 recommendinstall = 1
05/16/2007 13:05:41.314 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:41.329 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:41.360 splevel = 2
05/16/2007 13:05:41.376 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:41.392 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:41.423 version = 9
05/16/2007 13:05:41.439
05/16/2007 13:05:41.454 File Group Details: MSP
05/16/2007 13:05:41.485 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:41.501 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:41.517 File Details: sqlrun_dts.msp
05/16/2007 13:05:41.548
05/16/2007 13:05:41.564 Product Enumeration Results:
05/16/2007 13:05:41.579 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixTools.inf
05/16/2007 13:05:41.610 baselinebuild = 1399
05/16/2007 13:05:41.626 baselinebuildmax = 3042
05/16/2007 13:05:41.642 build = 3042
05/16/2007 13:05:41.657 description = Componenti client
05/16/2007 13:05:41.688 details = Service Pack per gli strumenti interattivi di gestione per l'esecuzione di SQL Server, tra cui Gestione configurazione SQL Server, SQL Server Management Studio, SQL Profiler e Monitoraggio replica.
05/16/2007 13:05:41.704 installer = Hotfix
05/16/2007 13:05:41.720 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:41.751 kbarticle = KB921896
05/16/2007 13:05:41.767 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:41.782 lcid = 1040
05/16/2007 13:05:41.798 legalproductname = Componenti workstation e strumenti di SQL Server 2005
05/16/2007 13:05:41.829 machinetype = x86
05/16/2007 13:05:41.845 package = HotFixTools
05/16/2007 13:05:41.860 packagetype = Hotfix
05/16/2007 13:05:41.876 productname = SQLTools9
05/16/2007 13:05:41.892 recommendinstall = 1
05/16/2007 13:05:41.923 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:41.938 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:41.954 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/16/2007 13:05:41.985 splevel = 2
05/16/2007 13:05:42.001 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:42.016 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:42.032 version = 9
05/16/2007 13:05:42.063
05/16/2007 13:05:42.079 File Group Details: MSP
05/16/2007 13:05:42.095 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:42.110 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:42.141 File Details: sqlrun_tools.msp
05/16/2007 13:05:42.157
05/16/2007 13:05:42.188 Instance Details: SQL Tools
05/16/2007 13:05:42.204 associatedhotfixbuild = 1520
05/16/2007 13:05:42.220 clustername =
05/16/2007 13:05:42.235 fullversion = 9.2.3042
05/16/2007 13:05:42.266 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90Tools
05/16/2007 13:05:42.282 id =
05/16/2007 13:05:42.298 installsqldatadir =
05/16/2007 13:05:42.313 installsqldir = C:ProgrammiMicrosoft SQL Server90Tools
05/16/2007 13:05:42.329 lcid = 1040
05/16/2007 13:05:42.360 name =
05/16/2007 13:05:42.376 productcode = {B03FBBA3-CCE4-40CC-A0F1-01F952E7EB3E}
05/16/2007 13:05:42.391 qfelevel = 3042
05/16/2007 13:05:42.407 sku = STANDARD
05/16/2007 13:05:42.438 sp = 2
05/16/2007 13:05:42.454 type = Tools Only
05/16/2007 13:05:42.469 vermajbld = 3042
05/16/2007 13:05:42.501 version = 9
05/16/2007 13:05:42.516
05/16/2007 13:05:42.532 Product Enumeration Results:
05/16/2007 13:05:42.563 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixMsxml6.inf
05/16/2007 13:05:42.579 baselinebuild = 1399
05/16/2007 13:05:42.594 build = 6.10.1129.0
05/16/2007 13:05:42.626 description = Parser MSXML 6.0
05/16/2007 13:05:42.641 details = Service Pack per il parser Microsoft XML 6.0.
05/16/2007 13:05:42.657 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:42.688 kbarticle = KB921896
05/16/2007 13:05:42.704 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:42.719 lcid = 1040
05/16/2007 13:05:42.751 legalproductname = Parser MSXML 6.0
05/16/2007 13:05:42.766 machinetype = x86
05/16/2007 13:05:42.782 package = HotFixMsxml6
05/16/2007 13:05:42.797 packagetype = Hotfix
05/16/2007 13:05:42.813 productcode = {8919A89C-D378-4899-BE19-12893E4DCCEE}
05/16/2007 13:05:42.844 productname = Redist9
05/16/2007 13:05:42.860 recommendinstall = 1
05/16/2007 13:05:42.876 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:42.891 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:42.922 splevel = 2
05/16/2007 13:05:42.938 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:42.969 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:42.985 upgradecode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
05/16/2007 13:05:43.000 version = 9
05/16/2007 13:05:43.016
05/16/2007 13:05:43.032 File Group Details: MSI
05/16/2007 13:05:43.063 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:43.079 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:43.094 File Details: msxml6.msi
05/16/2007 13:05:43.110
05/16/2007 13:05:43.141 Instance Details: Parser MSXML 6.0
05/16/2007 13:05:43.157 fullversion = 6.10.1129.0
05/16/2007 13:05:43.172 lcid = 1040
05/16/2007 13:05:43.188 productcode = {8919A89C-D378-4899-BE19-12893E4DCCEE}
05/16/2007 13:05:43.219 qfelevel = 1129
05/16/2007 13:05:43.235 sp = -1
05/16/2007 13:05:43.250
05/16/2007 13:05:43.266 Product Enumeration Results:
05/16/2007 13:05:43.297 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixMsxml6_x64.inf
05/16/2007 13:05:43.313 baselinebuild = 1399
05/16/2007 13:05:43.328 build = 6.10.1129.0
05/16/2007 13:05:43.360 description = Parser MSXML 6.0
05/16/2007 13:05:43.375 details = Service Pack per il parser Microsoft XML 6.0.
05/16/2007 13:05:43.391 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:43.422 kbarticle = KB921896
05/16/2007 13:05:43.438 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:43.453 lcid = 1040
05/16/2007 13:05:43.469 legalproductname = Parser MSXML 6.0 (64 bit)
05/16/2007 13:05:43.500 machinetype = x64
05/16/2007 13:05:43.516 package = HotFixMsxml6_x64
05/16/2007 13:05:43.532 packagetype = Hotfix
05/16/2007 13:05:43.563 productname = Redist9
05/16/2007 13:05:43.578 recommendinstall = 1
05/16/2007 13:05:43.594 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:43.610 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:43.625 splevel = 2
05/16/2007 13:05:43.641 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:43.656 upgradecode = {5BBED1F8-E6F3-4A02-BC97-26D35BE200CA}
05/16/2007 13:05:43.672 version = 9
05/16/2007 13:05:43.688
05/16/2007 13:05:43.703 File Group Details: MSI
05/16/2007 13:05:43.719 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:43.735 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:43.750 File Details: msxml6_x64.msi
05/16/2007 13:05:43.781
05/16/2007 13:05:43.797 Product Enumeration Results:
05/16/2007 13:05:43.813 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlxml4.inf
05/16/2007 13:05:43.828 baselinebuild = 1399
05/16/2007 13:05:43.844 build = 3042
05/16/2007 13:05:43.860 description = SQLXML4
05/16/2007 13:05:43.875 details = Service Pack per Microsoft SQLXML 4.0.
05/16/2007 13:05:43.891 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:43.906 kbarticle = KB921896
05/16/2007 13:05:43.922 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:43.938 lcid = 1040
05/16/2007 13:05:43.953 legalproductname = SQLXML4
05/16/2007 13:05:43.969 machinetype = x86
05/16/2007 13:05:43.984 package = HotFixSqlxml4
05/16/2007 13:05:44.000 packagetype = Hotfix
05/16/2007 13:05:44.016 productname = Redist9
05/16/2007 13:05:44.047 recommendinstall = 1
05/16/2007 13:05:44.063 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:44.078 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:44.094 splevel = 2
05/16/2007 13:05:44.109 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:44.125 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:44.141 upgradecode = {D9CA3D82-6F1B-41A7-8141-B90ACA8F865B}
05/16/2007 13:05:44.156 version = 9
05/16/2007 13:05:44.172
05/16/2007 13:05:44.188 File Group Details: MSI
05/16/2007 13:05:44.203 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:44.219 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:44.234 File Details: sqlxml4.msi
05/16/2007 13:05:44.266
05/16/2007 13:05:44.281 Product Enumeration Results:
05/16/2007 13:05:44.297 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlxml4_x64.inf
05/16/2007 13:05:44.312 baselinebuild = 1399
05/16/2007 13:05:44.328 build = 3042
05/16/2007 13:05:44.344 description = SQLXML4
05/16/2007 13:05:44.375 details = Service Pack per Microsoft SQLXML 4.0.
05/16/2007 13:05:44.391 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:44.391 kbarticle = KB921896
05/16/2007 13:05:44.422 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:44.422 lcid = 1040
05/16/2007 13:05:44.437 legalproductname = SQLXML4 (64 bit)
05/16/2007 13:05:44.453 machinetype = x64
05/16/2007 13:05:44.469 package = HotFixSqlxml4_x64
05/16/2007 13:05:44.484 packagetype = Hotfix
05/16/2007 13:05:44.500 productname = Redist9
05/16/2007 13:05:44.516 recommendinstall = 1
05/16/2007 13:05:44.531 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:44.547 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:44.562 splevel = 2
05/16/2007 13:05:44.594 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:44.609 upgradecode = {F457D8E6-7686-437D-9B17-E21D45CCABD8}
05/16/2007 13:05:44.625 version = 9
05/16/2007 13:05:44.640
05/16/2007 13:05:44.656 File Group Details: MSI
05/16/2007 13:05:44.672 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:44.687 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:44.703 File Details: sqlxml4_x64.msi
05/16/2007 13:05:44.719
05/16/2007 13:05:44.734 Product Enumeration Results:
05/16/2007 13:05:44.750 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQLServer2005_BC.inf
05/16/2007 13:05:44.765 baselinebuild = 1399
05/16/2007 13:05:44.781 build = 2004
05/16/2007 13:05:44.797 description = Compatibilità con le versioni precedenti
05/16/2007 13:05:44.812 details = Service Pack per i componenti per la compatibilità con le versioni precedenti, tra cui Data Transformation Services Runtime e SQL-DMO.
05/16/2007 13:05:44.828 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:44.844 kbarticle = KB921896
05/16/2007 13:05:44.859 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:44.875 lcid = 1040
05/16/2007 13:05:44.890 legalproductname = Compatibilità con le versioni precedenti a Microsoft SQL Server 2005
05/16/2007 13:05:44.906 machinetype = x86
05/16/2007 13:05:44.922 package = HotFixSQLServer2005_BC
05/16/2007 13:05:44.937 packagetype = Hotfix
05/16/2007 13:05:44.953 productcode = {B532F403-16FA-4433-929C-3768090D70E3}
05/16/2007 13:05:44.968 productname = Redist9
05/16/2007 13:05:44.984 recommendinstall = 1
05/16/2007 13:05:45.015 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:45.031 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:45.047 splevel = 2
05/16/2007 13:05:45.062 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:45.078 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:45.093 upgradecode = {1E70C6C9-E1B7-4A74-BC8C-8EB5D010CEC9}
05/16/2007 13:05:45.109 version = 9
05/16/2007 13:05:45.125
05/16/2007 13:05:45.140 File Group Details: MSI
05/16/2007 13:05:45.171 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:45.187 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:45.203 File Details: SQLServer2005_BC.msi
05/16/2007 13:05:45.203
05/16/2007 13:05:45.218 Instance Details: Compatibilità con le versioni precedenti
05/16/2007 13:05:45.234 fullversion = 8.05.2004
05/16/2007 13:05:45.250 lcid = 1040
05/16/2007 13:05:45.265 productcode = {B532F403-16FA-4433-929C-3768090D70E3}
05/16/2007 13:05:45.281 qfelevel = 2004
05/16/2007 13:05:45.296 sp = -1
05/16/2007 13:05:45.312
05/16/2007 13:05:45.328 Product Enumeration Results:
05/16/2007 13:05:45.343 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQLServer2005_BC_x64.inf
05/16/2007 13:05:45.375 baselinebuild = 1399
05/16/2007 13:05:45.375 build = 2004
05/16/2007 13:05:45.390 description = Compatibilità con le versioni precedenti
05/16/2007 13:05:45.406 details = Service Pack per i componenti per la compatibilità con le versioni precedenti, tra cui Data Transformation Services Runtime e SQL-DMO.
05/16/2007 13:05:45.421 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:45.453 kbarticle = KB921896
05/16/2007 13:05:45.453 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:45.468 lcid = 1040
05/16/2007 13:05:45.484 legalproductname = Compatibilità con le versioni precedenti a Microsoft SQL Server 2005 (64 bit)
05/16/2007 13:05:45.500 machinetype = x64
05/16/2007 13:05:45.515 package = HotFixSQLServer2005_BC_x64
05/16/2007 13:05:45.531 packagetype = Hotfix
05/16/2007 13:05:45.546 productname = Redist9
05/16/2007 13:05:45.562 recommendinstall = 1
05/16/2007 13:05:45.578 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:45.593 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:45.609 splevel = 2
05/16/2007 13:05:45.624 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:45.640 upgradecode = {7B6BF434-3C72-4DB3-8049-FEF31AEAFF9A}
05/16/2007 13:05:45.656 version = 9
05/16/2007 13:05:45.671
05/16/2007 13:05:45.703 File Group Details: MSI
05/16/2007 13:05:45.718 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:45.734 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:45.749 File Details: SQLServer2005_BC_x64.msi
05/16/2007 13:05:45.765
05/16/2007 13:05:45.781 Product Enumeration Results:
05/16/2007 13:05:45.796 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlWriter.inf
05/16/2007 13:05:45.812 baselinebuild = 1399
05/16/2007 13:05:45.828 build = 3042
05/16/2007 13:05:45.843 description = Microsoft SQL Server VSS Writer
05/16/2007 13:05:45.874 details = Service Pack per Microsoft SQL Server VSS Writer.
05/16/2007 13:05:45.890 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:45.906 kbarticle = KB921896
05/16/2007 13:05:45.921 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:45.937 lcid = 1040
05/16/2007 13:05:45.953 legalproductname = Microsoft SQL Server VSS Writer
05/16/2007 13:05:45.968 machinetype = x86
05/16/2007 13:05:45.984 package = HotFixSqlWriter
05/16/2007 13:05:45.999 packagetype = Hotfix
05/16/2007 13:05:46.015 productcode = {DCEFDFAB-9543-4F03-ADAE-F6729C2B9966}
05/16/2007 13:05:46.031 productname = Redist9
05/16/2007 13:05:46.062 recommendinstall = 1
05/16/2007 13:05:46.078 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:46.093 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:46.109 splevel = 2
05/16/2007 13:05:46.124 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:46.140 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:46.156 upgradecode = {65D8E1DF-6201-4B53-A0F9-E654F8E80F97}
05/16/2007 13:05:46.171 version = 9
05/16/2007 13:05:46.187
05/16/2007 13:05:46.203 File Group Details: MSI
05/16/2007 13:05:46.218 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:46.234 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:46.249 File Details: SqlWriter.msi
05/16/2007 13:05:46.281
05/16/2007 13:05:46.296 Instance Details: Microsoft SQL Server VSS Writer
05/16/2007 13:05:46.312 fullversion = 9.00.3042.00
05/16/2007 13:05:46.328 lcid = 1040
05/16/2007 13:05:46.328 productcode = {DCEFDFAB-9543-4F03-ADAE-F6729C2B9966}
05/16/2007 13:05:46.359 qfelevel = 3042
05/16/2007 13:05:46.374 sp = -1
05/16/2007 13:05:46.390
05/16/2007 13:05:46.406 Product Enumeration Results:
05/16/2007 13:05:46.421 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlWriter_x64.inf
05/16/2007 13:05:46.437 baselinebuild = 1399
05/16/2007 13:05:46.453 build = 3042
05/16/2007 13:05:46.468 description = Microsoft SQL Server VSS Writer
05/16/2007 13:05:46.484 details = Service Pack per Microsoft SQL Server VSS Writer.
05/16/2007 13:05:46.499 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:46.515 kbarticle = KB921896
05/16/2007 13:05:46.546 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:46.562 lcid = 1040
05/16/2007 13:05:46.577 legalproductname = Microsoft SQL Server VSS Writer (64 bit)
05/16/2007 13:05:46.593 machinetype = x64
05/16/2007 13:05:46.609 package = HotFixSqlWriter_x64
05/16/2007 13:05:46.640 packagetype = Hotfix
05/16/2007 13:05:46.656 productname = Redist9
05/16/2007 13:05:46.671 recommendinstall = 1
05/16/2007 13:05:46.687 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:46.718 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:46.734 splevel = 2
05/16/2007 13:05:46.749 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:46.781 upgradecode = {E9031696-DD39-4C25-BAEB-425FF28279EA}
05/16/2007 13:05:46.796 version = 9
05/16/2007 13:05:46.796
05/16/2007 13:05:46.827 File Group Details: MSI
05/16/2007 13:05:46.843 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:46.859 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:46.874 File Details: SqlWriter_x64.msi
05/16/2007 13:05:46.890
05/16/2007 13:05:57.967 Registry: Opened registry key "SystemCurrentControlSetControlSession Manager"
05/16/2007 13:05:57.967 Registry: Read registry key value "PendingFileRenameOperations"
05/16/2007 13:05:57.982 Multi-string values:
05/16/2007 13:05:57.998 Registry: Read registry key value "PendingFileRenameOperations"
05/16/2007 13:05:58.014 Multi-string values:
05/16/2007 13:05:58.029 ??e:1971703f8a5eaa69b207
05/16/2007 13:05:58.045 PFR Check: PFR was found, but no files to be serviced were being referenced
05/16/2007 13:06:18.980 Authenticating user using SAPWD
05/16/2007 13:06:18.995 SQL Service MSSQLServer was not previously running, started for authentication
05/16/2007 13:06:19.011 Starting service: MSSQLServer
05/16/2007 13:06:23.666 Started service: MSSQLServer
05/16/2007 13:06:23.729 SQL Agent Service SQLSERVERAGENT was not previously running
05/16/2007 13:06:24.323 User authentication failed
05/16/2007 13:06:24.354 Messaggio 18456, livello 14, stato 1, server DC-01, riga 1
05/16/2007 13:06:24.385 Accesso non riuscito per l'utente 'sa'.
05/16/2007 13:06:24.416 Stopping service: MSSQLServer
05/16/2007 13:06:26.432 Stopped service: MSSQLServer
05/16/2007 13:06:29.978 Authenticating user using Windows Authentication
05/16/2007 13:06:29.994 SQL Service MSSQLServer was not previously running, started for authentication
05/16/2007 13:06:30.009 Starting service: MSSQLServer
05/16/2007 13:06:34.837 Started service: MSSQLServer
05/16/2007 13:06:34.931 SQL Agent Service SQLSERVERAGENT was not previously running
05/16/2007 13:06:35.462 Authenticating user using Windows Authentication
05/16/2007 13:06:35.477 Validating database connections using Windows Authentication
05/16/2007 13:06:35.868 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:36.337 Received sysadmin status for instance: MSSQLSERVER
05/16/2007 13:06:36.352 Validating database connections using Windows Authentication
05/16/2007 13:06:36.680 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:36.696 User authentication was successful
05/16/2007 13:06:36.696 Stopping service: MSSQLServer
05/16/2007 13:06:38.711 Stopped service: MSSQLServer
05/16/2007 13:06:40.461 Authenticating user using Windows Authentication
05/16/2007 13:06:40.477 SQL Service MSSQLServer was not previously running, started for authentication
05/16/2007 13:06:40.492 Starting service: MSSQLServer
05/16/2007 13:06:45.086 Started service: MSSQLServer
05/16/2007 13:06:45.101 SQL Agent Service SQLSERVERAGENT was not previously running
05/16/2007 13:06:45.523 Authenticating user using Windows Authentication
05/16/2007 13:06:45.539 Validating database connections using Windows Authentication
05/16/2007 13:06:46.085 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:46.414 Received sysadmin status for instance: MSSQLSERVER
05/16/2007 13:06:46.429 Validating database connections using Windows Authentication
05/16/2007 13:06:46.742 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:46.757 User authentication was successful
05/16/2007 13:06:46.773 Stopping service: MSSQLServer
05/16/2007 13:06:48.788 Stopped service: MSSQLServer
05/16/2007 13:06:48.835 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:48.851 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:48.866 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:48.882 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:55.287 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:55.303 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:55.319 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:55.319 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:55.662 Locked file: Checking for locked files
05/16/2007 13:07:05.099 Attempting to pause the 32 bit ngen queue
05/16/2007 13:07:05.271 Installing product: SQL9
05/16/2007 13:07:05.286 Installing instance: MSSQLSERVER
05/16/2007 13:07:05.302 Installing target: DC-01
05/16/2007 13:07:05.317 Installing file: sqlrun_sql.msp
05/16/2007 13:07:05.349 Copy Engine: Creating MSP install log file at: C:ProgrammiMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
05/16/2007 13:07:05.364 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
05/16/2007 13:07:05.380 Registry: Cannot read registry key value "Debug"
05/16/2007 13:09:06.458 MSP Error: 29506 Impossibile modificare le autorizzazioni di protezione del file C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQLData per l'utente SYSTEM. Per continuare, verificare l'esistenza dell'account e del dominio che eseguono l'installazione di SQL Server. Verificare inoltre che tale account disponga dei privilegi di amministratore e che sia presente nell'unità di destinazione.
05/16/2007 13:10:03.685 MSP returned 1603: Si è verificato un errore irreversibile durante l'installazione.
05/16/2007 13:10:03.701 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
05/16/2007 13:10:03.716 Registry: Cannot read registry key value "Debug"
05/16/2007 13:10:04.248 Copy Engine: Error, unable to install MSP file: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQLFilessqlrun_sql.msp
05/16/2007 13:10:04.310 The following exception occurred: Impossibile installare il file MSP di Windows Installer Date: 05/16/2007 13:10:04.310 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 800
05/16/2007 13:10:08.966 Watson: Param1 = Do_sqlFileSDDL
05/16/2007 13:10:08.997 Watson: Param2 = 0x7342
05/16/2007 13:10:09.044 Watson: Param3 = ExceptionInSDDL
05/16/2007 13:10:09.075 Watson: Param4 = 0x7342
05/16/2007 13:10:09.106 Watson: Param5 = sqlcasqlsddlca.cpp@65
05/16/2007 13:10:09.153 Watson: Param6 = Unknown
05/16/2007 13:10:09.184 Watson: Param7 = SQL9
05/16/2007 13:10:09.200 Watson: Param8 = Hotfix@
05/16/2007 13:10:09.231 Watson: Param9 = x86
05/16/2007 13:10:09.247 Watson: Param10 = 3042
05/16/2007 13:10:09.309 Installed product: SQL9
05/16/2007 13:10:09.356 Hotfix package completed
05/16/2007 13:10:09.388 Attempting to continue the 32 bit ngen queue

View 1 Replies View Related

Sql Server 2005 Dev Edition Error - Unexpected Error While Updating Installed Files

Feb 14, 2007

I am attempting to install SQL Server 2005 Developer Edition onto a Windows XP Pro SP2 machine, but unfortunately each time that I attempt to install I receive an error message in the summary log as follows:

Product : Microsoft SQL Server 2005
Product Version: 9.00.1399.06
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup
Last Action : InstallFinalize
Error String : The setup has encountered an unexpected error while Updating Installed Files.
The error is : Fatal error during installation.
Error Number : 29528

There is probably a simple solution for the issue but unfortunately I am unaware of what it is? I can€™t tell if the issue is specific to registry settings, security, file types, etc€¦ The information below surrounds the error w/in the log, any suggestions would be greatly appreciated?

Thanks, Jennifer

MSI (s) (6C:94) [16:02:23:713]: Executing op: SetTargetFolder(Folder=C:WINNTsystem32)
MSI (s) (6C:94) [16:02:23:713]: Executing op: SetSourceFolder(Folder=1System)
MSI (s) (6C:94) [16:02:23:713]: Executing op: FileCopy(SourceName=sqlctr90.dll,SourceCabKey=sqlctr90.dll.7188DA12_A95E_46B7_8623_9D93B5260E2A,DestName=sqlctr90.dll,Attributes=16384,FileSize=66264,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,Version=2005.90.1399.0,Language=1033,InstallMode=58982400,,,,,,,)
MSI (s) (6C:94) [16:02:23:713]: File: C:WINNTsystem32sqlctr90.dll; To be installed; Won't patch; No existing file
MSI (s) (6C:94) [16:02:23:713]: Source for file 'sqlctr90.dll.7188DA12_A95E_46B7_8623_9D93B5260E2A' is compressed
MSI (s) (6C:94) [16:02:23:713]: Note: 1: 2318 2: C:WINNTsystem32sqlctr90.dll
MSI (s) (6C:94) [16:02:23:713]: Note: 1: 2360
MSI (s) (6C:94) [16:02:23:713]: Note: 1: 2360
MSI (s) (6C:94) [16:02:23:723]: Executing op: CacheSizeFlush(,)
MSI (s) (6C:94) [16:02:23:723]: Executing op: InstallProtectedFiles(AllowUI=0)
MSI (s) (6C:94) [16:02:23:723]: Executing op: ActionStart(Name=CAFTEInstallFTERef.68C6D15C_77E0_11D5_8528_00C04F68155C,,)
MSI (s) (6C:94) [16:02:23:733]: Executing op: CustomActionSchedule(Action=CAFTEInstallFTERef.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1025,Source=BinaryData,Target=InstallFTERef,CustomActionData=C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERef|C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData)
MSI (s) (6C:2C) [16:02:23:743]: Invoking remote custom action. DLL: C:WINNTInstallerMSI64E.tmp, Entrypoint: InstallFTERef
FTECa.DLL: INFO: FTE: InstallFTERef(), Entering...
FTECa.DLL: INFO: FTE: GetFTERefInstallParams: FTERef : C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData
FTECa.DLL: INFO: FTE: InstallFTERef: File created: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTDataoiseCHS.txt Size=1000 IDR=1696
.
.
.
.
.
.
FTECa.DLL: INFO: FTE: InstallFTERef: File created: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData sSVE.xml Size=1035 IDR=1142
FTECa.DLL: INFO: FTE: InstallFTERef: File created: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTDataoiseTHA.txt Size=1036 IDR=697
FTECa.DLL: INFO: FTE: InstallFTERef: File created: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData sTHA.xml Size=1037 IDR=1142
FTECa.DLL: INFO: FTE: InstallFTERef: File created: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTDataoiseTRK.txt Size=1038 IDR=2224
MSI (s) (6C:94) [16:02:24:454]: Executing op: ActionStart(Name=Rollback_UpdateETWMOFWithGUID.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Removing registry updates,)
FTECa.DLL: INFO: FTE: InstallFTERef: File created: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLFTData sTRK.xml Size=1039 IDR=1142
MSI (s) (6C:94) [16:02:24:454]: Executing op: CustomActionSchedule(Action=Rollback_UpdateETWMOFWithGUID.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1345,Source=BinaryData,Target=Rollback_UpdateETWMOFWithGUID,CustomActionData=100Removing registry updates100000{2373A92B-1C1C-4E71-B494-5CA97F96AA19}MSSQLSERVERC:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn)
MSI (s) (6C:94) [16:02:24:454]: Executing op: ActionStart(Name=Do_UpdateETWMOFWithGUID.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Updating Installed Files,)
MSI (s) (6C:94) [16:02:24:454]: Executing op: CustomActionSchedule(Action=Do_UpdateETWMOFWithGUID.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1025,Source=BinaryData,Target=Do_UpdateETWMOFWithGUID,CustomActionData=010Updating Installed Files100000{2373A92B-1C1C-4E71-B494-5CA97F96AA19}MSSQLSERVERC:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn)
MSI (s) (6C:10) [16:02:24:464]: Invoking remote custom action. DLL: C:WINNTInstallerMSI64F.tmp, Entrypoint: Do_UpdateETWMOFWithGUID
<Func Name='LaunchFunction'>
Function=Do_UpdateETWMOFWithGUID
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_UpdateETWMOFWithGUID
PerfTime Start: Do_UpdateETWMOFWithGUID : Tue Feb 13 16:02:24 2007
<Func Name='Do_UpdateETWMOFWithGUID'>
Calling installSqlEvent Trance
The arguments that are passed to InstallSqlEventTrace are InstanceName: MSSQLSERVER , ProductCodeL: {2373A92B-1C1C-4E71-B494-5CA97F96AA19} , BinPath: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
INFO: Checking installed version
INFO: Writing MOF file
ERROR: Unable to open registry key: HRESULT = 0x80070005, Key = SYSTEMCurrentControlSetControlWMISecurity

The value returned is -2147024891
<EndFunc Name='Do_UpdateETWMOFWithGUID' Return='1603' GetLastError='0'>
PerfTime Stop: Do_UpdateETWMOFWithGUID : Tue Feb 13 16:02:24 2007
Gathering darwin properties for failure handling.
Error Code: 1603
MSI (s) (6C!D0) [16:02:37:273]: Product: Microsoft SQL Server 2005 -- Error 29528. The setup has encountered an unexpected error while Updating Installed Files. The error is: Fatal error during installation.

Error 29528. The setup has encountered an unexpected error while Updating Installed Files. The error is: Fatal error during installation.

<EndFunc Name='LaunchFunction' Return='1603' GetLastError='203'>
MSI (s) (6C:94) [16:02:37:283]: User policy value 'DisableRollback' is 0
MSI (s) (6C:94) [16:02:37:283]: Machine policy value 'DisableRollback' is 0
Action ended 16:02:37: InstallFinalize. Return value 3.

View 8 Replies View Related

SQL Server 2005 Error 8630: Internal Query Processor Error

Jan 22, 2007

I have a SProc that runs across many clients without any problems. Every now and then, though, I get the following error:

Internal Query Processor Error: The query processor encountered an unexpected error during execution. [SQLSTATE 42000] (Error 8630).

All I am doing is populating Temp tables with some data and then joining them together to create a Global Temp table that is being BCP'd to a network share.

Has anyone come across this error in SQL Server 2005? I cannot find anything on Google or Microcsoft.

Thanks,
Robert

View 1 Replies View Related

SQL Server 2005 Startup Error - TDSSNIClient... Error 0x5... Code 0x51

Jul 13, 2006

Hi,My SQL Server 2005 won't start - can anyone provide some help? Thisseems to be the most significant error:- TDSSNIClient initialization failed with error 0x5, status code 0x51.There was some info here, but the reg key described looks okay:- http://blogs.msdn.com/sql_protocols/I am running SQL Server 2005 64-bit Standard Edition. The server inquestion is the first node of an Active/Active Cluster. This firststarted happening while I was trying to add a share as a clusteredresource of the other node (not to this node's resources).I have not yet reinstalled SQL Server 2005 because I am hoping for moreexplanation of the problem and a possible fix.Thanks,Tom

View 1 Replies View Related

Error When Installed Sql Server 2005 On Vista Home Premium (WMI Error)

Oct 8, 2007

Hi. I've been trying to install Sql Server 2005 express on Vista Home Premium. After the initial files install, I get an error message that says the WMI configuration is not correct. (I'm not at home, so I can't post the exact error code at the moment). Does anyone have any ideas on how I can fix this? Thanks in advance.

View 3 Replies View Related

Error - Attempted To Read Or Write Protected Memory

Aug 22, 2007

Hi,

I am back with one more problem..

I have created few reports using SSRS 2005. I am using Oracle database in Data Source to fetch my data. It is working fine and showing me report correctly. But after running the report 8 to 10 times, it starts giving me Memory error. To get rid of that, I need to recycle (stop-start) ReportingService from IIS.

I am exactly getting following error...

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

I am not getting the actual problem, why is it giving memory error only after running few times? Please let me know if anyone facing same problem or knowing the solution for the problem.

Thanks,
HMaheta

View 3 Replies View Related

Flat File Processing - Cannot Get Error Output To Write

Apr 20, 2007

I cannot seem to get my flat file to write columns in error when inserting into a SQL table. I have tried a few examples from MS and did not get anything written to my flat file output. I have set the Source Error Output on this flat file and it uses a script task to created the error description and then write it to a Flat File Destination.



I am new to SSIS and have not had any formal training on it. However, I am very familiar with VS.Net/c# and SQL 2000 DTS - I need to get this working ASAP as there are 45 total flat files that need to be processed. Once I have this solved for one, the rest will follow suit.



If more details would help, I can provide them.



Kind Regards,

Ron

View 14 Replies View Related

SQL Server 2005 DTS Problem: Error 21776: General Error

Mar 5, 2007

I've recently migrated all databases to SQL Server 2005. I couldn'tfigure out how to create an SSIS package in the time I had, so I juststuck with the DTS packages. They all worked fine during testing, butonce we renamed the server we had problems. The DTS packages stillwork, but whenever I click into the Copy SQL Server Object and try toSelect Objects (on the Copy tab) I get this error:Microsoft SQL-DMOError 21776: General ErrorI click OK and get the error again and again for a total of 12 times(regardless of which database I'm connecting to in the packages, soit's not related to the number of objects in the database). Then theSelect Objects screen appears and it's business as usual.Has anyone else come across this problem and found a solution? I'verenamed the server using sp_dropserver and sp_addserver and select@@servername returns the correct valueJohn Hunter

View 1 Replies View Related

Error SQL Server 2005 Express Error: 70347(0x112cb) WMI

Mar 28, 2007

Que tal. Al iniciar el instalador SQL Server 2005 Express me saca el error "System Configuration Checker cannot be executed due to WMI configuration on te machine..." Si alguien sabe como solucionarlo agradeceria se ayuda. Gracias.

View 1 Replies View Related

Timeout Expired Error - SQL Server 2005 Error After Exactly 1 Hour

Aug 27, 2007

We have several large government web sites that we help look after. We recently migrated one of them from SQL Server 2000 to 2005 and are having a problem with our nightly email job in that if it runs for more than an hour then after exactly 1 hour the email job gets a "Timeout expired" message back from SQL Server.

Our batch jobs do run on a different server and connect remotely to our SQL Server DB. I did change the connections - remote query timeout and increased it 10 fold, but this didn't make any difference. Is there any other parameter that may be causing the Timeout expired error after exactly 1 hour?

Thanks !

View 1 Replies View Related

Cannot Write Logfile Error 1059 : Circular Service Dependency

Feb 14, 2007

I have a problem that looks like it has not been discussed before inthese groups.I have a simple SQLAgent job that runs sp_who (could be anything, butlet's just say sp_who for this example). I have set the jobstep towrite to an output file "T:out.txt". If the job is owned by anadmin, it runs fine and writes the output file. If it is owned by anon-admin user, it gets the following error msg:Warning: cannot write logfile t:out.txt. Error 1059 : Circularservice dependency was specified. The step failed.I know about setting up the SQLAgent CMDExec proxy account, and havedone that. In fact, both SQLAgent and the SQLAgent cmdexec proxy usethe same domain account, which is in the administrator group of thelocal server. So, I know that security is not the issue.When a simple job runs and writes to an output file, what service orservice group could it be trying to start or modify? I looked throughthe list of Services, and could not find any circular dependencies.Is there a utility to detect this? Why would running under onecontext (as an admin) be ok while the other context (non-admin on SQL,but using the same admin domain service account) fails?Thanks in advance for any info you might have.

View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved