Login Error At Microsoft SQl Server 2005

Nov 22, 2006

when i tried to login at SQL server 2005 by my local account i found an error (i login by the administrator account and use windows authentication) ... can any one help me plz??

View 2 Replies

Login Failed For The User'xxxx'(Microsoft SQL Server 2005. Error:18456)

Mar 3, 2008

hi,
i am getting the following error message while i am trying to login to the SQL Server 2005 on my vista laptop. i installed the server with dual authentication modes.

Login failed for the user'xxxx'(Microsoft SQL Server 2005. Error:18456)

if you have solution for my problem please send a reply as early as possible.

thanks,
ravi kishore.ch

View 12 Replies View Related

Link Server Error: Login Failed For User 'Domainuser'. (Microsoft SQL Server, Error: 18456)

Oct 18, 2007

Hi,

I am trying to create a linked server between 2 SQL Server 2005 boxes.
When I create the linked server I specify a login for the connection.
The strange part is that I get the following error when it goes to test the connection:

The test connection to the linked server failed
Login failed for user 'Domainuser'. (Microsoft SQL Server, Error: 18456)

I can use the SQL mangement studio to conenct to the database using this same login.
The login has all the server roles assigned to it also.

Can anyone shed some light as to what may be the problem?

Thanks,

View 5 Replies View Related

Microsoft SQL Server 2005 Cannot Install On Vista, Problem With 'sa' Login

Feb 3, 2008

Hi

I have just installed Vista on my computer and now has problems with installing: Microsoft sql server 2005. In the last part during the installation the following error occurs:

"SQL Server Setup could not connect to database service for server configuration..... Login failed for user 'sa'....,"

What is wrong? Why cant I install? Thank you for your help.

Here are more details from log:

