Hi
I've recently upgraded 4 sql servers to sp5a and have just found that BCP fails on all of them with a DR Watson error. I did reinstall the Nt sp after installing sql server sp5a.
Can anyone help ?
Thanks
While installing the service pack 5a, I had the following error
"setup could not be successfully completed,
ISQL.EXE could not be executed. Please check the relevant *.Out file.
Now I am unable to start up my SQL service. When I try to start it , I get the following message:
Error : 1105, Severity: 17, State: 2
Can't allocate space for object 'Syslogs' in database 'master' because the 'logsegment' segment is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment.
Apparently 4 mb of free space in my master database was not enough for the service pack. I can't extend the size of my Master database because I can't get the SQL service to start.
Any suggestions?
LH
we have a client that just upgraded to sp5a and are encountering problems...one stored procedure seems to routinely become corrupted, and does not complete correctly. however, it does not error out, and the only way to tell that it did not complete successfully it to query the data.
the only solution that i have found to this problem is to recreate the procedure. i have tried using sp_recompile to force a recompile at next runtime, and the problem still occurs. i have tried recreating the calling procedure, and recreating procedures it calls, but neither fix the problem.
after recreating the procedure, it continues to run fine for anywhere from 1 hour to 8 hours, and then starts to fail again.
microsoft so far has not been able to give us help in diagnosing this, and i am coming up with nothing in my own investigations.
has anyone seen a problem like this in sp5a?
also, it is occurring on 5 similar dbs that are on the same server...
thanks
carl
I have been using this code for years but today it is giving me Dr Watson Error "Access Violation" can someone help pls.
BCP PROD_elsie_DB..tblStudent_Info_Temp_Alex in P:elsiedataincomingacapsstu.txt /m 100 /f G:elsieapplsqlcpbstua.fmt /e G:custbasedata
eportsbstuaiw.err /o G:elsiedata
eportsbstuaiw.out /b 1000 /Sdwslc000 /U /P
I had an error crop up with a DTS package which I need some help with.Error Message :The application, , generated an application error The error occurredon 07/20/2004 @ 06:12:28.203 The exception generated was c0000005 ataddress 41504E2C (<nosymbols>)This happened this morning, but the DTS package runs every 10 minutesand it is the only occurance of this error. Nothing in the DTS packagehas changed and there will not have been any users on the network. I'mas convinced as I can be that the DTS package is fine. Nothing obviousas to what has caused the error, and it hasn't happened again, but Iwould like to understand it more if possible.The closest answer we found was for a SQL2000 error (http://support.microsoft.com/defaul...en-us%3BQ290644 ),but we are running SQL7 (latest sp), so any fix wouldn't apply.The DTS package does a fair amount of importing data and then variousSP's are run to generate a final table of data. From the timing, itlooks to have happened at the end of the process, so would suggestsomething with an SP. Unfortunately, I cannot tell which one. 10minutes after it failed, it worked again and has since, but no-one wasin to correct anything.Any ideas ?ThanksRyan
View 1 Replies View RelatedUsing the new Visual Studio 2008 I created a setup project for a small program, and added SQL Express 2005 SP2 to the list of prerequisites.
I checked the box so the setup project will contain all necessary files in a sub directory of the setup project.
My setup starts nice (on windows vista) prompts me to install SQL Express, setup of SQL Express runs for some time, I get an UAC prompt, then setup fails with error 1706.
The last lines of the setup log file:
Installing using command 'C:UserswilfiAppDataLocalTempVSDE5B7.tmpSqlExpresssqlexpr32.exe' and parameters '-q /norebootchk /qn reboot=ReallySuppress addlocal=all instancename=SQLEXPRESS SQLAUTOSTART=1 ADDUSERASADMIN=1'
Process exited with code 1706
Status of package 'SQL Server 2005 Express Edition SP2 (x86)' after install is 'InstallFailed'
I really would like to install SQL Express as part of the setup project, can someone help me with this problem?
Thanks in advance,
Sam
I have been trying to install Visual Web Developer 2005 Express Edition and SQL Server 2005. The Web Developer installs ok but the SQL Server installation fails. I can't figure out why. I have (I think...) uninstalled my previous beta intallations. The must be something else that prevents the installation. Can anyone point me to some FAQ or something that can give me some ideas on how to handle the installation./anders
View 2 Replies View RelatedHi,
Trying to install SQL Server 2005 SP1 on a windows 2003 box and it fails for database services and reporting services patch. It installs successfully other components of the patch.
Following errors are logged in the event log.
1) Product: Microsoft SQL Server 2005 - Update 'Service Pack 1 for SQL Server Database Services 2005 ENU (KB913090)' could not be installed. Error code 1603. Additional information is available in the log file C:WINNTHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log
2) Product: Microsoft SQL Server 2005 -- Error 29506. SQL Server Setup failed to modify security permissions on file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData for user birendraa. 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.
3) Product: Microsoft SQL Server 2005 Reporting Services -- Error 29561. SQL Server Setup failed to retrieve the SSL Certificate Name.
4) Product: Microsoft SQL Server 2005 Reporting Services - Update 'Service Pack 1 for SQL Server Reporting Services 2005 ENU (KB913090)' could not be installed. Error code 1603. Additional information is available in the log file C:WINNTHotfixRS9LogsRS9_Hotfix_KB913090_sqlrun_rs.msp.log.
The account running SQL server setup has admin privileges on that box.
Kindly help me in this regard.
Thanks.
Birendra
On my laptop I've got SQL2005 developper edition SP1 with 3 SSIS-jobs scheduled through SQL-agent.
These 3 SSIS-jobs are in fact maintenance plans which are also used on our production SQLServers.
These take backups (full, transactional), Cleanup old backups, reorganize indexes, update stats ...
One of these jobs runs every hour to take transaction logbackups. After installing SP2 this started failing.
When I opened the sources of that job in visual studio It seemed like the unit of thime was changed for cleanup jobs fe cleanup bak-files after 4 days changed into after 4 hours. The backup task for transactional backups which had the property to do that for all databases whas changed into specific databases which no database selected.
Even when I changed that into All databases and saved it, when I opened that backup task again, this was changed back into specific databases with no database selected.
I uninstalled SQL2005 and reinstalled it, including SP1 and everything works well again.
Does anyone know how to solve this.
I'm building an SQL Server 2005 cluster on a Windows 2003 cluster. Windows 2003 cluster and MSDTC service are all up and running properly. No problems there, but when I try to install SQL Server 2005 as a cluster service, it fails. The installation goes past the stage where it validates both the nodes and doesn't find any issue there, but when it tries to install fiels it fails. It fails on node 2. When I checked the scduled installer job it creates on node2 to install, the job never seems to run and fails. I'm using only one user account to setup windows cluster MSDTC and SQL Server. Now the complications: It is 64 bit Windows 2003 and SQL Server 2005. Also, the node 1 is built to be a domain controller as well.
Any help will be highly appreciated.
We have successfully been using MSCS with MSSQL7 (SP1) running under NT4 EE
(SP6a), installed in an active/active configuration using, two DELL
PowerEdge 6350 machines. Recently I installed MSSQL7 (SP2), I followed the
instructions that came with SP2, and unclustered the SQL nodes using the
Failover Cluster Wizard, and installed SP2, this was uneventful, and
appeared to install correctly. Next I tried to recluster the SQL nodes
using the Failover Cluster Wizard as directed. This failed with: "Could not
run setup on remote machine. SQL Cluster Setup failed." So I began the
usual research using the usual resources, and have found articles that
discusses this error, and the things to look for when it happens. I have
exhausted all suggestions without success. I appear to have everything
correctly configured. I have enabled Cluster Logging (level 3), following
are the two things I have found that indicate something is wrong:
1. In the SQL Error Log the following gets logged when I run the wizard:
"Attempting to initialize Distributed Transaction Coordinator."
"Failed to obtain TransactionDispenserInterface:
XACT_E_TMNOTAVAILABLE"
2. In the Cluster Log I see the following message repeatedly:
"[ClRtlCopySecurityDescriptor] MakeSelfRelativeSD failed,
0x00000551"
3. In the sqlclstr.log I see the following, without an indication of
which file is missing:
"[reghelp.h:235] : 2 (0x2): The system cannot find the file
specified."
"[clushelp.cpp:166] : 259 (0x103): No more data is available."
"[validate.cpp:147] DeleteTestGroup:OpenClusterResource: 5007
(0x138f): The cluster resource could not be found."
"~~~ XXX InstallRemote failed"
Does anyone have any ideas about what could be causing this problem?
Many thanks in advance.
Christpher Cutts
LifeMasters Supported SelfCare
For some reason when ever try to install SQL Server 2005 the install fails on MSXML6.
I get the following log file, can anyone make any sense of this.
=== Verbose logging started: 30/08/2007 22:16:00 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe ===
MSI (c) (84:10) [22:16:00:859]: Resetting cached policy values
MSI (c) (84:10) [22:16:00:859]: Machine policy value 'Debug' is 0
MSI (c) (84:10) [22:16:00:859]: ******* RunEngine:
******* Product: {AEB9948B-4FF2-47C9-990E-47014492A0FE}
******* Action:
******* CommandLine: **********
MSI (c) (84:10) [22:16:00:859]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (84:10) [22:16:00:859]: Grabbed execution mutex.
MSI (c) (84:10) [22:16:00:859]: Cloaking enabled.
MSI (c) (84:10) [22:16:00:859]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (84:10) [22:16:00:859]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (40:88) [22:16:00:859]: Grabbed execution mutex.
MSI (s) (40:58) [22:16:00:859]: Resetting cached policy values
MSI (s) (40:58) [22:16:00:859]: Machine policy value 'Debug' is 0
MSI (s) (40:58) [22:16:00:859]: ******* RunEngine:
******* Product: {AEB9948B-4FF2-47C9-990E-47014492A0FE}
******* Action:
******* CommandLine: **********
MSI (s) (40:58) [22:16:00:859]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (40:58) [22:16:00:859]: MainEngineThread is returning 1605
MSI (c) (84:10) [22:16:00:859]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (84:10) [22:16:00:859]: MainEngineThread is returning 1605
=== Verbose logging stopped: 30/08/2007 22:16:00 ===
I can't seem to get all of the SQL9_Hotfix_KB913090_sqlrun_sql.msp.log to post (too big), but I can post the SQL9_Hotfix_KB913090.log file...hope that helps and which seems to me might contain the clue as to what's going. Any ideas would be appreciated. This is happening on a fresh install of Win Server 2003 and SQL Server standard 2005.
Thanks,
Steve
04/09/2007 16:14:30.562 ================================================================================
04/09/2007 16:14:30.578 Hotfix package launched
04/09/2007 16:14:33.312 Product discovery successfully completed during the install process for MSSQLSERVER
04/09/2007 16:14:33.328 SP Level check successfully completed during the install process for MSSQLSERVER
04/09/2007 16:14:33.359 Product language check successfully completed during the install process for MSSQLSERVER
04/09/2007 16:14:33.390 Product version check successfully completed during the install process for MSSQLSERVER
04/09/2007 16:14:33.421 Command-line instance name check completed during the install process
04/09/2007 16:14:33.437 Baseline build check completed during the install process
04/09/2007 16:16:52.828 Attempting to install instance: MSSQLSERVER
04/09/2007 16:16:52.875 Attempting to install target: TURBULENT2
04/09/2007 16:16:53.015 Attempting to stop service: SQLSERVERAGENT
04/09/2007 16:16:58.171 Successfully stopped service: SQLSERVERAGENT
04/09/2007 16:16:58.203 Attempting to stop service: MSSQLServer
04/09/2007 16:17:00.250 Successfully stopped service: MSSQLServer
04/09/2007 16:17:00.281 Attempting to check for locked files: sqlrun_sql.msp
04/09/2007 16:17:00.468 Attempting to check for locked files: \TURBULENT2f$9104ddf6956f8b22663aHotFixSQLFilessqlrun_sql.msp
04/09/2007 16:17:00.500 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out
04/09/2007 16:17:38.125 MSP returned 1602: The user cancels installation.
04/09/2007 16:17:38.328 Successfully checked file: \TURBULENT2f$9104ddf6956f8b22663aHotFixSQLFilessqlrun_sql.msp
04/09/2007 16:17:38.359 Successfully opened registry key: SystemCurrentControlSetControlSession Manager
04/09/2007 16:17:38.421 Failed to read registry key: PendingFileRenameOperations
04/09/2007 16:17:38.468 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll
04/09/2007 16:17:38.515 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll
04/09/2007 16:17:38.562 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll
04/09/2007 16:17:38.609 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll
04/09/2007 16:17:38.687 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnlhtml.dll
04/09/2007 16:17:38.734 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll
04/09/2007 16:17:38.765 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe
04/09/2007 16:17:38.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll
04/09/2007 16:17:38.843 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe
04/09/2007 16:17:38.875 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll
04/09/2007 16:17:38.890 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll
04/09/2007 16:17:38.921 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll
04/09/2007 16:17:38.937 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll
04/09/2007 16:17:38.968 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll
04/09/2007 16:17:39.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL
04/09/2007 16:17:39.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll
04/09/2007 16:17:39.046 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll
04/09/2007 16:17:39.062 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
eplrec.dll
04/09/2007 16:17:39.093 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
plisapi.dll
04/09/2007 16:17:39.156 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:WINDOWSassemblyGAC_32Microsoft.SqlServer.Replication9.0.242.0__89845dcd8080cc91Repl.dll
04/09/2007 16:17:39.171 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll
04/09/2007 16:17:39.203 Failed to read version information for the following file: C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources10332005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
plhtfin.sql
04/09/2007 16:17:39.218 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe
04/09/2007 16:17:39.250 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMsnapshot.exe
04/09/2007 16:17:39.281 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
eplmerg.exe
04/09/2007 16:17:39.296 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90COM ablediff.exe
04/09/2007 16:17:39.328 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe
04/09/2007 16:17:39.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe
04/09/2007 16:17:39.390 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources30822005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources2052sqlevn70.rll
04/09/2007 16:17:39.406 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10422005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1041sqlevn70.rll
04/09/2007 16:17:39.437 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10402005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1036sqlevn70.rll
04/09/2007 16:17:39.453 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10332005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1031sqlevn70.rll
04/09/2007 16:17:39.484 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10282005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033XPStar90.RLL
04/09/2007 16:17:39.515 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
04/09/2007 16:17:39.531 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
04/09/2007 16:17:39.562 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
04/09/2007 16:17:39.578 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn6.6.3.5
C:Program FilesMicrosoft SQL Server90Sharedmsxmlsql.dll
04/09/2007 16:17:39.609 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2.0.3609.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlrw.dll
04/09/2007 16:17:39.640 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
04/09/2007 16:17:39.656 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
04/09/2007 16:17:39.687 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
04/09/2007 16:17:39.703 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLBOOT.dll
04/09/2007 16:17:39.734 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxplog70.dll
04/09/2007 16:17:39.765 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnatchp~1.dll
04/09/2007 16:17:39.796 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
04/09/2007 16:17:39.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
04/09/2007 16:17:39.843 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
04/09/2007 16:17:39.875 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
04/09/2007 16:17:39.906 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
04/09/2007 16:17:39.921 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
04/09/2007 16:17:39.953 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
04/09/2007 16:17:39.984 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
04/09/2007 16:17:40.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
04/09/2007 16:17:40.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
04/09/2007 16:17:40.062 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
04/09/2007 16:17:40.078 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
04/09/2007 16:17:40.140 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90SharedResources10339.0.2047.0
C:Program FilesMicrosoft SQL Server90Sharedmsmdrdir.dll
04/09/2007 16:17:40.156 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0
C:Program FilesCommon FilesSystemole dbxmlrw.dll
04/09/2007 16:17:40.171 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
04/09/2007 16:17:40.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
04/09/2007 16:17:40.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
04/09/2007 16:17:40.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
04/09/2007 16:17:40.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
04/09/2007 16:17:40.296 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
04/09/2007 16:17:40.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
04/09/2007 16:17:40.328 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
04/09/2007 16:17:40.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
04/09/2007 16:17:40.375 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml
04/09/2007 16:17:40.390 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll
04/09/2007 16:17:40.421 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll
04/09/2007 16:17:40.437 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033
C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml
04/09/2007 16:17:40.453 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
04/09/2007 16:17:40.484 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
04/09/2007 16:17:40.500 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
04/09/2007 16:17:40.515 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
04/09/2007 16:17:40.531 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
04/09/2007 16:17:40.546 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
04/09/2007 16:17:40.578 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
04/09/2007 16:17:40.593 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
04/09/2007 16:17:40.609 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
04/09/2007 16:17:40.625 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstallsysdbupg.sql
04/09/2007 16:17:40.656 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL
04/09/2007 16:17:40.671 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL
04/09/2007 16:17:40.687 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL
04/09/2007 16:17:40.703 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0
C:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe
04/09/2007 16:17:40.718 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0
C:Program FilesMicrosoft SQL Server90Sharedsqlsvc~1.dll
04/09/2007 16:17:40.765 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
04/09/2007 16:17:40.781 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
04/09/2007 16:17:40.796 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
04/09/2007 16:17:40.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
04/09/2007 16:17:40.843 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
04/09/2007 16:17:40.875 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
04/09/2007 16:17:40.890 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
04/09/2007 16:17:40.906 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
04/09/2007 16:17:40.937 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
04/09/2007 16:17:40.968 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
04/09/2007 16:17:40.984 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
04/09/2007 16:17:41.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
04/09/2007 16:17:41.015 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0
C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe
04/09/2007 16:17:41.046 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0
C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll
04/09/2007 16:17:41.062 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
04/09/2007 16:17:41.125 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
04/09/2007 16:17:41.171 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
04/09/2007 16:17:41.203 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll
04/09/2007 16:17:41.234 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL
04/09/2007 16:17:41.250 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL
04/09/2007 16:17:41.265 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll
04/09/2007 16:17:41.281 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
04/09/2007 16:17:41.312 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
04/09/2007 16:17:41.328 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
04/09/2007 16:17:41.359 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll
04/09/2007 16:17:41.375 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll
04/09/2007 16:17:41.406 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll
04/09/2007 16:17:41.421 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll
04/09/2007 16:17:41.453 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll
04/09/2007 16:17:41.484 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlSAC.exe
04/09/2007 16:17:41.515 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedMicrosoft.SqlSac.Public.dll
04/09/2007 16:17:41.687 Attempting to install file: sqlrun_sql.msp
04/09/2007 16:17:41.750 Attempting to install file: \TURBULENT2f$9104ddf6956f8b22663aHotFixSQLFilessqlrun_sql.msp
04/09/2007 16:17:41.765 Creating MSP install log file at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log
04/09/2007 16:17:41.796 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
04/09/2007 16:17:41.812 Failed to read registry key: Debug
04/09/2007 16:19:50.187 MSP returned 1603: A fatal error occurred during installation.
04/09/2007 16:19:50.250 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
04/09/2007 16:19:50.265 Failed to read registry key: Debug
04/09/2007 16:19:50.296 Unable to install MSP file: \TURBULENT2f$9104ddf6956f8b22663aHotFixSQLFilessqlrun_sql.msp
04/09/2007 16:19:50.312 The following exception occurred: Unable to install Windows Installer MSP file Date: 04/09/2007 16:19:50.312 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 856
04/09/2007 16:19:50.437
04/09/2007 16:19:50.468 Product Status Summary:
04/09/2007 16:19:50.500 Product: SQL Server Native Client
04/09/2007 16:19:50.546 SQL Server Native Client (RTM ) - Success
04/09/2007 16:19:50.578
04/09/2007 16:19:50.609 Product: Setup Support Files
04/09/2007 16:19:50.640 Setup Support Files (RTM ) - Success
04/09/2007 16:19:50.656
04/09/2007 16:19:50.687 Product: Database Services
04/09/2007 16:19:50.734 Database Services (SP1 2047 ENU) - Failure
04/09/2007 16:19:50.750 Details: Unable to install Windows Installer MSP file
04/09/2007 16:19:50.781 Reporting Services (SP1 2047 ENU) - Not Applied
04/09/2007 16:19:50.812
04/09/2007 16:19:50.843 Product: Client Components
04/09/2007 16:19:50.890 Client Components (SP1 2047 ENU) - Not Selected
04/09/2007 16:19:50.921
04/09/2007 16:19:50.953 Product: MSXML 6.0 Parser
04/09/2007 16:19:50.968 MSXML 6.0 Parser (RTM ) - Not Selected
04/09/2007 16:19:51.015
04/09/2007 16:19:51.046 Product: SQLXML4
04/09/2007 16:19:51.078 SQLXML4 (RTM ) - Not Selected
04/09/2007 16:19:51.109
04/09/2007 16:19:51.125 Product: Backward Compatibility
04/09/2007 16:19:51.140 Backward Compatibility (RTM ) - Not Selected
04/09/2007 16:19:51.171
04/09/2007 16:19:51.203 Product: Microsoft SQL Server VSS Writer
04/09/2007 16:19:51.265 Microsoft SQL Server VSS Writer (RTM ) - Not Selected
04/09/2007 16:19:51.296
04/09/2007 16:29:32.812 Hotfix package closed
I just upgraded ACT database and it needs SQL Server. I just keep getting "SQL Server Setup Failed". I downloaded SQL from Microsoft, went to install and get the same error. It then refers to a summary txt log which I have had a look at but to be quite honest means nothing to me.
I only want to be able to use ACT!!
Anyone help PLEASE!!
SQL Server 7.0
Whenever I attempt to create a new table, or modify an existing one, I get a Dr. Watson, c0000005 (access violation) error.
Any thoughts?
I'm trying to use bcp to move a table into SQL Server 6.5. The command I am using is bcp CCI..contacts in A:Contacts.txt -fC:contacts.fmt -Usa -P -eC:errors.txt. When executing, I receive the Dr. Watson error message shown here:
Exception: access violation (0xc0000005), Address: 0x77f64d28
If I run DRWTSN32.log it shows the application error to be the following:
c0000005 RtlFreeHeap(77f64d28)
Any ideas why??
I have a Windows 2003 Server SP1, Active Directory, Application Server and RIS installed on my computer. After installing SQL Server 2005 April CTP my DHCP Service fails to start. In the Event Viewer I see the following Events.
View 20 Replies View Related
Hi, pls can anyone help me out with this? I'm installing SQL2005 SP2 over an Itanium machine with W2003 SP2 but it keeps on failing on those features. Client components got installed with no problems. I've installed SQL2005-SP2 over x86 and x64 (not Itanium) machines many times before successfuly. I've been investigating this issue for several days with no luck so I'm a bit clueless at the moment. As I'm using Administrator account I think it is not file permission related.
Summary says "Unable to install Windows Installer MSP file".
let me know if further info is nedeed.
Many thanks.
Anyone experience Dr Watson's on MS Cluster Server? This is the second time that it's happened and I can't explian it.
The first time it happened it appeared to stop the virtual server service on my prod server, Cluster admin showed it as running.
This time it bounced the engine but nothing stopped.
Any clue is much appreciated, because I don't have one
I'm at SP5 on NT4 and SP2 on SQL 7 EE.
Pete
Hello:
We have, on a devlopment server, running a long_running transaction for
almost two days. It was still running. This morning I decided to look at
three of two backup devices under EM to see if any backups were made to
these devices during the last couple of days on a de,mand basis by anyone.
The first one had a backup and the second and third device did not.
Somehow, and for some unexplained reason, the following message was put
into the MSSQL error log (and pretty much the same message went into the NT
event viewer).
----------------------------------------------------------------------
99/02/23 10:05:45.81 kernel dbsvolopen: Backup device
'E:MSSQLBACKUPEaglePro2_run02.DAT' failed to open, operating system
error = 2(The system cannot find the file specified.)
99/02/23 10:05:48.48 kernel dbsvolopen: Backup device
'E:MSSQLBACKUPEaglePro2_run02.DAT' failed to open, operating system
error = 2(The system cannot find the file specified.)
99/02/23 10:05:49.17 kernel dbsvolopen: Backup device
'E:MSSQLBACKUPEaglePro2_run03.DAT' failed to open, operating system
error = 2(The system cannot find the file specified.)
---------------------------------------------------------------------
This error, I beleive, caused DR watson to kick off and we could only sopt
it and revive the long running transaction by rebooting the machine, of
course thus requiring us to restart the lon_running transaction.
It look like NT couldn't find the backup device and therefore activated the
drwatson executible or so it seems to me.
Has anyone experienced this error before? IS it caused by NT? Or that
perhaps a certain threshhold was reacched on NT and drwatson kicked in?Any
other ideas?
Any information that can be provided would be GREATLY appreciated. THanks.
David Spaisman
I'm currently receiving the following error message whilst attempting to install SQL Server 2005 Standard Edition on Windows Server 2003 (32 Bit):
Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.
This server already has an install of SQL Server 2000 as the default instance. I'm attempting to install a new named instance of SQL Server 2005.
Extract from log:
<Func Name='LaunchFunction'>
Function=Do_sqlPerfmon2
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_sqlPerfmon2
PerfTime Start: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
<Func Name='Do_sqlPerfmon2'>
<EndFunc Name='Do_sqlPerfmon2' Return='0' GetLastError='2'>
PerfTime Stop: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
MSI (s) (4C:FC) [10:20:02:833]: Executing op: ActionStart(Name=Rollback_Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Removing performance counters,)
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (4C:FC) [10:20:02:849]: Executing op: CustomActionSchedule(Action=Rollback_Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1281,Source=BinaryData,Target=Rollback_Do_sqlPerfmon2,CustomActionData=100Removing performance counters200000DTSPipelineC:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.INI)
MSI (s) (4C:FC) [10:20:02:849]: Executing op: ActionStart(Name=Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Installing performance counters,)
MSI (s) (4C:FC) [10:20:02:849]: Executing op: CustomActionSchedule(Action=Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1025,Source=BinaryData,Target=Do_sqlPerfmon2,CustomActionData=100Installing performance counters200000C:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.INIC:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.HC:Program FilesMicrosoft SQL Server90DTSBinnDTSPipelinePerf.dllDTSPipeline0DTSPipelinePrfData_OpenPrfData_CollectPrfData_Close)
MSI (s) (4C:94) [10:20:02:864]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI1683.tmp, Entrypoint: Do_sqlPerfmon2
<Func Name='LaunchFunction'>
Function=Do_sqlPerfmon2
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_sqlPerfmon2
PerfTime Start: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
<Func Name='Do_sqlPerfmon2'>
<EndFunc Name='Do_sqlPerfmon2' Return='2' GetLastError='2'>
PerfTime Stop: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
Gathering darwin properties for failure handling.
Error Code: 2
MSI (s) (4C!F0) [10:23:46:381]: Product: Microsoft SQL Server 2005 Integration Services -- Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.
You can ignore this and it will complete the installation, but subsequently trying to patch with SP2 will fail on the same sections - Hotfix.exe crashes whilst attempting to patch Database Services, Integration Services and Client Components (3 separate crashes).
I've removed SQL Server 2005 elements and tried to re-install, but it's not improved the situation.
Any ideas?
Got the following message while trying to apply sp5a:
"Setup initialization could not be successfully completed.
ISQL.EXE could not be executed. Please check the relevant .OUT file."
And yes, i did check the readme file, but found no problem in the PATH variable.
(unless I'm looking at it wrong!)
Please help!
I am trying to apply SQL Server Service Pack 5a to my original SQL
Server 6.5 but an error keeps coming up "Setup initialization could not
be successfully executed. ISQL,EXE could not be executed.Pls check
relevant .out file".
The last line of the relevant .out file produced by this error is:
You cannot run SELECT INTO this database. The DBO would have to run
sp_dboption to enable this option.
Msg 208, Level 16, State 1, Server REYWINNT, Procedure sp_helpsort, Line
295
I would appreciate any help to solve my problem
Thanks a lot
Rey Caunca
I have a third party app that has been 'certified' by the vendor on SQL 6.5 SP5. We are aware of the dump database issues when using SP5 and Enterprise Manager. We would like to use SP5a to get around those issues.
Is anyone aware of any other 'bugs' or problems that have come about in SP5a....
Thanks tons!
Dean
Is there a proper order to installing SQL SP5a. Should you reinstall NT SP4 after you install
the SQL SP5a?
I've got a script that runs regularly to monitor log space usage on a SQL 6.5 sp5a server. Where the log space usage is greater than 75% it then dumps the log. However the Enterprise Manager screen still shows usage as being above 75%. I'm aware that I need to run dbcc checktable(syslogs) to have EM reflect the change, and my question is:
Within my sql script how do I switch context to the database where I need to run the dbcc checktable(syslogs) command?
I currently have SP5 in a folder on the server desktop. MSSQL Server is installed on drive E:
Running setup, it finds SQL Server and shuts it down. It then returns errors about not being able to find files, though the files are actually there.
I appologize for the brain-cramps, as I know this has been discussed before, but I need HELP ASAP.
Thanks
Steve Jimmo
I run replication among several SQL 6.5 Servers with SP3. Recently,
I've applied SP5a to publisher/distributor. After that, some publications
continued to replicate normally, but two of them started to act strangely -
the distribution tasks end succesfully, but it seems that no transactions
were marked for replication.
After investigating a bit, I've found that the data that continued to
replicate normally is modified by stored procedures, while problematic
tables are updated directly. Then I've tried to run isql/w updates against
problematic tables - all the changes were succesfully applied to the
subscribers. The other difference between problematic and non-problematic
tables is their size - problematic tables are much bigger and more
frequently updated.
All the subscribers are still SQL 6.5 Servers with SP3. One of them
is also a publisher that uses SP5a-upgraded SQL Server as remote
distributor. Its publications replicate OK.
I'd appreciate any explanation of the above.
Thanks
Maja
I've installed SQL Server Service pack 5a on our test lab Database and have come up with problems with my protocol. Everything works fine IF I set the Net Library to Named pipes. But before the service patch, I was running Multi-Protocol WITH TCP/IP (much faster). How can I make SQL use Multi?
Using Named pipes screws up my replication. Any suggestions???
Thanks,
Andrew
P.S. I also have SP4 on WindowsNT.
HELP!!!!!!!!!!!!!!!!!!
I loaded SQL SP5a last night on my SQL Server and now none of my users can connect and run their applications.
I removed the virtual server and loaded the sp without any problems (so it seemed). "sa" works fine.
I am getting login failed errors:
Sql State 28000 and Sql Server 4002
Any thougts, ideas, curses would be GREATLY APPRECIATED!!!!!!!!!!!!
Hi:
I installed SQL sp5a on most SQL servers with no error. However, one server, a special application failed after upgrading to sp5a.
Is there a way to uninstall sp5a and back to sp3 without re-install entire SQL 6.5 on this particular machine?
thanks in advance
david
I am having problems with stack dumps (as many as 12 a day) at a production site running NT 4.0 SP4 with Sql Server 6.5 SP5A. I've tried running every diagnostic utility on the server but it shows no problems. Before I open a ticket with Microsoft on the stack dumps, I'd like to upgrade the server to NT Service Pack 6A. My question is, do I need to re-install SqlServer SP5A? Will the NT Service Pack 6A invalidate SQL SP5A?
TIA,
Mike
Hi all,
I recently upgraded to SQL 6.5- sp5a. I run DBCC TEXTALL as part of my nightly maintenance. Our db is about 3 GB and is heavy on text
fields. Since the upgrade, DBCC TEXTALL hangs up the server until I reboot it. The last message in the error log is "Warning:
out of RA slots... comfigure more RA slots." (or something like that). This never happened before.
BOL says don't monkey with the RA slots per thread, so
I've been adjusting the number of RA worker threads. I raise it, bounce SQL SERVER, and try to run the DBCC TEXTALL again.
Same results. Eventually I got up to 10 RA worker threads, at which point I got an "IO buf_wait" error, which also hung up the server.
I've read that increasing RA worker threads will eventually run you out of buffer space, and it looks like that's what happened.
I'm beginning to think that the problem isn't really with isn't really with the number of RA worker threads I have configured,
but rather with something that sp5a changed. Or maybe DBCC TEXTALL is running into some sort of corruption it can't handle...
Or something...
So, I'm reading up on the relationship between buffer cache, RA, etc., but
the sad fact is that information on that low down level is hard to find, and I don't understand most of it anyway.
Any suggestions, reading recommendations, comments, or jeers would be highly appreciated.