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
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 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
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
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.
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
When running Enterprise Manager from my desktop pc to try and expand a database device I am unable to do so. The size shown is negative, and the max size is the same, with the 'Change Now' box greyed out.
When I log on directly onto the server I can easily expand the db device. There is lots of free space on the server.
Our set up is quite small with four NT workstations and two NT servers with SQL Server 6.5 on them. All these six machines are in the same workgroup. The workstations are on a separate floor to the servers, which are in the computer room. I have a feeling this is a networking issue. Can anyone suggest why this is happening?
Hi,
Has anyone encountered this?
After applying SP 5a I found out that my SQL strings with sums and groups produced double rows. I found out that grouping one column (type CHAR(6)) produced two distinct rows of the equal values.
All the values in that column have 4 characters, but it seemed like some distinct values were grouped by the whole field length i.e 6 characters. I haven't seen earlier that those blanks after field value change the grouping results.
When I transferred the table and data to old SQL Server without any SPs, query showed distinct values correctly.
The sort order and other settings are the same. Can anyone tell where to look for help?
TIA, Al
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
Has anyone gotten clustering to work via the Cluster Wizard in SP5a?
I've got two ProLiant 5500's with the Compaq Clustering S/100 option. I've done a fresh install of NT Enterprise 4.0 SP3, then installed clustering with the Compaq S/100 drivers... everything fails over nicely, can make shares off the virtual server, etc. I then install SQL Server 6.5 EE, then apply SP5a -- so far, so good.
Now I try to run the clustering wizard. The wiz prompts me for my SA password. I enter it, and it gives me a message box that it can't start or log onto the database... but when I look in the event log it appears to have logged on successfully with a Non-trusted connection.
Thanks for the help...
Hello,
Just in case anybody has had this problem after applying service pack 5a.
a stored procedure that sets serial numbers on records on a temporary table is skipping every other record.
I ran the code manually on isql and could not replicate the error, however when re-compiled on stored procedure it fails misserably.
when is Microsoft going to release a service pack that actually works?
Did you know that Executive does not recognize 2000 as a leap year?
If anybody has any suggestions on this problem, besides the obvious (using a real table) please write back
thanks.
David E. Pierri
Pseudo data-admin
ACNY
When attemping to install SQL 2005 Express using the following command line arguments
/qb UPGRADE=SQL_Engine INSTANCENAME=MY_INSTANCE
or
/qb UPGRADE=SQL_Engine INSTANCENAME=MY_INSTANCE SECURITYMODE=SQL SAPWD=MY_PASSWORD
the following error occurs.
Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Edition check:
Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
The following version and editions have been verified.
1. .NET 2.0 installed
2. Windows XP SP2
3. MSDE 8.00.2039(SP4)
4. all MSDE databases are owned by sa
5. Instance and SQLAgent running under user that is member of Administrators
What are the possible reasons this error is occurring?
We have a server instance on SQL Server 2005 SP2 build 3042. We have a 32 bit x86 server. We attempted to upgrade to SP2 build 3054 KB934458. And we got the following error as stated in the Summary.txt file.
Code Snippet
**********************************************************************************
Product Installation Status
Product : SQL Server Database Services 2005 (MSSQLSERVER)
Product Version (Previous): 3042
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB934458_sqlrun_sql.msp.log
Error Number : 29538
Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: e:SQLDatamssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
----------------------------------------------------------------------------------
The client tools and workstation components were successfully installed. The server is still reporting build 3042.
Here is the portions of the HotFix.log file.
Code Snippet
05/12/2008 09:19:09.041 Copy Engine: Creating MSP install log file at: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB934458_sqlrun_sql.msp.log
05/12/2008 09:19:09.072 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
05/12/2008 09:19:09.103 Registry: Cannot read registry key value "Debug"
05/12/2008 09:21:29.382 MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: e:SQLDatamssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
05/12/2008 09:22:33.678 MSP returned 1603: A fatal error occurred during installation.
05/12/2008 09:22:33.724 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
Any help would be appreciated.
Hi,
We are performing a SQL 2005 SP1 upgrade from SQL 2000 on our Windows 2003 SP1 Standard Edition.
When we run the upgrade, we got a error "Upgrade Advisor Return -1" as a pop-up window.
When we run the Upgrade Advisor separately, we get this error :
===================================
Common Language Runtime detected an invalid program.
===================================
Common Language Runtime detected an invalid program. (System.Xml)
------------------------------
Program Location:
at System.Xml.Schema.SchemaInfo..ctor()
at System.Xml.Schema.XmlSchemaSet..ctor(XmlNameTable nameTable)
at System.Xml.XmlReaderSettings.get_Schemas()
at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAReportController.LoadAndValidateDataFile()
at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAReport.ValidateDataFile()
at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAIssueReport.Refresh()
at Microsoft.SqlServer.UpgradeAdvisor.ReportPanel.OpenReport(String reportFile)
We are in a lost for solutions. We do hope to hear from anyone asap...
Greatly appreciated for any kind assistance.
Thanks.
Hi,
We are running a test upgrade form sql 2000 standard edition 32 bit to sql 2005 developer edition 32bit. Followed through all the steps and specified the account(SA priveleges and currently used by the 2000 version) and is the local admin on the box for the services and the setup seemed to move fine, except for when it got to the point of installing database services - This is the error message that I got:
MSSQLServer could not be started. Verify you have sufficient priveleges to start system services. The was no choice but to hit cancel and then the set up progressed with a final message of 'SEtup failed'.
Here is a portion of the error log:
Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
Database Mirroring Transport is disabled in the endpoint configuration.
Starting up database 'master'.
Converting database 'master' from version 589 to the current version 611.
Database 'master' running the upgrade step from version 589 to version 590.
Error: 946, Severity: 14, State: 1.
Cannot open database 'master' version 589. Upgrade the database to the latest version.
System Task Aggregate global counters produced an error that was not handled. Major: 9, Minor: 46, Severity:14, State:1
Error: 928, Severity: 20, State: 1.
During upgrade, database raised exception 15151, severity 16, state 1, address 01C4C50B. Use the exception number to determine the cause.
Error: 15151, Severity: 16, State: 1.
Cannot find the endpoint 'TSQL Local Machine', because it does not exist or you do not have permission.
Any help would be greatly appreciated
Thanks KR
Greetings,
I have a client whose DBA upgraded their SQL 2000 database to SQL 2005. They still have it running in 8.0 compatibility mode, for various reasons, and would like me to help them develop a migration strategy to get them to full 9.0 compatibility.
My question is: can I run the Upgrade Advisor on a SQL 2005 engine database running in 8.0 compatibility mode and get anything useful? I already know there will be some issues with existing DTS packages but it would be nice to catch any other issues in advance.
I know that the Upgrade Advisor was run before the upgrade took place but to my knowledge the report was not saved and none of the recommendations were followed.
Any help would be greatly appreciated.
Cheers,
Lon
SQL 2000 -> SQL 2005 upgrade on windows server 2003 ... We've done numerous side by side types of upgrades which have the advantages of being able to migrate things at a slower pace with limited downtime. I have a situation where it seems like it would be the least amount of work to do an in place upgrade involving 22 transactional in-house developed databases and associated in-house developed applications. There's no replication, no DTS packages, nothing I can think of that would complicate the upgrade. I was wondering if there's people out there that have done lots of these and haven't had any problems OR if there have been lots of problems. Anyway, any advice would be appreciated.
John
Hi,
I plan to move my servers from Windows NT and SQL 7 to Win2K Advanced Server and SQL 2000. I am not going to upgrade the windows server, as I have been told this isn't a good thing. Therefore, I plan to detach my databases, install win2K, install SQL 2000, and then attach the databases. I've read that this works fine, but I am curious as to whether or not I can do this with master and msdb(as I want to keep all logins, jobs, etc). Is this possible? Also, is my plan decent? it seems to be the easiest way to me...
Thanks!
Hi All,
I am upgrading sql 6.5 to 7.0. The 6.5 database has 3 data files. Do I need to create 3 datafiles in version 7.0 after the server has been upgraded? Before I do the upgrade on the production server, I want to do a test on another machine loaded with sql 6.5, Do I need create 3 data files on 6.5 to to load the database from the production server before I upgrade the test machine to sql 7.0?
Thanks in advance,
Jason
I get this error when I try to run a query. I just upgraded to SQL 7.0
ERROR connecting to local server ...
Error Number Error Text
0x8004D903 [SQL Server] You must upgrade your SQL Enterprise Manager and SQL-DMO (SQLOLE) to version 7.0 (SQLDMO) to connect to this server.
Thanks
I HAVE AN NT 4 SERVER WITH SQL 7. WHAT WOULD BE THE PROPER STEPS TO
UPAGRADE THAT AS A WINDOWS 2000 SERVER WITH SQL 2000.
SHOULD I UP THE OS FIRST ?? ETC
ANY INPUT IS MUCH APPRECIATED.
-MIKE
When I upgraded my server from SQL-6.5 (service pack 5a) to SQL-7.0, I got an error message like this :
<<
Error:
Microsoft SQL-DMO (ODBC SQLState: 42000) returned error: [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near 'where'.
The replication upgrade task was not able to completely transfer your existing replication configuration settings to 7.0 server. Following the completion of upgrade, it is recommended that you use the Microsoft Management Console in Sphinx to re-establis>>
Has any one come across this ? The existing setup is using the transaction replication with 5 other servers. In 6.5, it is functioning well.
Rgds
Armstrong
I have an NT4 SQL7 server ( no clustering, replication ) and planning to get that to W2K SQL 2000. What would the best and safe to do that ?
Sharing your ideas is much appreciated. Pls. give details.
Thanks,
Mark
I need to upgrade an NT4/SQL 7 sever to Win2000/SQL 2000.
What would be the effient way doing this ?
Any ideas are appreciated.
Thanks,
Hi everybody,
I am using SQL Server 7.0 with SP2 and I want to upgrade it to SP3. If anybody has done this please share your experiences on wha problems were faced while installing SP3 and wheather it is safe to upgrade or not.