SQL service MSSQL$SQLEXPRESS started successfully waiting for SQL service to accept client connections
Service MSSQL$SQLEXPRESS started at Sun Feb 03 09:01:52 2008
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=28000, level=-1, state=-1, native_error=18456, msg=[Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'.
Error Code: 0x80074818 (18456)
Windows Error Text: Source File Name: libodbc_connection.cpp
Compiler Timestamp: Wed Jun 14 16:28:15 2006
Function Name: OdbcConnection::connect@connect
Source Line Number: 148

---- Context -----------------------------------------------

Connecting to SQL Server
ExecuteSqlCommands
Originial error was 80074818 (18456)
ipt
SqlScriptHlpr

Error Code: 18456
MSI (s) (04!E8) [09:02:52:245]: Product: Microsoft SQL Server 2005 Express Edition -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Sun Feb 03 09:02:52 2008
Service MSSQL$SQLEXPRESS with parameters '-m SqlSetup -Q -qDanish_Norwegian_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Sun Feb 03 09:02:52 2008
Attempt to start service when it is already running
SQL service MSSQL$SQLEXPRESS started successfully waiting for SQL service to accept client connections
Service MSSQL$SQLEXPRESS started at Sun Feb 03 09:02:52 2008
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=28000, level=-1, state=-1, native_error=18456, msg=[Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'.
Error Code: 0x80074818 (18456)
Windows Error Text: Source File Name: libodbc_connection.cpp
Compiler Timestamp: Wed Jun 14 16:28:15 2006
Function Name: OdbcConnection::connect@connect
Source Line Number: 148

View 21 Replies View Related

Login Failed For User 'sa'. (Microsoft SQL Server, Error: 18456)

Aug 25, 2006

I just upgraded SQL Server 2000 to 2005 without any errors. Afterwards, I tried registering with sa and it failed. I registered with another sysadmin login to get into most of my databases, but I need sa to work for my backup software Idera SQLSafe to login to the database.

Does anyone have any experience or recommendations? I know my password is correct.

Mindy

View 4 Replies View Related

Login Failed For User &&<user_name&&>. (Microsoft SQL Server, Error: 18456)

Aug 25, 2007

Please help I keep getting this message when I log on to my data base. Not sure what state 1 relates too

TITLE: Connect to Server
------------------------------
Cannot connect to <server_name>
------------------------------
ADDITIONAL INFORMATION:
Login failed for user <user_name>. (Microsoft SQL Server, Error: 18456)

------------------------------
BUTTONS:
OK
------------------------------
Server Name: <server~name>Error Number: 18456
Severity: 14
State: 1
Line Number: 65536

View 13 Replies View Related

Error String: [Microsoft][ODBC SQL Server Driver][SQL Server]Login Failed For User '(null)'. Reason: Not Associated With A Trus

May 14, 2008

Hi all

This Job ran yester day fine,to day It got failed with this error

any suggestion to troubleshoot problem is appreciated.

DTSRun OnError: DTSStep_DTSTransferObjectsTask_1, Error = -2147203052 (80044814)

Error string: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

Error source: Microsoft SQL-DMO (ODBC SQLState: 28000)

Help file: SQLDMO80.hlp

Help context: 1131

Error Detail Records:

Error: 0 (0); Provider Error: 0 (0)

Error string: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

Error source: Microsoft SQL-DMO (ODBC SQLState: 28000)

Help file: SQLDMO80.hlp

Help context: 1131

DTSRun OnFinish: DTSStep_DTSTransferObjectsTask_1

DTSRun: Package execution complete.

View 3 Replies View Related

Login Failed For User , The User Is Not Associated With A Trusted Sql Server Connection. (microsoft SQL Server,Error:18452)

Aug 21, 2007

Login Failed for user , the user is not associated with a trusted sql server connection. (microsoft SQL Server,Error:18452)

hi ,
i am getting the above error message once in a while maybe two or 3 times a week , and then it goes away in 10 to 15 minutes or 5 minutes ,

our mode is set to mixed and we are able to connect and use both sql and windows , but once in a while , it will give us the above message when we try connecting throught sql server management studio client (using sql 05) using windows login , although it lets us connect using sql login while the windows login is denied, and after a while it lets us connect with both.

occurs randomly on some days , we run our servers on VM ware virtual machines using windows 2003 r2 enterprise 64 bit with sp2 with esx 301 virtual machine.

would appericate any feedback on this thanks

View 5 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

Entreprise Manager Error Message: [Microsoft][ODBC SQL ServerDriver][SQL Server]Login Failed For User '#####'. The User Is Not Associatedwith A Trusted SQL Server Connection.(28000,18452)

Dec 12, 2007

Can anyone give a quick description of the meaning of this message andwhat needs to be done to get a connection.I'm running DBArtisan with SQLServer 2000 client SP4 installed.I also get the same message with MS Enterprise Manager so this iscoming out of the actual ODBC connection attempt.Thanks in advance!

View 1 Replies View Related

Microsoft SQL Server 2005 Setup Error

Jan 7, 2008

"SQL Server is unable to run. Either the owning node or all nodes that currently part of the virtual server are not available. Review any SCC failures and validate that all nodes are online."

Can someone tell me what's the cause of this error?
How can this be corrected?

I am very grateful for all feedback.

View 1 Replies View Related

Microsoft SQL Server 2005 Setup Error Message

Mar 5, 2008

I was in the process of installing Microsof Project 2003 when we suddenly decided to move up to Microsoft Project 2007. We removed SharePoint 3.0 and SQL Server 2K so all that is installed on the box is Windows Server 2003 with all Service Packs. During the install of SQL Server 2005, here is the error message we get.

Microsoft SQL Server 2005 Setup

SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Cannot alter the login ��sa��, because it does not exist or you do not have permission.. Refer to the server error logs and Setup logs for detailed error information.

Any help is appreciated.

Thanks,
Ron

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

Microsoft SQL Server 2005 Reporting Services -- Error 1303

Feb 28, 2006

I am trying to install Microsoft SQL Server 2005 Reporting Services, Receiving the following error

Microsoft SQL Server 2005 Reporting Services -- Error 1303. The installer has insufficient privileges to access this directory: C:Config.Msi. The installation cannot continue. Log on as administrator or contact your system administrator.

I am already logged in as Administrator and should have all the necessary permissions to install software

Please help me.

View 3 Replies View Related

RDA Pull Error Using Microsoft SQL Server Compact Edition 2005

May 20, 2007

Hello dear all.

I am using a Compact Framework 2.0 on a mobile 5.0 with a local Microsoft SQL Compact Edition 2005 database. The backend database is a Microsoft SQL Server 2005 and I am trying to pull a 45000 rows table (the table has 2 varchars(8) forming a primary key and an INTEGER column).

The statement I issue is the following:

rda.Pull(table.TableName, table.TableQuery, Program.RdaOleDbConnectionString, RdaTrackOption.TrackingOnWithIndexes, table.TableName + "Errors");

The application works perfectly when I am pulling smaller tables (up to 15000 rows) but when I try to pull this one I get the following error details:

sqlCeEx
{""}
base {System.SystemException}: {""}
Errors: {System.Data.SqlServerCe.SqlCeErrorCollection}
errors: {System.Data.SqlServerCe.SqlCeErrorCollection}
HResult: -2147024882
Message: ""
NativeError: 0
Source: "Microsoft SQL Server Compact Edition"

Please have in mind that the handheld on which I deploy does not have an extra storage card.

I have done a thorough internet search and I have found no solution to this problem. I truly rely on you to find the solution.

Thanks in advance,

Steliosvcy.

View 5 Replies View Related

How Can I Connect To Microsoft SQL Server 2005 CTP With Microsoft SQL Server 2005 Express Manager?

Aug 9, 2005

I installed Microsoft SQL Server 2005 Express Manager and connect to SQL 2000 normally

View 10 Replies View Related

Error Installing KB 921896 (Microsoft SQL Server 2005 Express Edition)

Mar 22, 2008

I receive the error:

Installation Failure

Error Code: 0x734C

Try to install the update again, or request help from one of the following resources.

For self-help options:

Frequently Asked Questions
Find Solutions
Windows Update Newsgroup
For assisted support options:

Microsoft Online Assisted Support (no-cost for issues related to getting updates)

nothing seems to be available for this error.

any ideas?

View 4 Replies View Related

Product: Microsoft SQL Server 2005 Express Edition -- Error 1937.

Jan 28, 2008

I am trying to get SQL Express 2005 installed, I have tried this on two PC's within the Domain. Both get the same error. I am the Admin, MCSE since 1999, but I DO NOT know much about SQL. Have search Google for two days, renamed DLL's, installed localy, copied off the CD, update .net, windows updates.... The PC will load SQL 2005 (full version) and 2000, but the app doesnt seem to want anything but the Express version... any ideas would help...

btd43@hotmail.com westcoastpc@gmail.com

Product: Microsoft SQL Server 2005 Express Edition -- Error 1937. An error occurred during the installation of assembly 'Microsoft.SqlServer.Rmo,Version="9.0.242.0",Culture="neutral",processorArchitecture="MSIL",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.2047.0"'. The signature or catalog could not be verified or is not valid. HRESULT: 0x80131045. assembly interface: IAssemblyCacheItem, function: Commit, component: {D1B86CEE-1C5E-4960-B99F-7142D1582B1B}

View 1 Replies View Related

Error 1601 Installing Microsoft SQL Server 2005 Setup Support Files

Dec 26, 2007

Hi guys,

I have problems installing SQL server 2005, any help ??
Tks...

This is the log file description...

=== Verbose logging started: 25/12/2007 21:05:41 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: c:Archivos de programaMicrosoft SQL Server90Setup Bootstrapsetup.exe ===
MSI (c) (AC:50) [21:05:41:656]: Resetting cached policy values
MSI (c) (AC:50) [21:05:41:656]: Machine policy value 'Debug' is 0
MSI (c) (AC:50) [21:05:41:656]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (c) (AC:50) [21:05:41:656]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (AC:50) [21:05:41:656]: Grabbed execution mutex.
MSI (c) (AC:50) [21:05:41:671]: No se puede conectar al servidor. Error: 0x80040154

MSI (c) (AC:50) [21:05:41:671]: Failed to connect to server.
MSI (c) (AC:50) [21:05:41:671]: MainEngineThread is returning 1601
=== Verbose logging stopped: 25/12/2007 21:05:41 ===

View 11 Replies View Related

Error 1603 Installing Microsoft Sql Server 2005 Setup Support Files

Feb 13, 2008

I'm attempting to install the standard version of SQL server 2005 on XP SP2. I'm getting the following:

Errors occurred during the installation:
Error 1603 installing Microsoft SQL Server 2005 setup support files.

View 11 Replies View Related

Microsoft.AnalysisServices.Viewers.DLL Microsoft SQL Server 2005 Datamining Viewer Controls

Jun 21, 2007

Hi

I am trying to use Association Viewer Control in

Microsoft.AnalysisServices.Viewers.DLL dll in VS 2005 but sometimes it gives an error.

"Code generatio for property 'ConnecitonManager'" failed. Error was:'Property accesor 'ConnectionManager' on object 'AssosiactionViewer1' threw the following exception:'Object referance not set to instance of an object"

Is there anyone here who use
"Microsoft SQL Server 2005 Datamining Viewer Controls" in SQLServer2005 FeaturePack ?
http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&DisplayLang=en

i am using VS2005 Version 8.0.50727.762 (SP.050727-7600)
and SQL Server 2005 SP2

thanks from now.

Cem Üney

View 9 Replies View Related

Microsoft SQL Server 2005 Express Edition Service Pack 2 Error Code: 0x2B22

May 19, 2007

Hi i tried to install the Microsoft SQL Server 2005 Express Edition Service Pack 2 but was unable to do so. I got an error message saying: Error Code: 0x2B22

I went through what the message said, but i was unable to solve the problem. Below is the summary of the problem. Please help me solve it.

Time: 05/19/2007 12:32:24.781
KB Number: KB921896
Machine: DET-NB0631262
OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
/quiet
/allinstances
Cluster Installation: No

**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed

**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Express Database Services (SQLEXPRESS) ENU RTM 2005.090.1399.00 x86 EXPRESS
Express Database Services (SQLExpress) ENU SP2 x86 EXPRESS

**********************************************************************************
Products Disqualified & Reason
Product Reason
Express Database Services (SQLEXPRESS) Unable to start service

**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID

**********************************************************************************
Product Installation Status
Product : Express Database Services (SQLEXPRESS)
Product Version (Previous): 1399
Product Version (Final) :
Status : Not Applied
Log File :
SQL Express Features : SQL_Data_Files,SQL_Engine,SQL_Replication,SQL_SharedTools
Error Number : 11042
Error Description : Unable to start service
----------------------------------------------------------------------------------
Product : Express Database Services (SQLExpress)
Product Version (Previous):
Product Version (Final) :
Status : Not Applied
Log File :
SQL Express Features : Client_Components,Connectivity,SDK
Error Number : 0
Error Description :
----------------------------------------------------------------------------------

**********************************************************************************
Summary
Unable to start service
Exit Code Returned: 11042

View 3 Replies View Related

SQL Server 2005 Standard Login Error

Jan 13, 2007

When I was using

winXP Pro I installed a copy of SQL Server Standard and had it working correctly with Windows authenication logon. I subsequently upgraded to Windows Vista business edition. I also upgraded to SQL Server sp2. Now I get the dreaded "SQL Server, Error: 18456" when trying to connect to the instance of SQL server on my machine. On solution seems to be to login to the original instance and use a stored procedure to update subsequent instances of SQL server.

My subsequent instance is my original instance with the new OS. I do not have a clue how to edit registry entries or any othe methods of overcoming this problem. Anyone have a solution that I could use? Help would be very much appreciated.

View 1 Replies View Related

Error: Login Failed For User ... Microsoft Sql Native Client . In Remote Connection On Integration Service

Apr 10, 2007

Hi

i connect to remote Integration Service. i configure server for remote connection( on component services and DCOM config , ... ) .and now i can connect to Integration Service remotely and correctly.

but when i expand Stored Package and then click to expand MSDB this error will hapen:

login failed for user ... .(microsoft sql native client )

please help me

thanks in advance

View 1 Replies View Related

Difference Between Microsoft Sql Server 2008 And Microsoft Sql Server 2005

Mar 27, 2008

Pls tell me about the adjact difference between sql server 2005 and sql server 2008.
Why to upgrade for Sql Server 2008

View 1 Replies View Related

[Microsoft][ODBC SQL Server Driver][SQL Server]Login Failed For User 'ErrorLog'.

Feb 22, 2005

Hi, all

recently, I use the following script(somebody else) to create a database on a remote server: the script is as follow:
/*************************/
CREATE DATABASE [ErrorLog]
GO

Use ErrorLog

CREATE TABLE [dbo].[Errors] (
[ID] [int] IDENTITY (1, 1) NOT NULL ,
[SessionID] [char] (12) NULL ,
[RequestMethod] [char] (5) NULL ,
[ServerPort] [char] (5) NULL ,
[HTTPS] [char] (3) NULL ,
[LocalAddr] [char] (15) NULL ,
[HostAddress] [char] (15) NULL ,
[UserAgent] [varchar] (255) NULL ,
[URL] [varchar] (400) NULL ,
[CustomerRefID] [varchar] (20) NULL ,
[FormData] [varchar] (2000),
[AllHTTP] [varchar] (2000),
[ErrASPCode] [char] (10) NULL ,
[ErrNumber] [char] (11) NULL ,
[ErrSource] [varchar] (255) NULL ,
[ErrCategory] [varchar] (50) NULL ,
[ErrFile] [varchar] (255) NULL ,
[ErrLine] [int] NULL ,
[ErrColumn] [int] NULL,
[ErrDescription] [varchar] (1000) NULL ,
[ErrAspDescription] [varchar] (1000) NULL ,
[InsertDate] [datetime] NOT NULL
) ON [PRIMARY]

--Create the user "ErrorLog"

if not exists (select * from master.dbo.syslogins where loginname = N'ErrorLog')
BEGIN
declare @logindb nvarchar(132), @loginlang nvarchar(132) select @logindb = N'Navigator', @loginlang = N'us_english'
if @logindb is null or not exists (select * from master.dbo.sysdatabases where name = @logindb)
select @logindb = N'master'
if @loginlang is null or (not exists (select * from master.dbo.syslanguages where name = @loginlang) and @loginlang <> N'us_english')
select @loginlang = @@language
exec sp_addlogin N'ErrorLog', 'secret', @logindb, @loginlang
END
GO

if not exists (select * from dbo.sysusers where name = N'ErrorLog' and uid < 16382)
EXEC sp_grantdbaccess N'ErrorLog', N'ErrorLog'
GO

Grant select, insert On Errors to ErrorLog
/***************************/
in my *.asp program, I used the following string to connect to the database on the remote server.
/********
con.open "dsn=ErrorLog;uid=ErrorLog;pwd=secret;"
********/
the following message comes up:
/********/
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'ErrorLog'.
/*********/
what is the problem here?
when I set up dsn ErrorLOG, I used "abc" userID and password "XXX" which is our server database administrator assigned to me. I tested connection in odbc, it is OK
I just don't get, ther user ErrorLog already had login id and granted access to database errorlog. any clue, please help!
Betty

View 6 Replies View Related

VB.NET Login (SQL Server 2005) Error: Communication With The Underlying Transaction Manager Has Failed

Mar 4, 2008

Hi all,I am trying to setup a VB.Net development environment on my desktop for one of the application which was already in the production for couple of years (some unknown contractor(s) developed and maintained it so far). The application works fine on the web.Visual Studio 2005, .Net 2.0, SQL 2000, SQL Server 2005 were installed on my desktop. When I try to build the entire application/solution in the debug mode (i.e., with http://localhost/), build succeeds and I could get to the login.aspx. When I try to login, I am getting an error in the Visual Studio at the following code;connection = New SqlConnection(connectionString)
connection.Open()
saying "Communication with the underlying transaction manager has failed", "System.Transactions.TransactionManagerCommunicationException was unhandled by user code". And the web browser displays the following error "Error HRESULT E_FAIL has been returned from a call to a COM component". When I try to connect the SQL Server 2005 with the same ConnectionString attributes by going to Tools>Connect to Database, it works fine. But, through application connection.Open() giving above errors. I have set the MSDTC properties (i.e., under Component Services>MyComputer Properties>Security Configuration) as below:-Enabled Network DTC Access, Allow Remote Clients, Allow Remote Administration, Allow Inbound, Allow Outbound, No Authentication required - selected, Enabled XA Transactions...& DTC Logon Account is "NT AUTHORITYNetworkService".Please help.Thanks in advance,Chandra

View 3 Replies View Related

Aspclassic On IIS7 SQL 2005. ODBC SQL Server Driver[SQL Server]Cannot Open Database Requested By The Login. The Login Failed

Apr 16, 2008

Hi all,

Have just tried my sql server 2005 connected asp classic website on II7 for the first time and have gotten some errors.
First off I have unchecked show friendly errors in IE and have enabled ASP to send error messages to the browser.

My error I get is when I execute a basic .asp page:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "mydatabasename" requested by the login. The login failed.
/index.asp, line 10 which is dbConnect.Open cstring

from this peice of code:

sub dbOpen()
set dbConnect = Server.CreateObject("ADODB.Connection")
cstring = "DSN=mysqldsn; Trusted Connection=yes"
dbConnect.Open cstring
end sub

I have gone into ODBC and have setup both a user dsn and file dsn that equals mysqldsn and points to my database (I know you only need to set up one DSN but I'm not sure which)

I also notice under mywebsite home panel there is a connection string option. Do I do anything with that?

Definatley a lot more to it than XP's II6!

Any help or advice would be greatly appreciated.

View 3 Replies View Related

Microsoft.Data.Odbc.OdbcException: ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]

Dec 10, 2003

Hi Everybody,

On localhost this application works fine but when I put on remote server. I am getting following errors. For both localhost and server, I am using same remote sql 2000. I will appreciate any help.

Thanks,

Arif

Server Error in '/' Application.
--------------------------------------------------------------------------------

ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.
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: Microsoft.Data.Odbc.OdbcException: ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.

Source Error:

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

Stack Trace:

[OdbcException: ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.]
Microsoft.Data.Odbc.OdbcConnection.HandleError(IntPtr hHandle, SQL_HANDLE hType, RETCODE retcode) +27
Microsoft.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method) +838
Microsoft.Data.Odbc.OdbcCommand.ExecuteNonQuery() +80
Calgary.venues.Page_Load(Object sender, EventArgs e) in c:inetpubwwwrootCalgarySitevenuesvenues.aspx.vb:32
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +731

View 5 Replies View Related

I Created A Login In SQL SERVER 2005 EXPRESS, But Cant Login...

Nov 24, 2005

create login dave with password='abc', default_database=tempdb

View 6 Replies View Related

How Can I Login To My MS SQL Server 2005 If I Forgot My Login Password

Oct 8, 2007

Hi,

I am using SQL Server 2005 at home.
My problem is I forgot my password to log in to my server.
I only remember user name is 'sa'.
I haven't used it for two to three months. So I forgot password.
Previously, When I used sql server 2000, my login is as windows login. so no problem.
But this time, I set seperate log in and I got this problem.
Any help will be appreciated.
Thanks
George

View 11 Replies View Related

SQL SERVER 2005 Login Failed Message For Sa Login

Feb 26, 2007

Hello everyone,

Since last so many days i am seeing that someone is trying to login to sql server through login name sa.but that login is failed.and this is occuring constantly.

Earlier i had same login failed message for another ip address.i have blocked that ip address through access-list in firewall.but now i am seeing the same message for another ip address.

(1).how can i permenently remove this message from Event log.

(2).What is the impact of this on sql server performance.is sql server performance degraded by this kind of contineous attack?

here i am attaching that report from event viewer log file.

2/26/2007 1:48:18 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:17 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:17 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:17 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:16 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:16 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:16 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:15 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:15 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:15 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:14 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:14 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:14 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:13 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:13 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:12 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:12 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:12 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:11 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:11 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:11 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:10 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:10 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:10 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:09 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:09 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:09 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:08 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:08 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:08 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:07 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:07 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:07 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:06 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:06 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:06 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:05 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:05 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:05 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:04 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:04 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:04 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:03 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:02 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:02 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:02 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:01 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:01 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:01 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:00 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:00 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:00 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:59 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:59 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:59 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:58 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:58 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:57 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:57 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:57 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:56 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:56 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:55 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:55 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:54 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:54 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:54 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:53 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:53 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:53 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:52 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:52 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:52 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:51 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:51 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:50 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:50 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:50 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:49 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:49 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:49 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:48 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:48 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:48 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:48 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:47 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:47 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:47 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:46 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:46 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:45 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:45 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:45 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:44 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:44 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:44 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:43 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:43 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:43 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]

Needs your help to resolve this issue.

Thanks,

Bharat

View 3 Replies View Related

VB.Net 2005 Setup Creation Gets Error Using Microsoft.SqlServer.Dts.Runtime

Feb 3, 2007

I have a very small project written in VB.Net 2005 using the SQL Server 2005 SSiS DTSx package.

I migrated a SLQ 2000 DTS package using the SQL 2005 Legacy tools and saved the package as a local .DTSx package on our file server.

I need to run the package from a clients PC.

I added the reference Microsoft.SqlServer.ManagedDTS so I could then use the Microsoft.SqlServer.Dts.Runtime so I can execute the commands:

Dim oApp As New Application
Dim oPkg As New Package
oPkg = oApp.LoadPackage(g_DTSx_Directory & "AOC copy Generic1 CSV to AOC_verify_file_1.dtsx", Nothing)
Dim oResults As DTSExecResult
oResults = oPkg.Execute

Ok. That works fine and is basically the entire app. It executes without a hitch in debug and as a compiled exe on my PC, but I have all the tools. So now I try and create a setup project for this and I use the setup wizard.

During the creation of the setup project I get a message that states:
The following files may have dependencies that cannot be determined automatically. Please confirm that all dependencies have been added to the project.
C:windowssystem32msxml6.dll

OK. The dll is part of the reference I mentioned above and I have no idea what other dependencies it may have.

How do I find this out?

Has anyone else created a project like this and experenced the same?

I am on a clean build running WinXP Pro with SP2 - VS2005 with SP1 and the SQL Server 2005 tools.

View 4 Replies View Related