Hi...can someone explain to me what fiber mode is, and how can I tell if my
instance of SQL Server is running in fiber mode
Thanks.An instance of the database engine is in fiber mode if the option
lightweight pooling is set to 1. You can see the setting of that option
using sp_configure or Enterprise Manager. It is an advanced option, so you
have to have the sp_configure show advanced options setting turned on.
There are a set of topics in the SQL Server 2000 Books Online that discuss
how the database engine uses Windows threads and fibers under this node:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa_0w6d.asp?frame=true
Fiber mode is specifically discussed in this topic:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa_9m9f.asp?frame=true
Most instances of the database engine are not run in fiber mode, most of the
time the instance runs fine without using fibers.
--
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts
Tuesday, March 27, 2012
Friday, March 9, 2012
Fastest connection method?
I am trying to find some info on the fastest connection transport for an app that is running on the same box as a SQL 2005 instance. The app does a large number of updates (high volume of data).. win32 using native ODBC. I am trying to find info on which connection mechanism is best... socket, pipes, etc. I read somewhere that there is a file mapped method available but i cannot find info on that either. Also, is there any performance difference between the old SQL OCBD drive and the new SQL Native Client OCBD drive?
Thanks.
For best performance, I recommend you use the SQL Native Client ODBC driver with SQL 2005. I would also recommend you use TCP/IP as the transport.
Regards,
Uwa.
|||Thanks for the info... does anyone know of any benchmarks for these methods? I have seen it written that shared memory should be used for best performance when on the same box as the SQL server... but have never seen numbers to prove or disprove this.Sunday, February 26, 2012
Fast copy of data from one table to another
I have to copy the contents of a table (6million rows) into another table on
the same instance. The target table has an identity column(PK). What is the
fastest way to do this? The instance has to remain up for the web site, and
yes, the target table is read by the web site. I was thinking a bcp out/in.
Thanks,
MichaelUse SET IDENTITY_INSERT ON/OFF to keep the identity column. There's
also a switch in the bcp utility to keep identities (-E)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_set-set_7zas.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_bcp_61et.asp
Snake wrote:
> I have to copy the contents of a table (6million rows) into another table on
> the same instance. The target table has an identity column(PK). What is the
> fastest way to do this? The instance has to remain up for the web site, and
> yes, the target table is read by the web site. I was thinking a bcp out/in.
> Thanks,
> Michael
the same instance. The target table has an identity column(PK). What is the
fastest way to do this? The instance has to remain up for the web site, and
yes, the target table is read by the web site. I was thinking a bcp out/in.
Thanks,
MichaelUse SET IDENTITY_INSERT ON/OFF to keep the identity column. There's
also a switch in the bcp utility to keep identities (-E)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_set-set_7zas.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_bcp_61et.asp
Snake wrote:
> I have to copy the contents of a table (6million rows) into another table on
> the same instance. The target table has an identity column(PK). What is the
> fastest way to do this? The instance has to remain up for the web site, and
> yes, the target table is read by the web site. I was thinking a bcp out/in.
> Thanks,
> Michael
Fast copy of data from one table to another
I have to copy the contents of a table (6million rows) into another table on
the same instance. The target table has an identity column(PK). What is the
fastest way to do this? The instance has to remain up for the web site, and
yes, the target table is read by the web site. I was thinking a bcp out/in.
Thanks,
Michael
Use SET IDENTITY_INSERT ON/OFF to keep the identity column. There's
also a switch in the bcp utility to keep identities (-E)
http://msdn.microsoft.com/library/de...t-set_7zas.asp
http://msdn.microsoft.com/library/de...p_bcp_61et.asp
Snake wrote:
> I have to copy the contents of a table (6million rows) into another table on
> the same instance. The target table has an identity column(PK). What is the
> fastest way to do this? The instance has to remain up for the web site, and
> yes, the target table is read by the web site. I was thinking a bcp out/in.
> Thanks,
> Michael
the same instance. The target table has an identity column(PK). What is the
fastest way to do this? The instance has to remain up for the web site, and
yes, the target table is read by the web site. I was thinking a bcp out/in.
Thanks,
Michael
Use SET IDENTITY_INSERT ON/OFF to keep the identity column. There's
also a switch in the bcp utility to keep identities (-E)
http://msdn.microsoft.com/library/de...t-set_7zas.asp
http://msdn.microsoft.com/library/de...p_bcp_61et.asp
Snake wrote:
> I have to copy the contents of a table (6million rows) into another table on
> the same instance. The target table has an identity column(PK). What is the
> fastest way to do this? The instance has to remain up for the web site, and
> yes, the target table is read by the web site. I was thinking a bcp out/in.
> Thanks,
> Michael
Fast copy of data from one table to another
I have to copy the contents of a table (6million rows) into another table on
the same instance. The target table has an identity column(PK). What is th
e
fastest way to do this? The instance has to remain up for the web site, and
yes, the target table is read by the web site. I was thinking a bcp out/in.
Thanks,
MichaelUse SET IDENTITY_INSERT ON/OFF to keep the identity column. There's
also a switch in the bcp utility to keep identities (-E)
http://msdn.microsoft.com/library/d... />
t_7zas.asp
http://msdn.microsoft.com/library/d...
1et.asp
Snake wrote:
> I have to copy the contents of a table (6million rows) into another table
on
> the same instance. The target table has an identity column(PK). What is
the
> fastest way to do this? The instance has to remain up for the web site, a
nd
> yes, the target table is read by the web site. I was thinking a bcp out/in
.
> Thanks,
> Michael
the same instance. The target table has an identity column(PK). What is th
e
fastest way to do this? The instance has to remain up for the web site, and
yes, the target table is read by the web site. I was thinking a bcp out/in.
Thanks,
MichaelUse SET IDENTITY_INSERT ON/OFF to keep the identity column. There's
also a switch in the bcp utility to keep identities (-E)
http://msdn.microsoft.com/library/d... />
t_7zas.asp
http://msdn.microsoft.com/library/d...
1et.asp
Snake wrote:
> I have to copy the contents of a table (6million rows) into another table
on
> the same instance. The target table has an identity column(PK). What is
the
> fastest way to do this? The instance has to remain up for the web site, a
nd
> yes, the target table is read by the web site. I was thinking a bcp out/in
.
> Thanks,
> Michael
Failures in installing SP1 on top SQL Server 2005
I am trying to apply SP1 on top of SQL Server 2005 and it keeps failing. I have a default instance and a named instance on the machine. The named instance disabled when I tried installing the pack. Then I enabled the named instance and tried the pack. This time the default instance failed as usual but the named instance was successful. The log is as follows ( when I attempted when the named instance 'TEST' was disabled ):
ANy suggestions / insights ?
Thanks.
-chiraj
12/13/2006 12:23:18.661 ================================================================================
12/13/2006 12:23:18.661 Hotfix package launched
12/13/2006 12:23:20.021 Product discovery successfully completed during the install process for MSSQLSERVER
12/13/2006 12:23:20.021 SP Level check successfully completed during the install process for MSSQLSERVER
12/13/2006 12:23:20.021 Product language check successfully completed during the install process for MSSQLSERVER
12/13/2006 12:23:20.021 Product version check successfully completed during the install process for MSSQLSERVER
12/13/2006 12:23:20.021 Product discovery successfully completed during the install process for TEST
12/13/2006 12:23:20.021 SP Level check successfully completed during the install process for TEST
12/13/2006 12:23:20.021 Product language check successfully completed during the install process for TEST
12/13/2006 12:23:20.021 Product version check successfully completed during the install process for TEST
12/13/2006 12:23:20.021 Command-line instance name check completed during the install process
12/13/2006 12:23:20.021 Baseline build check completed during the install process
12/13/2006 12:26:04.479 Attempting to install instance: MSSQLSERVER
12/13/2006 12:26:04.479 Attempting to install target: KCMSQL02
12/13/2006 12:26:04.479 Attempting to check for locked files: sqlrun_sql.msp
12/13/2006 12:26:04.526 Attempting to check for locked files: \\KCMSQL02\e$\491bf0f9e8c5744ccb0c\HotFixSQL\Files\sqlrun_sql.msp
12/13/2006 12:26:04.526 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.out
12/13/2006 12:26:16.416 MSP returned 1602: The user cancels installation.
12/13/2006 12:26:16.416 Successfully checked file: \\KCMSQL02\e$\491bf0f9e8c5744ccb0c\HotFixSQL\Files\sqlrun_sql.msp
12/13/2006 12:26:16.431 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
12/13/2006 12:26:16.431 Failed to read registry key: PendingFileRenameOperations
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nlhtml.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msir5jp.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msftesql.exe
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msftepxy.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msftefd.exe
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msfte.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\LangWrbk.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\korwbrkr.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\infosoft.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\FTERef\FTERef.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\CHTBRKR.DLL
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ChsBrkr.dll
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\COM\Resources\1033\REPLRES.rll
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\COM\replrec.dll
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\COM\rplisapi.dll
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.Replication\9.0.242.0__89845dcd8080cc91\Repl.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.DataStorage\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.DataStorage.dll
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Common Files\Microsoft Shared\Database Replication\Resources\1033\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\rplhtfin.sql
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\
C:\Program Files\Microsoft SQL Server\90\COM\qrdrsvc.exe
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\COM\snapshot.exe
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\COM\replmerg.exe
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\tablediff.exe
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\COM\DISTRIB.exe
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\DatabaseMail90.exe
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\3082\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\2052\sqlevn70.rll
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1042\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1041\sqlevn70.rll
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1040\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1036\sqlevn70.rll
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1031\sqlevn70.rll
12/13/2006 12:26:16.431 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1028\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\XPStar90.RLL
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlaccess.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlaccess.dll
12/13/2006 12:26:16.431 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlaccess.dll
12/13/2006 12:26:16.447 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\6.6.3.5
C:\Program Files\Microsoft SQL Server\90\Shared\msxmlsql.dll
12/13/2006 12:26:16.447 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\2.0.3609.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlrw.dll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlsvc90.dll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlsvc90.dll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlsvc90.dll
12/13/2006 12:26:16.447 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLBOOT.dll
12/13/2006 12:26:16.447 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xplog70.dll
12/13/2006 12:26:16.447 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\batchp~1.dll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\SQLAgentMail90.rll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\SQLAgentMail90.rll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\SQLAgentMail90.rll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\SQLAGENT90.RLL
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\SQLAGENT90.RLL
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\SQLAGENT90.RLL
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLAgentMail90.dll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLAgentMail90.dll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLAgentMail90.dll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLAGENT90.EXE
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLAGENT90.EXE
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLAGENT90.EXE
12/13/2006 12:26:16.447 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\Resources\1033\9.0.2047.0
C:\Program Files\Microsoft SQL Server\90\Shared\msmdrdir.dll
12/13/2006 12:26:16.447 Failed to read version information for the following file: C:\Program Files\Common Files\System\ole db\2.0.3609.0
C:\Program Files\Common Files\System\ole db\xmlrw.dll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\msmdlocal.dll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\msmdlocal.dll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\msmdlocal.dll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\msasxpress.dll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\msasxpress.dll
12/13/2006 12:26:16.447 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\msasxpress.dll
12/13/2006 12:26:16.447 Failed to read version information for the following file: C:\Program Files\Microsoft.NET\ADOMD.NET\90\en\Microsoft.AnalysisServices.AdomdClient.xml
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft.NET\ADOMD.NET\90\Microsoft.AnalysisServices.AdomdClient.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.AnalysisServices.AdomdClient\9.0.242.0__89845dcd8080cc91\Microsoft.AnalysisServices.AdomdClient.dll
12/13/2006 12:26:16.463 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033\
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033\sqlcm.xml
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033\SqlManager.rll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033\SqlManager.rll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033\SqlManager.rll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\binn\SqlManager.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\binn\SqlManager.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\binn\SqlManager.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\batchparser90.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\batchparser90.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\batchparser90.dll
12/13/2006 12:26:16.463 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLSVC90.DLL
12/13/2006 12:26:16.463 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\2.0.3609.0
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\SQLdiag.exe
12/13/2006 12:26:16.463 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\Shared\sqlsvc~1.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlsecacctchg.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlsecacctchg.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlsecacctchg.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlftacct.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlftacct.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlftacct.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\isacctchange.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\isacctchange.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\isacctchange.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\svrenumapi.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\svrenumapi.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\svrenumapi.dll
12/13/2006 12:26:16.463 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\Shared\sqlsqm.exe
12/13/2006 12:26:16.463 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\9.0.2047.0
C:\Program Files\Microsoft SQL Server\90\Shared\dbghelp.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\SqlDumper.exe
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\SqlDumper.exe
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\SqlDumper.exe
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.Rmo\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.Rmo.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.AnalysisServices\9.0.242.0__89845dcd8080cc91\Microsoft.AnalysisServices.DLL
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.DataWarehouse.Interfaces\9.0.242.0__89845dcd8080cc91\Microsoft.DataWarehouse.Interfaces.DLL
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.RegSvrEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.RegSvrEnum.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.BatchParser\9.0.242.0__89845dcd8080cc91\microsoft.sqlserver.batchparser.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.BatchParser\9.0.242.0__89845dcd8080cc91\microsoft.sqlserver.batchparser.dll
12/13/2006 12:26:16.463 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.BatchParser\9.0.242.0__89845dcd8080cc91\microsoft.sqlserver.batchparser.dll
12/13/2006 12:26:16.478 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ServiceBrokerEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.ServiceBrokerEnum.dll
12/13/2006 12:26:16.478 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.WmiEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.WmiEnum.dll
12/13/2006 12:26:16.478 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.SqlEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.SqlEnum.dll
12/13/2006 12:26:16.478 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.SmoEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.SmoEnum.dll
12/13/2006 12:26:16.478 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.Smo\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.Smo.dll
12/13/2006 12:26:16.478 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\SqlSAC.exe
12/13/2006 12:26:16.478 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
12/13/2006 12:26:16.494 Attempting to install file: sqlrun_sql.msp
12/13/2006 12:26:16.510 Attempting to install file: \\KCMSQL02\e$\491bf0f9e8c5744ccb0c\HotFixSQL\Files\sqlrun_sql.msp
12/13/2006 12:26:16.510 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.log
12/13/2006 12:26:16.510 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
12/13/2006 12:26:16.510 Failed to read registry key: Debug
12/13/2006 12:26:57.834 MSP returned 1603: A fatal error occurred during installation.
12/13/2006 12:26:57.834 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
12/13/2006 12:26:57.834 Failed to read registry key: Debug
12/13/2006 12:26:57.834 Unable to install MSP file: \\KCMSQL02\e$\491bf0f9e8c5744ccb0c\HotFixSQL\Files\sqlrun_sql.msp
12/13/2006 12:26:57.834 The following exception occurred: Unable to install Windows Installer MSP file Date: 12/13/2006 12:26:57.834 File: \depot\sqlvault\setupmain\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
12/13/2006 12:26:57.881
12/13/2006 12:26:57.881 Product Status Summary:
12/13/2006 12:26:57.881 Product: SQL Server Native Client
12/13/2006 12:26:57.881 SQL Server Native Client (RTM ) - Success
12/13/2006 12:26:57.881
12/13/2006 12:26:57.881 Product: Setup Support Files
12/13/2006 12:26:57.881 Setup Support Files (RTM ) - Success
12/13/2006 12:26:57.881
12/13/2006 12:26:57.881 Product: Database Services
12/13/2006 12:26:57.881 Database Services (RTM 1399 ENU) - Failure
12/13/2006 12:26:57.881 Details: Unable to install Windows Installer MSP file
12/13/2006 12:26:57.881 Analysis Services (SP1 2047 ENU) - Not Applied
12/13/2006 12:26:57.881
12/13/2006 12:26:57.881 Product: Database Services
12/13/2006 12:26:57.881 Database Services (RTM 1399 ENU) - Not Selected
12/13/2006 12:26:57.881
12/13/2006 12:26:57.881 Product: Notification Services
12/13/2006 12:26:57.881 Notification Services (SP1 2047 ENU) - Not Applied
12/13/2006 12:26:57.881
12/13/2006 12:26:57.881 Product: Integration Services
12/13/2006 12:26:57.881 Integration Services (SP1 2047 ENU) - Not Applied
12/13/2006 12:26:57.881
12/13/2006 12:26:57.881 Product: Client Components
12/13/2006 12:26:57.881 Client Components (SP1 2047 ENU) - Not Applied
12/13/2006 12:26:57.881
12/13/2006 12:26:57.881 Product: MSXML 6.0 Parser
12/13/2006 12:26:57.881 MSXML 6.0 Parser (RTM ) - Not Applied
12/13/2006 12:26:57.881
12/13/2006 12:26:57.881 Product: SQLXML4
12/13/2006 12:26:57.881 SQLXML4 (RTM ) - Not Applied
12/13/2006 12:26:57.881
12/13/2006 12:26:57.881 Product: Backward Compatibility
12/13/2006 12:26:57.881 Backward Compatibility (RTM ) - Not Applied
12/13/2006 12:26:57.881
12/13/2006 12:26:57.881 Product: Microsoft SQL Server VSS Writer
12/13/2006 12:26:57.881 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
12/13/2006 12:26:57.881
12/13/2006 12:30:17.995 Hotfix package closed
this is a bug which is filed in the connect portal. In the meantime, shutdown your SQL Server processes in order to avoid the lock on the appropiate files and let the installer run through.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de|||
Hi Jens,
Thanks for the response. When I first attempted installing the pack, my named instance was disabled because I was not using it and I shutdown the default instance's sqlserver process and its agent. Some other process in the sqlserver group may have been running which explains the locked files. On subsequent attempts, I made sure all the processes in the "SQL Server Configuration Manager" were stopped and then attempted installing the patch. I suspect the first failure left things in a dirty state and subsequent attempts are failing because of that.
I'd appreciate any workarounds for this.
Thanks,
-chiraj.
Failure...SQL Server does not allow remote connections
Hi all,
We've got a product which is three tier,
using a .NET Client -> .NET Server which in turn connects to a Sql
Server 2005 Instance.
On top of this we also have a Windows Service which runs nightly
processes also written in .NET
and connects directly to the SQL Server instance.
It's all working pretty well, except that in some installations the
Nightly Processes service
is failing to connect to the SQL Server instance.
We're getting the following message:
__________________________________________________ _______________
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections
........
__________________________________________________ _______________
This has us confused. The nightly processes is using an indentical
connection string
to the .NET Server. The .NET application is connecting fine
everytime.
The service and the application server are sitting on the same machine
as the SQL Server instance,
so no remote connection should be needed.
The problem seems to happen only on Windows Server Machines/SQL Server
installations vs WinXP/SQLExpress, however that could be unrelated.
Any thoughts appreciated.
Cheers
Chris.
Do ou use TCP port ?
If yes do you use autopmatic selection of port number ?
If yes it is preferable to fixed a tcp port to connect to SQL server, using
autoamtic selction of port might affect such connection trouble
Hope it helps
serge
"theinvisibleGhost" wrote:
> Hi all,
> We've got a product which is three tier,
> using a .NET Client -> .NET Server which in turn connects to a Sql
> Server 2005 Instance.
> On top of this we also have a Windows Service which runs nightly
> processes also written in .NET
> and connects directly to the SQL Server instance.
> It's all working pretty well, except that in some installations the
> Nightly Processes service
> is failing to connect to the SQL Server instance.
> We're getting the following message:
> __________________________________________________ _______________
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections
> ........
> __________________________________________________ _______________
> This has us confused. The nightly processes is using an indentical
> connection string
> to the .NET Server. The .NET application is connecting fine
> everytime.
> The service and the application server are sitting on the same machine
> as the SQL Server instance,
> so no remote connection should be needed.
> The problem seems to happen only on Windows Server Machines/SQL Server
> installations vs WinXP/SQLExpress, however that could be unrelated.
> Any thoughts appreciated.
> Cheers
> Chris.
>
|||Not as far as I'm aware. It's certainly not referenced in the
connection string?
|||See my whitepaper on connecting... it might turn up some issues that you had
not considered.
http://betav.com/blog/billva/2006/06/getting_and_staying_connected_1.html
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"theinvisibleGhost" <theinvisibleGhost@.yahoo.com> wrote in message
news:1178703769.427072.296430@.q75g2000hsh.googlegr oups.com...
> Hi all,
> We've got a product which is three tier,
> using a .NET Client -> .NET Server which in turn connects to a Sql
> Server 2005 Instance.
> On top of this we also have a Windows Service which runs nightly
> processes also written in .NET
> and connects directly to the SQL Server instance.
> It's all working pretty well, except that in some installations the
> Nightly Processes service
> is failing to connect to the SQL Server instance.
> We're getting the following message:
> __________________________________________________ _______________
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections
> .......
> __________________________________________________ _______________
> This has us confused. The nightly processes is using an indentical
> connection string
> to the .NET Server. The .NET application is connecting fine
> everytime.
> The service and the application server are sitting on the same machine
> as the SQL Server instance,
> so no remote connection should be needed.
> The problem seems to happen only on Windows Server Machines/SQL Server
> installations vs WinXP/SQLExpress, however that could be unrelated.
> Any thoughts appreciated.
> Cheers
> Chris.
>
|||Cheers Bill,
I've taken a good look through your page.
I think the most likely scenario might be that the service
is running the local-system account and this may not
have access for some reason, the SQL services are running
under a different windows logon.
The SQL Server instance is running in mixed mode security.
I know where to find the permissions, how can I find out if "Local
System"
has access?
Cheers
Chris
|||OK i've checked and LocalSystem already has Connect SQL access,
so I don't think it's that...
Hmmmm...
We've got a product which is three tier,
using a .NET Client -> .NET Server which in turn connects to a Sql
Server 2005 Instance.
On top of this we also have a Windows Service which runs nightly
processes also written in .NET
and connects directly to the SQL Server instance.
It's all working pretty well, except that in some installations the
Nightly Processes service
is failing to connect to the SQL Server instance.
We're getting the following message:
__________________________________________________ _______________
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections
........
__________________________________________________ _______________
This has us confused. The nightly processes is using an indentical
connection string
to the .NET Server. The .NET application is connecting fine
everytime.
The service and the application server are sitting on the same machine
as the SQL Server instance,
so no remote connection should be needed.
The problem seems to happen only on Windows Server Machines/SQL Server
installations vs WinXP/SQLExpress, however that could be unrelated.
Any thoughts appreciated.
Cheers
Chris.
Do ou use TCP port ?
If yes do you use autopmatic selection of port number ?
If yes it is preferable to fixed a tcp port to connect to SQL server, using
autoamtic selction of port might affect such connection trouble
Hope it helps
serge
"theinvisibleGhost" wrote:
> Hi all,
> We've got a product which is three tier,
> using a .NET Client -> .NET Server which in turn connects to a Sql
> Server 2005 Instance.
> On top of this we also have a Windows Service which runs nightly
> processes also written in .NET
> and connects directly to the SQL Server instance.
> It's all working pretty well, except that in some installations the
> Nightly Processes service
> is failing to connect to the SQL Server instance.
> We're getting the following message:
> __________________________________________________ _______________
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections
> ........
> __________________________________________________ _______________
> This has us confused. The nightly processes is using an indentical
> connection string
> to the .NET Server. The .NET application is connecting fine
> everytime.
> The service and the application server are sitting on the same machine
> as the SQL Server instance,
> so no remote connection should be needed.
> The problem seems to happen only on Windows Server Machines/SQL Server
> installations vs WinXP/SQLExpress, however that could be unrelated.
> Any thoughts appreciated.
> Cheers
> Chris.
>
|||Not as far as I'm aware. It's certainly not referenced in the
connection string?
|||See my whitepaper on connecting... it might turn up some issues that you had
not considered.
http://betav.com/blog/billva/2006/06/getting_and_staying_connected_1.html
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"theinvisibleGhost" <theinvisibleGhost@.yahoo.com> wrote in message
news:1178703769.427072.296430@.q75g2000hsh.googlegr oups.com...
> Hi all,
> We've got a product which is three tier,
> using a .NET Client -> .NET Server which in turn connects to a Sql
> Server 2005 Instance.
> On top of this we also have a Windows Service which runs nightly
> processes also written in .NET
> and connects directly to the SQL Server instance.
> It's all working pretty well, except that in some installations the
> Nightly Processes service
> is failing to connect to the SQL Server instance.
> We're getting the following message:
> __________________________________________________ _______________
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections
> .......
> __________________________________________________ _______________
> This has us confused. The nightly processes is using an indentical
> connection string
> to the .NET Server. The .NET application is connecting fine
> everytime.
> The service and the application server are sitting on the same machine
> as the SQL Server instance,
> so no remote connection should be needed.
> The problem seems to happen only on Windows Server Machines/SQL Server
> installations vs WinXP/SQLExpress, however that could be unrelated.
> Any thoughts appreciated.
> Cheers
> Chris.
>
|||Cheers Bill,
I've taken a good look through your page.
I think the most likely scenario might be that the service
is running the local-system account and this may not
have access for some reason, the SQL services are running
under a different windows logon.
The SQL Server instance is running in mixed mode security.
I know where to find the permissions, how can I find out if "Local
System"
has access?
Cheers
Chris
|||OK i've checked and LocalSystem already has Connect SQL access,
so I don't think it's that...
Hmmmm...
Failure...SQL Server does not allow remote connections
Hi all,
We've got a product which is three tier,
using a .NET Client -> .NET Server which in turn connects to a Sql
Server 2005 Instance.
On top of this we also have a Windows Service which runs nightly
processes also written in .NET
and connects directly to the SQL Server instance.
It's all working pretty well, except that in some installations the
Nightly Processes service
is failing to connect to the SQL Server instance.
We're getting the following message:
________________________________________
_________________________
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections
.......
________________________________________
_________________________
This has us confused. The nightly processes is using an indentical
connection string
to the .NET Server. The .NET application is connecting fine
everytime.
The service and the application server are sitting on the same machine
as the SQL Server instance,
so no remote connection should be needed.
The problem seems to happen only on Windows Server Machines/SQL Server
installations vs WinXP/SQLExpress, however that could be unrelated.
Any thoughts appreciated.
Cheers
Chris.Do ou use TCP port ?
If yes do you use autopmatic selection of port number ?
If yes it is preferable to fixed a tcp port to connect to SQL server, using
autoamtic selction of port might affect such connection trouble
Hope it helps
serge
"theinvisibleGhost" wrote:
> Hi all,
> We've got a product which is three tier,
> using a .NET Client -> .NET Server which in turn connects to a Sql
> Server 2005 Instance.
> On top of this we also have a Windows Service which runs nightly
> processes also written in .NET
> and connects directly to the SQL Server instance.
> It's all working pretty well, except that in some installations the
> Nightly Processes service
> is failing to connect to the SQL Server instance.
> We're getting the following message:
> ________________________________________
_________________________
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections
> ........
> ________________________________________
_________________________
> This has us confused. The nightly processes is using an indentical
> connection string
> to the .NET Server. The .NET application is connecting fine
> everytime.
> The service and the application server are sitting on the same machine
> as the SQL Server instance,
> so no remote connection should be needed.
> The problem seems to happen only on Windows Server Machines/SQL Server
> installations vs WinXP/SQLExpress, however that could be unrelated.
> Any thoughts appreciated.
> Cheers
> Chris.
>|||Not as far as I'm aware. It's certainly not referenced in the
connection string?|||See my whitepaper on connecting... it might turn up some issues that you had
not considered.
http://betav.com/blog/billva/2006/0...onnected_1.html
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"theinvisibleGhost" <theinvisibleGhost@.yahoo.com> wrote in message
news:1178703769.427072.296430@.q75g2000hsh.googlegroups.com...
> Hi all,
> We've got a product which is three tier,
> using a .NET Client -> .NET Server which in turn connects to a Sql
> Server 2005 Instance.
> On top of this we also have a Windows Service which runs nightly
> processes also written in .NET
> and connects directly to the SQL Server instance.
> It's all working pretty well, except that in some installations the
> Nightly Processes service
> is failing to connect to the SQL Server instance.
> We're getting the following message:
> ________________________________________
_________________________
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections
> .......
> ________________________________________
_________________________
> This has us confused. The nightly processes is using an indentical
> connection string
> to the .NET Server. The .NET application is connecting fine
> everytime.
> The service and the application server are sitting on the same machine
> as the SQL Server instance,
> so no remote connection should be needed.
> The problem seems to happen only on Windows Server Machines/SQL Server
> installations vs WinXP/SQLExpress, however that could be unrelated.
> Any thoughts appreciated.
> Cheers
> Chris.
>|||Cheers Bill,
I've taken a good look through your page.
I think the most likely scenario might be that the service
is running the local-system account and this may not
have access for some reason, the SQL services are running
under a different windows logon.
The SQL Server instance is running in mixed mode security.
I know where to find the permissions, how can I find out if "Local
System"
has access?
Cheers
Chris|||OK i've checked and LocalSystem already has Connect SQL access,
so I don't think it's that...
Hmmmm...
We've got a product which is three tier,
using a .NET Client -> .NET Server which in turn connects to a Sql
Server 2005 Instance.
On top of this we also have a Windows Service which runs nightly
processes also written in .NET
and connects directly to the SQL Server instance.
It's all working pretty well, except that in some installations the
Nightly Processes service
is failing to connect to the SQL Server instance.
We're getting the following message:
________________________________________
_________________________
An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections
.......
________________________________________
_________________________
This has us confused. The nightly processes is using an indentical
connection string
to the .NET Server. The .NET application is connecting fine
everytime.
The service and the application server are sitting on the same machine
as the SQL Server instance,
so no remote connection should be needed.
The problem seems to happen only on Windows Server Machines/SQL Server
installations vs WinXP/SQLExpress, however that could be unrelated.
Any thoughts appreciated.
Cheers
Chris.Do ou use TCP port ?
If yes do you use autopmatic selection of port number ?
If yes it is preferable to fixed a tcp port to connect to SQL server, using
autoamtic selction of port might affect such connection trouble
Hope it helps
serge
"theinvisibleGhost" wrote:
> Hi all,
> We've got a product which is three tier,
> using a .NET Client -> .NET Server which in turn connects to a Sql
> Server 2005 Instance.
> On top of this we also have a Windows Service which runs nightly
> processes also written in .NET
> and connects directly to the SQL Server instance.
> It's all working pretty well, except that in some installations the
> Nightly Processes service
> is failing to connect to the SQL Server instance.
> We're getting the following message:
> ________________________________________
_________________________
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections
> ........
> ________________________________________
_________________________
> This has us confused. The nightly processes is using an indentical
> connection string
> to the .NET Server. The .NET application is connecting fine
> everytime.
> The service and the application server are sitting on the same machine
> as the SQL Server instance,
> so no remote connection should be needed.
> The problem seems to happen only on Windows Server Machines/SQL Server
> installations vs WinXP/SQLExpress, however that could be unrelated.
> Any thoughts appreciated.
> Cheers
> Chris.
>|||Not as far as I'm aware. It's certainly not referenced in the
connection string?|||See my whitepaper on connecting... it might turn up some issues that you had
not considered.
http://betav.com/blog/billva/2006/0...onnected_1.html
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"theinvisibleGhost" <theinvisibleGhost@.yahoo.com> wrote in message
news:1178703769.427072.296430@.q75g2000hsh.googlegroups.com...
> Hi all,
> We've got a product which is three tier,
> using a .NET Client -> .NET Server which in turn connects to a Sql
> Server 2005 Instance.
> On top of this we also have a Windows Service which runs nightly
> processes also written in .NET
> and connects directly to the SQL Server instance.
> It's all working pretty well, except that in some installations the
> Nightly Processes service
> is failing to connect to the SQL Server instance.
> We're getting the following message:
> ________________________________________
_________________________
> An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections
> .......
> ________________________________________
_________________________
> This has us confused. The nightly processes is using an indentical
> connection string
> to the .NET Server. The .NET application is connecting fine
> everytime.
> The service and the application server are sitting on the same machine
> as the SQL Server instance,
> so no remote connection should be needed.
> The problem seems to happen only on Windows Server Machines/SQL Server
> installations vs WinXP/SQLExpress, however that could be unrelated.
> Any thoughts appreciated.
> Cheers
> Chris.
>|||Cheers Bill,
I've taken a good look through your page.
I think the most likely scenario might be that the service
is running the local-system account and this may not
have access for some reason, the SQL services are running
under a different windows logon.
The SQL Server instance is running in mixed mode security.
I know where to find the permissions, how can I find out if "Local
System"
has access?
Cheers
Chris|||OK i've checked and LocalSystem already has Connect SQL access,
so I don't think it's that...
Hmmmm...
Sunday, February 19, 2012
failure in starting the process for the user instance
High everybody,
I have a set of winforms (.NET 2.0 assemblies) ( 6 total ) that each tries to open a connection to the same Database file using the same connection string. In the connection string, UserInstance is set to true.
If each winform is started manually after opening the session on the computer, the connection to the database performs well for every winform.
If the same winforms are automatically started at the opening of the user session, the the following error is reported by each application when trying to open the connection :
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
The only way to overcome this problem is :
to stop the winforms, to stop the SQLExpress service, to kill the remaining sqlserv.exe running task, then restarting SQLExpress service, and finally manualy start the winforms.
Any help would be greatly appreciated.
Hi Henri,
When you say "a set of winforms" do you mean a single applications or six different applications?
Are all these forms being opened by the same user?
Is the database embedded in the application or is it located somewhere else? (If somewhere else, where?)
You can frequently find more detailed information about this error in the User Instance error log which is located in the user profile directories of the user who is starting the user instance: C:\Documents and Settings\<user name>\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS. Check out this file and let us know what it says.
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
I get a similar problem. I get this message anytime I try to open the database from within VB Express. I was following Lesson 08 by trying to Add a SQL Server Item Template to my project.
Here is what I found in my logs.
2006-04-08 17:11:44.62 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2006-04-08 17:11:44.07 spid4s Starting up database 'mssqlsystemresource'.
2006-04-08 17:11:44.32 spid4s Error: 15466, Severity: 16, State: 1.
2006-04-08 17:11:44.32 spid4s An error occurred during decryption.
2006-04-08 17:11:44.50 spid4s The current master key cannot be decrypted. The error was ignored because the FORCE option was specified.
Does this only happen when connecting to the user instance? Can you connect to the main instance?
Thanks
Laurentiu
Hi Mike,
Thank you for your help and sorry for the late answer, but I am still on holidays. I will try to get the User Instance log at the customer site.
my application consists of six different exe that are started at the same time when opening the user session ( on a windows 2000 server). Each of these exe makes a connection to the same database file using the same connection string. When the user session is opened, there are other softwares that are automatically started which makes the CPU usage about 100% for a few minutes.
However, when each exe is started manually one after the other, the connection to the User Instance is done without error.
regards,
Henri d'Orgeval
|||Hi Mike,
here is the error log content :
2006-04-13 10:41:30.09 Server Microsoft SQL Server 2005 - 9.00.1314.06 (Intel X86)
Sep 2 2005 21:10:31
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2006-04-13 10:41:30.09 Server (c) 2005 Microsoft Corporation.
2006-04-13 10:41:30.09 Server All rights reserved.
2006-04-13 10:41:30.09 Server Server process ID is 2468.
2006-04-13 10:41:30.09 Server Logging SQL Server messages in file 'C:\Documents and Settings\AdminIt\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log'.
2006-04-13 10:41:30.09 Server Registry startup parameters:
2006-04-13 10:41:30.09 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2006-04-13 10:41:30.09 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2006-04-13 10:41:30.09 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2006-04-13 10:41:30.09 Server Command Line Startup Parameters:
2006-04-13 10:41:30.09 Server -d C:\Documents and Settings\AdminIt\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\master.mdf
2006-04-13 10:41:30.09 Server -l C:\Documents and Settings\AdminIt\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\mastlog.ldf
2006-04-13 10:41:30.09 Server -e C:\Documents and Settings\AdminIt\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS\error.log
2006-04-13 10:41:30.09 Server -c
2006-04-13 10:41:30.09 Server -S SQLEXPRESS
2006-04-13 10:41:30.09 Server -s F2DAFDAF-4081-43
2006-04-13 10:41:30.09 Server -w 60
2006-04-13 10:41:30.09 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-04-13 10:41:30.09 Server Detected 2 CPUs. This is an informational message; no user action is required.
2006-04-13 10:41:30.46 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2006-04-13 10:41:30.79 Server Database mirroring has been enabled on this instance of SQL Server.
2006-04-13 10:41:30.81 spid5s Starting up database 'master'.
2006-04-13 10:41:30.90 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2006-04-13 10:41:31.04 spid5s SQL Trace ID 1 was started by login "sa".
2006-04-13 10:41:31.10 spid5s Starting up database 'mssqlsystemresource'.
2006-04-13 10:41:31.21 Server Server local connection provider is ready to accept connection on [ \\.\pipe\F2DAFDAF-4081-43\tsql\query ].
2006-04-13 10:41:31.21 spid7s Starting up database 'model'.
2006-04-13 10:41:31.21 spid5s Server name is 'IT-SHAPER1\F2DAFDAF-4081-43'. This is an informational message only. No user action is required.
2006-04-13 10:41:31.21 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2006-04-13 10:41:31.21 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2006-04-13 10:41:31.34 spid5s Starting up database 'msdb'.
2006-04-13 10:41:31.48 spid7s Clearing tempdb database.
2006-04-13 10:41:32.12 spid7s Starting up database 'tempdb'.
2006-04-13 10:41:32.18 spid5s Recovery is complete. This is an informational message only. No user action is required.
2006-04-13 10:41:32.18 spid10s The Service Broker protocol transport is disabled or not configured.
2006-04-13 10:41:32.18 spid10s The Database Mirroring protocol transport is disabled or not configured.
2006-04-13 10:41:32.34 spid10s Service Broker manager has started.
2006-04-13 10:41:32.54 spid51 Starting up database 'C:\PROGRAM FILES\W.A.I.S. TECHNOLOGY\DISTRIBUTION MANAGER\DISTRIBUTIONMANAGER.MDF'.
There are other error logs named errorN.log that contains the same content
Best regards,
Henri d'Orgeval
|||This appears to be a successful errorlog. Can you post the errorlog that contains the errors you have extracted and posted in your earlier post?
Also, based on your description of the problem, have you considered starting the six instances of your program in succession, with a small delay between them. This might be a workaround until we determine the cause of this failure.
Thanks
Laurentiu
Hi Henri,
I'm still not clear on when you're getting the error. You state that when each exe is started one after another the connection is done without error, when do you get the error?
As for the error log, could you confirm that you pulled that error log for the User Instance and not the main instance? The User Instance error log would be located at C:\Documents and Settings\<user>\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS where <user> is the user that experienced the problem.
Regards,
Mike Wachal
SQL Express team
-
Please mark your thread as Answered when you get your solution.
Hi Henri,
Could you give a bit more information as requested by both Laurentiu and me? It's still not clear to use how your application is actually starting and where the error is occuring.
Have you tried the process that Laurentiu suggests and did it work for you?
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
Hi Mike and Laurentiu,
I confirm that if each exe is started one after the other, waiting a little bit between each launch, everything is right. This is the only workaround I found that works every time.
If the 6 exes are started at the same time at the opening of the user session ( ie the 6 exes are started from the Startup folder of the User Session), then each exe reports the same error which is the one I mentioned at my first post.
To reproduce the problem the following is done :
1°) the station is rebooted,
2°) as soon as the Login/Password screen appears on the screen, the operator opens the session, which starts the 6 exe at the same time.
3°) then each exe immediately tries to open the connection by attaching the same database file and using the same connection string.
About the error log file I posted :
There are many error log files in the User Instance SQL folder, but the content of each of these error log files is similar to what I posted.
I agree with you, surprisingly it does not look like an error has occured !
I am currently rewriting the software in order to have only one exe that will start 6 different threads one after the other.
Best regards
Henri d'Orgeval
|||I actually expect that only 5 exes are failing and the 6th succeeds. Can you please confirm this?
The process of connecting to the user instance works like this (this is a high level description):
1. if the instance exists, connect to it
2. otherwise start up the instance
3. connect to the instance
I expect all exe's try step 1 and find that there's no instance, then they all try to start it up, but only one will succeed and the others will fail. This is to be expected and can be resolved in several ways:
(a) start the exe's in succession. This was already proposed and verified to be a valid solution.
(b) start one exe first and after some delay start all the others.
(c) implement code in the exe to handle the connection failure and attempt to reconnect for several times with some delay in between.
Thanks
Laurentiu
Subscribe to:
Posts (Atom)