Intermittent Failure Of Interdatabase Service With SP-1 CTP
Apr 5, 2006
In an SSB test project created from the T-SQL batch in Stuart Padley's Weblog (subtitled "SQL Server 2005 stuff I couldn't find anywhere else", http://blogs.msdn.com/stuartpa/archive/2005/07/25/443229.aspx) I found strange inconsistencies with enquing messages between two databases on the same SQL Server 2005 Standard Edition SP-1 CTP March instance running under Windows Server 2003 SE SP-1:
Sending a simple message from the Initiator to the Target database with either the SendMessageProc stored procedure or its code as a batch fails for about 50% of all tries, with varying failure patters (up to 10 sequential attempts fail). Messages for failed tries remained in the transmission_queue, but didn't appear in the InitiatorQueue or TargetQueue.
I made the following changes to Stuart's code in the SendMessageProc procedure and my SendInitiatorToTarget.sql messaging script:
1. Split out EXEC SendMessageProc from Stage 4 and all of Stage 5 into a separate batch to enable sending multiple messages without recreating all objects.
2. Changed BEGIN DIALOG to BEGIN DIALOG CONVERSATION
3. Added a missing END CONVERSATION statement
A simple intradatabase service based on the "Hello World" DB Engine sample run in the Northwind or AdventureWorks database behaves as expected.
The partition with SQLS 2005 SP-1 also has SSX SP-1 with Advanced Services installed. Some minor problems occured when installing SSX SP-1, so I removed the original SSX instance and reinstalled SSX SP-1. See http://oakleafblog.blogspot.com/2006/03/sql-server-2005-sp1-ctp-available-for.html.
The same SSMS project runs fine on a fresh install of SQLS 2005 RTM under WS 2003 SP-1 on another machine partition. (This machine isn't running VS.) No messages fail to reach the Target database, as would be expected.
Has anyone else encountered similar anomalous behavior with SSB under SP-1 CTP? This problem ran me nuts for an entire day until I finally gave up and created a new SQLS 2005 RTM test instance.
If anyone (especially Remus) wants a copy of the scrpt, send your e-mail address to roger_jennings(nospam_at)compuserve(nospam_dot)com.
We seem to be being plagued by the error below by our SQL Server agent. This happens almost everytime we restart the server that has been running for a day or two.
Our SQL Server Agent uses a none expiring domain credential. I understand that this problem only happens when the profile being used by the SQL Servr Agent has changed (password change). What puzzles me is that the login is A ok and no changes has been made to it's password.
We always resolve this problem by changing the login used in the SQL Server Agent to local and after that, returning it back to it's original domain login. Unfortunately, we cant always do this everytime something goes wrong.
Can anyone please help us shed a light on this? We're using SQL2k with SP3a. Thanks!
Error:
An error 1069 - )The service did not start due to logon failure) occurred while performing this service operation on the SQLServerAgent service.
I have a User function created within one SQL DB (an allways existing DB), but I want to run it on DB's (with same structure: tabels, views,...) that are dinamically created (one per mount), is this possible?
Hello to all,I have say two databases A and B.A database has tables a1 and a2.B database has a table b1.My question isCan i write a trigger for the table b1, which access the fields fromthe table a1 and a2?Simply, can i write a trigger which access data from other databases?Thank you in advance,vishnu
Trying to install Service Pack 2 on a production server and it fails updating the Database Services with an 11032 error. Here is the summery log.
Time: 09/13/2007 20:43:21.980 KB Number: KB921896 Machine: SQLDATABASE OS Version: Microsoft Windows Server 2003 family, Service Pack 2 (Build 3790) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: No
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.2.3042 x86 Database Services (MSSQLSERVER) ENU SP1 2005.090.2047.00 x86 STANDARD Integration Services ENU SP2 9.00.3042.00 x86 STANDARD SQL Server Native Client ENU 9.00.3042.00 x86 Client Components ENU SP2 9.2.3042 x86 STANDARD MSXML 6.0 Parser ENU 6.10.1200.0 x86 SQLXML4 ENU 9.00.3042.00 x86 Backward Compatibility ENU 8.05.2004 x86 Microsoft SQL Server VSS Writer ENU 9.00.3042.00 x86
DNS lookup failed with error: '11001(error not found)'.
when I select transmisson status from sys.transmission_queue on the initiating server.
I am setting up a service broker to connect 2 servers. I have used two different code samples - one to use windows auth, the other with certificates. Both give me the above error. I have connected to the sending and receiving instances with Profiler, with no luck - the receiving instance does not begin to react.
I have endpoints on instance 1 & 2 - ports 5040 and 5041. The route on instance 1 is to instance2 endpoint & service - on the initiator, select * from sys.routes gives: RouteToTargetServer 65539 1 TargetService NULL NULL TCP://TargetSSBEndPoint:5041 NULL
I think that there may be a ports issue (?) so I've checked the ports - telnet <machinename> 5040 which seems OK. I have admin access on my machine - for test, I have 2 instances on the same PC.
I'm new to sql server administration so please show some understanding!
I installed sql server 2000 personal edition (upgrated to sp4) on an windows xp pro OS, but I cannot get the sql server agent service running. I get a message " the service did not start due to a logon failure". The server is my local pc, I'm using windows authentication and the login is "domain/loginname" where domain is my pc name.
Does it have to be installed on a server OS to have this service running?
I am a member of the Administrators group, and there is plenty of space in all hard drives, plus the temp directory is open for "everybody" to full-control it. Yet the Service Pack 2 database engine fails, all other components upgrade fine.
---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 3033 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29506 Error Description : MSP Error: 29506 SQL Server Setup failed to modify security permissions on file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData for user SYSTEM. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive. -
I get this error (connection closed) in web applications, whenever SQL Server database Service is restarted. When I run the application again, the error disappears. Granted that there are lots of users and Database gets restarted every night is not helping.
Is there any setting in the JDBC driver properties, where I can tell it to open a closed connection (like a retry count), rather than fail the first time and work the second time.
We use 1. SQL SERVER 2005 SP2, 2. Websphere Protal Server 5.1 3. SQL SERVER 2005 JDBC driver 1.1(com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolDataSource.)
I am wondering if connection pool driver is causing this problem. I do not care about connection pooling, but Websphere doen not seem to like any other JDBC Driver. I don't mind switching to another driver as the last option.
Error is : [11/27/07 17:01:59:331 MST] 7202440d WSRdbManagedC W DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.getCatalog(Unknown Source) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.getCatalog(WSRdbManagedConnectionImpl.java:676) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.introspectSelf(WSRdbManagedConnectionImpl.java:808) at com.ibm.ws.rsadapter.FFDCLogger.introspect(FFDCLogger.java:169) at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.introspectSelf(WSJdbcConnection.java:1253) at com.ibm.ws.ffdc.IntrospectionLevelMember.getNextMembers(IntrospectionLevelMember.java(Compiled Code)) at com.ibm.ws.ffdc.IntrospectionLevel.getNextLevel(IntrospectionLevel.java:181) at com.ibm.ws.ffdc.ObjectIntrospectorImpl.dumpContents(ObjectIntrospectorImpl.java:67) at com.ibm.ws.ffdc.ObjectIntrospectorImpl.dumpContents(ObjectIntrospectorImpl.java:51) at com.ibm.ws.ffdc.IncidentStreamImpl.introspectAndWrite(IncidentStreamImpl.java:396) at com.ibm.ws.ffdc.IncidentStreamImpl.introspectAndWriteLine(IncidentStreamImpl.java:632) at com.ibm.ws.ffdc.DiagnosticEngine.dumpObjectAndStack(DiagnosticEngine.java:301) at com.ibm.ws.ffdc.DiagnosticEngine.processIncident(DiagnosticEngine.java:147) at com.ibm.ws.ffdc.FFDCFilter.filterEngine(FFDCFilter.java:428) .......lots of lines
All of items of the service pack will install execpt for the Database Services.
The Details are:
"Unable to install Windows Installer MSP file"
Log Details Below
05/04/2006 08:18:42.327 ================================================================================ 05/04/2006 08:18:42.327 Hotfix package launched 05/04/2006 08:18:43.827 Product discovery successfully completed during the install process for MSSQLSERVER 05/04/2006 08:18:43.827 SP Level check successfully completed during the install process for MSSQLSERVER 05/04/2006 08:18:43.827 Product language check successfully completed during the install process for MSSQLSERVER 05/04/2006 08:18:43.827 Product version check successfully completed during the install process for MSSQLSERVER 05/04/2006 08:18:43.827 Command-line instance name check completed during the install process 05/04/2006 08:18:43.827 Baseline build check completed during the install process 05/04/2006 08:19:12.014 Attempting to install instance: MSSQLSERVER 05/04/2006 08:19:12.060 Attempting to install target: REPORTS 05/04/2006 08:19:12.076 Attempting to stop service: SQLSERVERAGENT 05/04/2006 08:19:17.154 Successfully stopped service: SQLSERVERAGENT 05/04/2006 08:19:17.154 Attempting to stop service: MSSQLServer 05/04/2006 08:19:19.154 Successfully stopped service: MSSQLServer 05/04/2006 08:19:19.154 Attempting to check for locked files: sqlrun_sql.msp 05/04/2006 08:19:19.326 Attempting to check for locked files: \REPORTSe$7d39b5ebc15c1b5ee29a229c92b3HotFixSQLFilessqlrun_sql.msp 05/04/2006 08:19:19.326 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out 05/04/2006 08:19:38.029 MSP returned 1602: The user cancels installation. 05/04/2006 08:19:38.169 Successfully checked file: \REPORTSe$7d39b5ebc15c1b5ee29a229c92b3HotFixSQLFilessqlrun_sql.msp 05/04/2006 08:19:38.169 Successfully opened registry key: SystemCurrentControlSetControlSession Manager 05/04/2006 08:19:38.169 Failed to read registry key: PendingFileRenameOperations 05/04/2006 08:19:38.169 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll 05/04/2006 08:19:38.169 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll 05/04/2006 08:19:38.169 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll 05/04/2006 08:19:38.169 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll 05/04/2006 08:19:38.169 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnlhtml.dll 05/04/2006 08:19:38.169 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll 05/04/2006 08:19:38.169 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe 05/04/2006 08:19:38.169 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll 05/04/2006 08:19:38.185 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe 05/04/2006 08:19:38.185 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll 05/04/2006 08:19:38.185 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll 05/04/2006 08:19:38.185 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll 05/04/2006 08:19:38.185 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll 05/04/2006 08:19:38.185 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll 05/04/2006 08:19:38.185 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL 05/04/2006 08:19:38.185 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll 05/04/2006 08:19:38.185 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll 05/04/2006 08:19:38.185 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplrec.dll 05/04/2006 08:19:38.185 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM plisapi.dll 05/04/2006 08:19:38.185 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:WINDOWSassemblyGAC_64Microsoft.SqlServer.Replication9.0.242.0__89845dcd8080cc91Repl.dll 05/04/2006 08:19:38.185 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll 05/04/2006 08:19:38.185 Failed to read version information for the following file: C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources10332005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall plhtfin.sql 05/04/2006 08:19:38.185 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe 05/04/2006 08:19:38.185 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program Files (x86)Microsoft SQL Server90COMsnapshot.exe 05/04/2006 08:19:38.185 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM9.0.2047.0 C:Program FilesMicrosoft SQL Server90COMsqlmergx.dll 05/04/2006 08:19:38.185 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM abldiff.exe 05/04/2006 08:19:38.185 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe 05/04/2006 08:19:38.185 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe 05/04/2006 08:19:38.185 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources30822005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources2052sqlevn70.rll 05/04/2006 08:19:38.185 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10532005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1046sqlevn70.rll 05/04/2006 08:19:38.185 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10432005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1042sqlevn70.rll 05/04/2006 08:19:38.185 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10412005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1040sqlevn70.rll 05/04/2006 08:19:38.185 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10362005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033sqlevn70.rll 05/04/2006 08:19:38.185 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10312005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1028sqlevn70.rll 05/04/2006 08:19:38.185 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10332005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlacc~1.dll 05/04/2006 08:19:38.185 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlrwbin.dll 05/04/2006 08:19:38.201 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2.0.3609.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 05/04/2006 08:19:38.201 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLBOOT.dll 05/04/2006 08:19:38.201 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxplog70.dll 05/04/2006 08:19:38.201 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnatchp~1.dll 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 05/04/2006 08:19:38.201 Failed to read version information for the following file: C:Program Files (x86)Microsoft SQL Server90SharedResources10339.0.2047.0 C:Program Files (x86)Microsoft SQL Server90Sharedmsmdrdir.dll 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedmsmdlocal.dll 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedmsmdlocal.dll 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedmsmdlocal.dll 05/04/2006 08:19:38.201 Failed to read version information for the following file: C:Program Files (x86)Common FilesSystemole db2.0.3609.0 C:Program Files (x86)Common FilesSystemole dbxmlrw.dll 05/04/2006 08:19:38.201 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0 C:Program FilesCommon FilesSystemole dbxmlrw.dll 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedsqlbrowser.exe 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedsqlbrowser.exe 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedsqlbrowser.exe 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedmsasxpress.dll 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedmsasxpress.dll 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedmsasxpress.dll 05/04/2006 08:19:38.201 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 05/04/2006 08:19:38.216 Failed to read version information for the following file: C:Program Files (x86)Microsoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml 05/04/2006 08:19:38.216 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll 05/04/2006 08:19:38.216 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server (x86)90ToolsBinnResources1033 E:Program FilesMicrosoft SQL Server (x86)90ToolsBinnResources1033sqlcm.xml 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server (x86)90ToolsBinnResources1033SqlManager.rll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server (x86)90ToolsBinnResources1033SqlManager.rll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server (x86)90ToolsBinnResources1033SqlManager.rll 05/04/2006 08:19:38.216 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033 E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server (x86)90ToolsinnSqlManager.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server (x86)90ToolsinnSqlManager.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server (x86)90ToolsinnSqlManager.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server (x86)90ToolsBinnatchparser90.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server (x86)90ToolsBinnatchparser90.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server (x86)90ToolsBinnatchparser90.dll 05/04/2006 08:19:38.216 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 05/04/2006 08:19:38.232 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0 E:Program FilesMicrosoft SQL Server (x86)90ToolsinnSQLSVC90.DLL 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 05/04/2006 08:19:38.232 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0 E:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe 05/04/2006 08:19:38.232 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0 C:Program Files (x86)Microsoft SQL Server90Sharedsqlsvc~1.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedsqlsecacctchg.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedsqlsecacctchg.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedsqlsecacctchg.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedsqlftacct.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedsqlftacct.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedsqlftacct.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedisacctchange.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedisacctchange.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedisacctchange.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedsvrenumapi.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedsvrenumapi.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedsvrenumapi.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsvcsync.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsvcsync.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsvcsync.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 05/04/2006 08:19:38.232 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 05/04/2006 08:19:38.247 Failed to read version information for the following file: C:Program Files (x86)Microsoft SQL Server90Shared2005.90.2047.0 C:Program FilesMicrosoft SQL Server90SharedSqlBoot.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90Sharedsqlsqm.exe 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe 05/04/2006 08:19:38.247 Failed to read version information for the following file: C:Program Files (x86)Microsoft SQL Server90Shared9.0.2047.0 C:Program Files (x86)Microsoft SQL Server90Shareddbghelp.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90SharedSqlDumper.exe 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90SharedSqlDumper.exe 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90SharedSqlDumper.exe 05/04/2006 08:19:38.247 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0 C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_64Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_64Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_64Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll 05/04/2006 08:19:38.247 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll 05/04/2006 08:19:38.263 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90SharedSqlSAC.exe 05/04/2006 08:19:38.263 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90SharedMicrosoft.SqlSac.Public.dll 05/04/2006 08:21:12.933 Attempting to install file: sqlrun_sql.msp 05/04/2006 08:21:12.949 Attempting to install file: \REPORTSe$7d39b5ebc15c1b5ee29a229c92b3HotFixSQLFilessqlrun_sql.msp 05/04/2006 08:21:12.949 Creating MSP install log file at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log 05/04/2006 08:21:12.949 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 05/04/2006 08:21:12.949 Failed to read registry key: Debug 05/04/2006 08:22:23.775 MSP returned 1603: A fatal error occurred during installation. 05/04/2006 08:22:23.838 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 05/04/2006 08:22:23.838 Failed to read registry key: Debug 05/04/2006 08:22:23.838 Unable to install MSP file: \REPORTSe$7d39b5ebc15c1b5ee29a229c92b3HotFixSQLFilessqlrun_sql.msp 05/04/2006 08:22:23.838 The following exception occurred: Unable to install Windows Installer MSP file Date: 05/04/2006 08:22:23.838 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 856 05/04/2006 08:22:23.885 05/04/2006 08:22:23.885 Product Status Summary: 05/04/2006 08:22:23.885 Product: SQL Server Native Client (64-bit) 05/04/2006 08:22:23.885 SQL Server Native Client (64-bit) (RTM ) - Success 05/04/2006 08:22:23.885 05/04/2006 08:22:23.885 Product: Setup Support Files (64-bit) 05/04/2006 08:22:23.885 Setup Support Files (64-bit) (RTM ) - Success 05/04/2006 08:22:23.885 05/04/2006 08:22:23.885 Product: Database Services (64-bit) 05/04/2006 08:22:23.885 Database Services (64-bit) (RTM 1399 ENU) - Failure 05/04/2006 08:22:23.885 Details: Unable to install Windows Installer MSP file 05/04/2006 08:22:23.885 Analysis Services (64-bit) (SP1 2047 ENU) - Not Applied 05/04/2006 08:22:23.885 Reporting Services (64-bit) (SP1 2047 ENU) - Not Applied 05/04/2006 08:22:23.885 05/04/2006 08:22:23.885 Product: Notification Services (64-bit) 05/04/2006 08:22:23.885 Notification Services (64-bit) (SP1 2047 ENU) - Not Applied 05/04/2006 08:22:23.885 05/04/2006 08:22:23.885 Product: Integration Services (64-bit) 05/04/2006 08:22:23.885 Integration Services (64-bit) (SP1 2047 ENU) - Not Applied 05/04/2006 08:22:23.885 05/04/2006 08:22:23.885 Product: Client Components (64-bit) 05/04/2006 08:22:23.885 Client Components (64-bit) (SP1 2047 ENU) - Not Applied 05/04/2006 08:22:23.885 05/04/2006 08:22:23.885 Product: MSXML 6.0 Parser (64-bit) 05/04/2006 08:22:23.885 MSXML 6.0 Parser (64-bit) (RTM ) - Not Applied 05/04/2006 08:22:23.885 05/04/2006 08:22:23.885 Product: SQLXML4 (64-bit) 05/04/2006 08:22:23.885 SQLXML4 (64-bit) (RTM ) - Not Applied 05/04/2006 08:22:23.885 05/04/2006 08:22:23.885 Product: Backward Compatibility (64-bit) 05/04/2006 08:22:23.885 Backward Compatibility (64-bit) (RTM ) - Not Applied 05/04/2006 08:22:23.885 05/04/2006 08:22:23.885 Product: Microsoft SQL Server VSS Writer (64-bit) 05/04/2006 08:22:23.885 Microsoft SQL Server VSS Writer (64-bit) (RTM ) - Not Applied 05/04/2006 08:22:23.885
I have tried different log ons - Domain Administration / Administrator (but not a local administrator)
I am attempting to run an SSIS package from a web service. Right now both the service and package are on my local machine which is running XP. I have accessed the web service from a client application in debug mode. I am not sure if it is actually running under aspnet_wp.exe because it is XP and a development environment? (separate question)??? The package fails with a series of OnError messages similar to:
The result of the expression ""/c DEL /F /Q "" + @DeployFolder + "\catalog.diff.lz""" on property "Arguments" cannot be written to the property. The expression was evaluated, but cannot be set on the property.
An initial supposition is that the permissions of the web service are inadequate for the package. I have the authentication as "Windows" and <identity impersonate="true" /> in the Web.Config file. When I break in the debugger the Environment.UserName and Environment.UserDomainName are mine and I am an Admin on the box. the authorization is 'deny users="?".
The article that describes basic implementation of this in a Web Service states:
With its default settings for authentication and authorization, a Web service generally does not have sufficient permissions to access SQL Server or the file system to load and execute packages. You may have to assign appropriate permissions to the Web service by configuring its authentication and authorization settings in the web.config file and assigning database and file system permissions as appropriate. A complete discussion of Web, database, and file system permissions is beyond the scope of this topic.
And how!
Note that the load is fine and that this is a run time error and that the package runs correctly when run manually from SQL Server using the 'run package' menu item in the Object Explorer tree of the SQL Server Management Console.
I need to know if this is an ASP.NET issue per se or XP or if this is even a security issue. And how to solve it! This is critical path so an expeditious reply with a solution would be greatly appreciated.
Windows Update Web Page indicates I have BOTH a SUCCESS and FAILURE for SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) ?Is it possible for my machine to have TWO DIFFERENT MS SQL Server Express installations? Is the problem real or some small ghost issue? I do have a trial CD from Microsoft .. Visual Studio 2005 Team Suite.
Please note that this is what windows update indicates on the web page duplicate lines are on the web page .. not a copy and paste mistake.
SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) Tuesday, March 13, 2007 Microsoft Update SQL Server 2005 Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896) Tuesday, March 13, 2007 Microsoft Update
LINK FOLLOWED Installation Failure Error Code: 0x652 Try to install the update again, or request help from one of the following resources
I include the logfile since it seems to convey useful informations to SQL Express experienced.
summary.txt logfile >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Time: 03/13/2007 12:28:02.906 KB Number: KB921896 Machine: somejunk 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 SP2 2005.090.3042.00 x86 EXPRESS Express Database Services (SQLExpress) ENU RTM x86 EXPRESS
Hi all, I had to uninstall SQL2005 Service, client-tools & BI studio applications on my laptop running XP SP-2. Now, I'm trying a fresh install, a simple install of >>just<< the 2005 DB service is failing. Snippet of log file------------------------- MSI (s) (F8:80) [22:35:02:484]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (F8:80) [22:35:02:484]: Warning: Local cached package 'C:WINDOWSInstaller4c483c.msi' is missing. Snippet of log file-------------------------
CSetupBootstrapWizard returned 1 <EndFunc Name='DisplaySCCWizard' Return='0' GetLastError='183'> Failed to find help file for LCID :3081 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0 <EndFunc Name='DwLaunchMsiExec' Return='0' GetLastError='0'> Complete: InvokeSqlSetupDllAction at: 2006/10/8 22:18:10, returned true Running: SetPackageInstallStateAction at: 2006/10/8 22:18:10 Complete: SetPackageInstallStateAction at: 2006/10/8 22:18:12, returned true Running: DeterminePackageTransformsAction at: 2006/10/8 22:18:12 Complete: DeterminePackageTransformsAction at: 2006/10/8 22:18:25, returned true Running: ValidateSetupPropertiesAction at: 2006/10/8 22:18:25 Complete: ValidateSetupPropertiesAction at: 2006/10/8 22:18:25, returned true Running: OpenPipeAction at: 2006/10/8 22:18:25 Complete: OpenPipeAction at: 2006/10/8 22:18:25, returned false Error: Action "OpenPipeAction" failed during execution. Running: CreatePipeAction at: 2006/10/8 22:18:25 Complete: CreatePipeAction at: 2006/10/8 22:18:25, returned false Error: Action "CreatePipeAction" failed during execution. Action "RunRemoteSetupAction" will be skipped due to the following restrictions: Condition "Action: CreatePipeAction has finished and passed." returned false.
The OWC11 setup failure is triggerring SQL DB Service installation to fail as well. Please help!!!
The SQL Server Agent (MSSQLSERVER) service on server started and then stopped. If i Manually start the services also SQL Server Agent services are stopping automatically.Though I selected Auto Restart SQL Server Agent if it stops unexpectedly, The services are stopping automatically.TCP/IP protocol was enabled for port 1433.Are there any setup I missed?
I have this problem occuring intermittently:When I try to add a package to the project, and click on the Packagepath button. I get a oledb error x080004005 (client unable toestablish connection)...After I click ok, and click on the Package path again 2 or 3 times,the error goes away and I get the list of packages displayed. Sometime I get an empty list box.Similar to this happens when I execute a package also. When I executeit 2nd or 3 rd time it works fine. The error happens only when I amtrying to connect to the serverdatabase. Once it is in the databaseI do not get any error message.This is what I have:I have sql 2005 installed.Microsoft SQL Server ManagementStudio9.00.1399.00Microsoft Analysis Services ClientTools2005.090.1399.00Microsoft Data Access Components(MDAC)2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)Thank you in advance!!!
When I try to add a package to the project, and click on the Package path button. I get a oledb error x080004005 (client unable to establish connection)...
After I click ok, and click on the Package path again 2 or 3 times, the error goes away and I get the list of packages displayed. Some time I get an empty list box.
Similar to this happens when I execute a package also. When I execute it 2nd or 3 rd time it works fine. The error happens only when I am trying to connect to the serverdatabase. Once it is in the database I do not get any error message.
This is what I have:
I have sql 2005 installed. Microsoft SQL Server Management Studio 9.00.1399.00 Microsoft Analysis Services Client Tools 2005.090.1399.00 Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
I have log shipping setup to 2 different servers. Every once in a while I get the
Server: Msg 3201, Level 16, State 1, Line 1 Cannot open backup device 'E:fac.dat'. Device error or device off-line. See the SQL Server error log for more details. Server: Msg 3013, Level 16, State 1, Line 1 Backup or restore operation terminating abnormally.
Checked MSDN which said it was a permissions error, which isn't right, because the same account works for this db and several others all the time. Anyone else seen this?
I've a SQL server that intermittently restarts itself mostly during. Its a SQL Server 6.5 SP4 running NT 4.0 SP6. It really has no rhyme or reason to it happening. The are no indications in either the SQL or the Nt events logs. Has anyone heard of this?
We recently migrated a SQL 2000 DB to SQL Server 2005 SP2. We have a VB 6 executable that uses the SQL Server 2005 DB. Immediately we began getting intermittent errors when trying to run a Stored Proc on SQL 2005 DB. The two errors we see are:
Timeout expired
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
If you immediately try to run the same query, it usually will work. The queries are random and so are the errors. I have gotten the time out error in Server Management Studio a couple of times.
In the VB 6 App we are using MDAC 2.81. Her is the connection string: Provider=SQLOLEDB.1;User ID=user;password=password;Initial Catalog=OASIS;Data Source=servername, portnumber
We added the port number to the DataSource in an attempt to troublshoot the issue, but it made no difference.
We have run sysinternals Process Monitor on a PC with the app running and we saw NAME NOT FOUND Results for Query Open actions for these DLLS: C:Program FilesOASISCLUSAPI.DLL C:Program FilesOASISRESUTILS.DLL C:Program FilesOASIStdsapi.dll
C:Program FilesOASIS is the application path. Of course, they are not in the application path but they are in C:WindowsSystem32. They do not seem to be registered.
Here is an example of the code we use in a class to run a SP:
Public Function FetchPostings() As ADODB.Recordset Dim cmFetch As ADODB.Command
On Error GoTo HandleError Set cmFetch = New ADODB.Command With cmFetch .Name = "FetchObligations" .ActiveConnection = gobjSecurity.Connection 'This is a connection string not a connection object .CommandText = "spClaimFetchObligations" .CommandType = adCmdStoredProc .Parameters.Append .CreateParameter("ClaimID", adInteger, adParamInput, , mlngClaimID) Set FetchObligations = .Execute End With
ExitSub: Set cmFetch = Nothing Exit Function
HandleError: gobjError.HandleError Err.Number, Err.Description, App.EXEName, "clsClaim", "FetchObligations", gobjSecurity.UserID Resume ExitSub End Function
I have VS 2005 and SQL CE 3.0. I sometimes get the a FileNotFoundException when I first use ExecuteReader. I believe this is because a dll has not been copied across because if I restart the emulator I can get it to work again.
Do I need to add a cab file/dll to my project to stop this happening?
I have developed a report that pulls its data from an SSAS cube. The report is grouped on Fields!FacilityName. On each "page" of the report, I have information for the displayed facility.
At the top of each page in my report I have a textbox whose value is =Fields!FacilityName. Further down on the report I have another text box whose value is set exactly the same. When I preview the report, I always have a value in the upper box, but only sometimes have a value in the lower box. If I change the value in the lower box to just a text string, it will always display, but when I put in the actual field reference it does not. It always doesn't display for the same facility names. Remember, the upper textbox on the form always displays 100% of the time.
I have a Dundas chart in the middle of the page on the report between these textboxes, but another field that pulls parameters and even a matrix all render correctly below that chart.
They both have the same parent according to the properties. I have even copied and pasted the working textbox further down the screen, with no improvement. When I changed the value of the textbox to "=cstr(len(Fields!FacilityName))", on the pages when it wants to be blank, it reads 0, and on other pages it shows a larger number. But the other textbox on the screen will always properly show the FacilityName.
I have also tried changing the name of the textbox, settings output to YES instead of Auto. If I slide the non-working textbox up to the top of the page and the working textbox down to the bottom area of the page, the bevavior switches.
Does anybody know of rendering issues with textboxes showing the same infomation?
We are using HTTPS anonymous merge subscriptions....
Sometimes when trying to synchonise, we will get the following error messages returned to the subscriber....
The upload message to be sent to Publisher '**thewebserver**' is being generated The merge process is using Exchange ID '0F65CFCB-AF17-47DC-8D98-493A44C243E0' for this web synchronization session. The Merge Agent could not connect to the URL 'https://**thewebserver**/client/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable. The Merge Agent could not connect to the URL 'https://**thewebserver**/client/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and that the Web server is reachable. The Merge Agent received the following error status and message from the Internet Information Services (IIS) server during Web synchronization: [401 :'Unauthorized']. When troubleshooting, ensure that the Web synchronization settings for the subscription are correct, and increase the internet timeout setting at the Subscriber and the connection timeout at the Web server.
If I then go to a web brower, put in the HTTPS address, it brings up the logon dialog - I put in the admin username and password to confirm the connection and that's fine.
We try and synchronise again, and this time it works - it's as though I have 'woken' it up again and it's happy to play.
Is increasing the timeouts as suggested by the error message the way to go ? If so, where does one set the 'internet timeout setting at the subscriber', and the 'connection timeout at the webserver' ?
I currently run a nightly replication from a windows server 2003 machine with sql server 2000 sp3 to a windows 2003 server machine with sql server 2005 sp1. I run a snapshot replication as merge is not supported from 2000 to 2005.
2 out 5 snapshots weekly fail with the following error:
2006-08-09 17:00:06.97 Message Code: 10054 2006-08-09 17:00:06.97 2006-08-09 17:00:06.97 [0%] The replication agent had encountered an exception. 2006-08-09 17:00:06.97 Source: Replication 2006-08-09 17:00:06.97 Exception Type: Microsoft.SqlServer.Replication.ConnectionFailureException 2006-08-09 17:00:06.97 Exception Message: TCP Provider: An existing connection was forcibly closed by the remote host.
I have setup the sql server 2005 agent service to automatic with a 'log on as' domain admin account. The sql server agent on the 2000 machine uses the local system account.
I'm having an issue with what appears to be SQL Server 2005 deciding to randomly ignore new connections.
I currently have two virtual servers - one running just SQL Server 2005, the other running Reporting Services, Windows Sharepoint Services and Team Foundation Server.
For 3 weeks, it was all working perfectly, then on Wednesday night the server (and both Virtual Servers) was rebooted after installing the latest updates for Windows. Since then, I've had this issue.
It will work fine for a while, then it'll start throwing loads of Errors and Warnings into the Event Log, all along the lines of unable to connect to the database. The Reporting Services Configuration utility throws up the same problem. Then randomly, it'll start working again.
If anyone has any ideas, they would be much appreciated as this is driving me crazy!
I'm working on a DB that will be used in separate physical locations. These DBs will be identical in structure and completely independent of each other. Whilst some tables will retain similar or identical information, there is a large amount of content that will diverge.However, there is a central location that will need to manage these DBs. There will be a requirement from this central location to run reports, often comparing data between them, and to push data into each child location. There is no requirement for the child locations to 'share' information and indeed the volume concerned and the intermittent/low-bandwidth nature of their connections would make this undesirable. If an individual selection of data does need to be shared between I'm happy for it to be uploaded centrally, a decision made, and manually pushed to each child-location.
Which brings me to my real question. Should I try and include composite Primary Keys in many of the tables (to include probably an incrementing number and another field of site ID) so that when I absorb them all back centrally I can put them into one large DB. Or should I keep them as separate DBs in the central location and use some fairly 'normal' mechanisms for mirroring to sites; accepting that this will make running comparisons between them more difficult and potentially more difficult to write interactivity for centrally?
The best 'real world' comparison I can think of is transactions in retail shops. How do these transaction logs get stored centrally when they're all generating individual transaction numbers that are only unique in that location?
I'm querying a small SQL2005 database and finding that the query can sometimes complete in under a second and then 5 minutes later the same query can take 15 minutes to complete.
The query I'm running is very simple as follows: select TOP 26 * from vSearchListOpportunityItem WHERE OpIt_OpportunityId=2495 ORDER BY Prod_Name, OpIt_OpportunityItemId
The view it is pulling data from only contains only 1890 lines, which in turn pulls data from 3 tables with 821, 2560, and 1957 lines of data. In other words it's small. I have noticed that if I try and open the smallest of these tables while on a 'go slow' period it also takes around 15 minutes to return the data.
The database was originally on SQL 2000. It is the only database on this powerful quad core server. The SQL Server CPU usage never goes above 40%, and always has free memory. No sign of locks.
I can't figure out why such a small database is going so slow with such a simple query. Any ideas?
After installing the Advanced Services package, I started getting errors connecting to a database (.MDF) that I've been using for weeks/months.
The error was something like "login failed for machineuser". After twiddling with the connection string and starting and stopping the SQLEXPRESS service it started working again. Did some more work, everything was fine, shutdown and went to bed.
This morning, I am unable to connect to the database - nor any other database, it seems. This time I'm getting "cannot find the physical file" type errors.
Any leads on solving this would be much appreciated. I've search using the error codes and I'm not turning anything up that seems quite like the problem I'm having.
I'm having weird issues with connecting to MS SQL Server. Sometimes it can establish a connection and sometimes it can't. This is both with ODBC and with .net code. This happens on multiple computers. I.e. one minute you can connect, the next you can't.
I have a SQL 2000 server which connects fine every time. So I assume the problem is with the upgraded MS SQL Server. I want to be able to resolve this issue before upgrading the main server to SQL 2005.
I am experiencing intermittent connection problems with the Northwind database and sql server express. The most frequent error message indicates that I am already logged in and will not allow another user.
The odd thing is that even when I am locked out I can access a Northwind database from another connection on Server Explorer.
I ran code to demonstrate simple binding for two text boxes, no problem. I added a project to show complex binding using the datagrid view tool, but could not get past selecting the database.
I tried the same simple binding project on another computer running a beta version of VS 2005 Pro and could not connect to Northwind on that computer also. (Two different Northwind databases, different computers)
A couple days ago I restored the database in Solutions Manager and that helped for a while, but I should not have to resort to that, I know.
How do I remove the user lock? I tried Solutions Manager Express with the first computer but could not access the database in the management module.
