SQL7 Upgrade Error/Problem (syscomments)
Jul 14, 1999
I have a SQL6.5 sp5a, NT4 sp5, BDC, IE5 server that I have installed SQL7
on. My installation is set to mixed security.
Everytime I try to run the upgrade wizard I get the following error/problem
right after the "Checking 6.x syscomments for corruption and Verifying 6.x
data base logins etc.
Summary of warnings (if any) and choices:
=============================================
The following syscomments entries are invalid on your 6.x SQL Server. It is
recommended that you fix these problems before you continue.
=============================================
********************************
master
********************************
********************************
Inconsistency Report For Database: master.
********************************
dbo.sp_db_upgrade2
Procedure
Occurs 28 times
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system
catalogs not enabled. System Administrator must reconfigure system to allow
this.
--------------------------------
dbo.sp_fallback_activate_svr_db
Procedure
Occurs three times
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system
catalogs not enabled. System Administrator must reconfigure system to allow
this.
--------------------------------
dbo.sp_password
Procedure
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system
catalogs not enabled. System Administrator must reconfigure system to allow
this.
--------------------------------
dbo.sp_recompile
Procedure
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system
catalogs not enabled. System Administrator must reconfigure system to allow
this.
--------------------------------
dbo.sp_rename
Procedure
Occurs 11 times
[Microsoft][ODBC SQL Server Driver][SQL Server]Ad-hoc updates to system
catalogs not enabled. System Administrator must reconfigure system to allow
this.
--------------------------------
=============================================
The following script will be created as upgrade.ini and run into the script
interpreter when you press finish.
=============================================
[Options]
Method=1
Perform a CRC Check=0
Source=CCIDEV
Destination=CCIDEV
Export Server Startup Options=
Import Server Startup Options= -T1808
SQLServer70Path=C:MSSQL7SourcePassword=066ce2f9c0e 4ba
DestinationPassword=00
MasterPath=C:MSSQLDATAMASTER.DAT
VerswitchOldVer=65
Code Page=1252
Override Server Code Page=0
QuotedIdentifiers=0
ObjectDumpPath=c:mssql7upgradeCCIDEV_071399_163117 Ansi Nulls=0
[Tasks]
Export and Import via Named Pipe=0
Marking database upgrade status=0
Export Logins=0
Export Database Owners=0
Import Logins=0
Creating Databases=0
Setting Database Options=0
Export Database Objects=0
Import Database Objects=0
Export SQL Executive Settings=0
Preparing MSDB for Upgrade=0
Import SQL Executive Settings=0
Export Server Settings from Master=0
Modifying Scripts=0
Import Server Settings from Master=0
Preparing SQL-DMO for upgrade=0
[Databases]
006CCIDATA=0
003model=0
005msdb=0
001master=0
I don't find anything about this anywhere except the upgrading to SQL7 white
paper, it mentions that the text for objects must be intact in the
syscomments system table and that logins must exist for every database user,
but that doesn't really tell me how to fix this.
Has any one seen these errors or can point me
to where on Microsoft's site you can now EASILY get KB info for SQL Server
7?
View 2 Replies
ADVERTISEMENT
Oct 12, 2001
I have a database on a 6.5 server but wish to upgrade this database to a sql 7 database. But I would like to test this first on another server which is a sql 7 server. Is it possible to restore a 6.5 backup to a SQL server 7.0 server?
Thanks in advance..
View 2 Replies
View Related
Jul 4, 2000
Hi all
I would like to know - we are currently running SQL6.0 on NT4 servers. We have 2 x 3rd party programs that runs on the servers, making use of the databases. We don't forsee any changes in the near future.
Question: will it be wise to upgrade to SQL7 anyways, or can we keep the status quo as is ???
Rgds
De Waal
View 1 Replies
View Related
Jun 17, 2002
Does anyone know of a good whitepaper detailing SQL7 to SQL2000 migration?
Thanks, I really appreciate your help.
--Alex
View 1 Replies
View Related
Mar 17, 2001
Im using MS SQL7 as database software ,but now I plan to upgrate SQL7 to SQL2000 . I would like to know that are there any affect on the old database that already use with sql7 after I upgrade to MSSQL2000 ?
Thanks
View 1 Replies
View Related
Apr 15, 2002
I had a number of jobs which were backing up system and user databases under SQL 7 using SQL ServerAgent. Over the weekend I upgraded SQL 7 to SQL 2K.
All backups work except for one, which gets the following error message: Executed as user: SANDIEGOSvcSQLServer. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
As best as I know SQLSTATE 42000 is an ODBC message indicating a syntax violation or an access violation. I have recreated the maintenance plan in an attempt to rule out a syntax violation. During the upgrade process I did not change the account under which SQL Server Agent runs, so it seems like it should not be an access violation.
Any ideas would be appreciated!!!
Thanks Gary Andrews Andrews_gary_w@solarturbines.com
View 1 Replies
View Related
Nov 29, 2006
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?
View 4 Replies
View Related
May 30, 2001
Hey Folks,
I am trying to replicate a a development database into a production database.
The production database has a different name from the developmet and I want to
find a way of re-creating the Stored procedures from SYSCOMMENTS.
I keep getting garbled ouput from select text from syscomments.
Can anybody please tell me how to extract Stored Procedures' text
from system table SYSCOMMENTS
TIA
View 2 Replies
View Related
May 19, 2008
Hi,
What is the use of sys.syscomments ?
Cheers,
Mathi
India.
View 5 Replies
View Related
May 13, 2008
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.
View 3 Replies
View Related
Aug 20, 2007
Quick question relating to the above tables.
I am currently experiencing an issue where the syscomments and sysdepends tables are increasing exponentially.
For example, i have a database with data segment of 666 MB (maybe its the number!) and the syscomments is 254MB and sysdepends is 325MB. all the other tables are remaining static, and over my sample period have not increased. Also there have been no new procedures or views created on this database, so I am not sure why these two tables are increasing so much.
Does anyone have any ideas as to what is causing this? or have any pointers for things i should be checking?
Many thanks in advance.
Mark
View 3 Replies
View Related
Jan 19, 2007
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.
View 1 Replies
View Related
May 8, 2008
Has anyone experienced problems calling stored procedures that references syscomments.text from Visual Basic 6?
I have a stored procedure that finds all tables referenced by a specific stored procedure. It works well when I call it from SQL Server Management Studio, but there are cases where it does not find the tables when I call it from VB 6.
I've isolated the failure it to a specific condition in the WHERE clause:
SELECT @howfar = so.id
FROM SYSOBJECTS so
LEFT OUTER JOIN syscomments sc on so.ID = sc.ID
Where lower(so.name) = lower('storedProcName')
AND lower(sc.TEXT) LIKE '%' + lower('update') + ' ' + lower('tableName') + '%'
The call from VB works (finds the record) if
" AND lower(sc.TEXT) LIKE '%' + lower('update') + ' ' + lower('tableName') + '%' "
is omitted, and fails (does not find any records, no error is raised) if that condition is included.
I should also add that the VB Call does work for some combinations of stored procedures and tables.
The old SET NOCOUNT ON trick does not make any difference.
View 4 Replies
View Related
Oct 18, 2006
Hello,
I have a table in SQL Server 2000 which has few triggers. When I try to update a record in that table, I get following message:
Warning: The table '[TABLE_NAME]' has been created but its maximum row size (17275) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
where the data I am updating is well less than the field limit. The triggers are stored in syscomments table and when I dropped these triggers, the update statements were executed without this message. Is there anyway I can change the data type of field text in syscomments from nvarchar to ntext?
Thanks
Din
View 1 Replies
View Related
Oct 25, 2000
I'm installing SQL7 on an NT4 SP5 server. It tells me it needs to check the ODBC drivers but then says they are
being held by an application. There are no ODBC drivers installed on this machine to be held.
What do I do? Install some drivers?
View 1 Replies
View Related
Aug 12, 2002
I'm attemting to replicate from a SQL7 box to SQL2000.
The snapshot works fine, but it fails when it tries to push the subscription to the SQL2000 box with a trust error (I don't recall the exact message). I noticed that it fails when Enterprise Mgr is configured as: "Tools/Replication/Configure Publishing, Subscribers and Distribution", Subscriber Tab, "Impersonating SQL Service Agent". It works if I change to "SA".
This is only the case when we replicate from SQL7 to SQL2K. SQL7 to SQL7 works fine with "Impersonating". Has anybody seen this behavior? Any workarounds, other than using SA?
View 2 Replies
View Related
Jul 31, 2001
Hi,
I am running SQL7 SP2 on a Compaq Proliant 5500 (NT4 Server SP6a) with dual processor.
When trying to schedule any jobs with DTSRUN I get the following error:
DTSRun.exe - Application Error
The instruction at "0x77f64d7b" referenced memory at "0x00000010". The memory could not be read.
Has anyone seen this error before ??
Regards,
Tim
View 1 Replies
View Related
Mar 8, 2001
In SQL 7 DTS I'm creating a Data Driven Query Tasks. When I get to writing the transformations in VB Script and try using the Test button to test the script, I get the following message:
Error Source: Microsoft Data Transformation Services Flat File Rowset
Provider
Error opening datafile. The system cannot find the file specified.
The documentation says:
[The transformation is tested] by executing it against a part of the
source data and copying the results to a temporary text file, for
preview purposes.
I can find no place to specify what temporary file is used for the test result and, because it is temporary, have assumed the system creates and
deletes it as needed.
Is this true?
I get this test error for every transformation. even those that work correctly when the DTS package is actually executed.
What can I do to get the transformations to test properly?
Any help or hints will be greatly appreciated.
===============================
William J Brown
Systems Analyst
College of Human Medicine
A114 East Fee Hall
Michigan State University
East Lansing, MI 48824
Voice: (517) 432-7490
Fax: (517) 355-0342
Email: brownwj@msu.edu
View 3 Replies
View Related
Aug 12, 2002
I'm attemting to replicate from a SQL7 box to SQL2000.
The snapshot works fine, but it fails when it tries to push the subscription to the SQL2000 box with a trust error (I don't recall the exact message). I noticed that it fails when Enterprise Mgr is configured as: "Tools/Replication/Configure Publishing, Subscribers and Distribution", Subscriber Tab, "Impersonating SQL Service Agent". It works if I change to "SA".
This is only the case when we replicate from SQL7 to SQL2K. SQL7 to SQL7 works fine with "Impersonating". Has anybody seen this behavior? Any workarounds, other than using SA?
View 1 Replies
View Related
Feb 15, 2007
Hallo, my problem is to upgrade instance of SQL7 to SQL7 SP4.
Server is WIN2K SP4 + MDAC 2.8 SP1
Installing the SQL7 Server from CD is OK.
When i try to apply the SQL7 SP4 the first fase, when SP4 checks all conditions to start is OK, when start to copy file i receive an error -113 like this
--------------------------------------------------------------
Error occurred during the move data process: -113
Component Server: base server base server files
File Group: Base Server Files
File: C:70SP4X86Setup.....SQLIMAGE.DLL
--------------------------------------------------------------
On server is installed the library SQLDMO.DLL for SQL2000 but only the library used by an application VB6.
In need to install SQL7 and i can't install SQL2000 or SQL2005 because we work with an application written for SQL7. I've tried to migrate application SQL2000 but not work properly.
Somebody can help me ?
Thanks in advance.
Aragorn
View 1 Replies
View Related
May 16, 2006
Hi,
I have backup of data from SQL Server 7.0 and now when i'm trying to restore it into SQL Express 2005, I'm getting following error......
--------------------
Msg 3154, Level 16, State 2, Line 1
The backup set holds a backup of a database other than the existing 'GOSLDW' database.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
--------------------
Here is SQL i'm using to restore database,
RESTORE DATABASE GOSLDW
FROM DISK = 'C:sqlserverDataGOSLDW'
WITH MOVE 'GOSLDW' TO 'C:sqlserverDataGOSLDW.mdf',
MOVE 'GOSLDW' TO 'C:sqlserverDataGOSLDW.ldf'
GO
Why i'm getting this error? Am i missing anything here?
Thanks in advance for your HELP.
- R
View 8 Replies
View Related
Dec 5, 1998
How can I copy a SQL 7 database from one server to another? Please tell me all the ways because I've tried the obvious and it doesn't work. (backup and restore - won't go from one server to another, DTS transfer object Wizard - does a whole pile of errors and doesn't do stored proceedures and trigures). Thanks for help in advance. Also, what is the email address to post to the listserv and where is the FAQ for SQL7? Most of my listserv's tell you where to post right at the bottom of the digest I get - any chance you guys would do that with this list? Thanks again.
View 6 Replies
View Related
Mar 22, 2004
We have a server which we needed to upgrade the OS on it from NT 4 Server to Windows 2000 Server.
As the system disks are seperate from the data disks. We did a fresh install of Windows, then installed SQL Server, applied service pack version 3, and then restored the master database.
From Query Analyser everything appears fine. I can query all the databases and tables, see them all, the web applications talk the database fine so all the users have recreated OK.
However .... if we try and look at the database through management console we get the following error.
A connection could not be established to ....
Reason: Cannot resolve collation conflict for like operation..
This happends logged in locally to the machine as administrator as well as connecting remotely. Does anybody have any idea what is happening?
View 8 Replies
View Related
Nov 30, 2007
Hi,
I am trying to upgrade from SQL Server 2000 SP4 to SQL Server 2005. But I am getting an error saying that " Your operating system does not meet service pack requirements for the SQL server release. Install the service pack from the Microsoft download center at http://go.microsoft.com/fwlink/?LinkID=50380, and then run the SQL Server Setup again. For system requirements, see hardware and software requirements, in the readme or in SQL Server Books online."
I don't know what other service pack I would need to upgrade to again when I already have SP4 installed. Could someone tell me what I need to do next.
Thanks.
View 2 Replies
View Related
Jun 8, 2006
Hi there,
I tried to run Upgrade Advisor on two SQL 2000 servers, but the wizard keeps failing when it reaches 22% while analyzing the Database Engine.
I downloaded the latest version, but still receive the same error...
Error: "SQL BPA command line has encountered a problem and needs to close"
Both servers are Windows 2003 Enterprise Edition SP1 with SQL 2000 Enterprise Edition SP4.
Does anyone have an idea what I can do to fix this problem.
Thanks!!
View 38 Replies
View Related
Oct 30, 2001
Hello:
We have an old 16-bit app that runs fine in SQL 7.0 but on our test SQL 2000 box some reports generate the following error "System Message 10202 - The application fetch buffer size is less than the cursor select statement requires". Any ideas what this means, I am not much of a coder. The MS Knowledge base does not list much on this.
Thanks,
View 1 Replies
View Related
Oct 14, 2004
I am having the following error when running the SQL upgrade wizard trying to upgrade SQL 6.5 to SQL 2000. Does anyone here know what is the problem ?
Version Switch has aborted because you do not have "Full Control" permission to one of the HKEY_LOCAL_MACHINESoftwareMicrosoftMSSQLServ* registry keys. Please use regedit32.exe to correct this problem and try again.
I have already checked the registry and I do have full control permission on HKEY_LOCAL_MACHINESoftwareMicrosoftMSSQLServ*. Please help.
View 10 Replies
View Related
Dec 14, 2004
I launch an installatino of SQL Server 2000 on a server, upgrading the V7 original datbase but it failed with error :
"the ordinal 105 could not be located in the dynamic link library opends60.dll"
And the SQL server services cant' start.
Can someone help me ?
It's urgent.
View 4 Replies
View Related
Nov 7, 2007
I have upgraded many of my servers from 2000,SP2 to 2005. Whilst doing 1 server I have the following error message:
Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation..To continue, correct the problem, and then run SQL Server Setup again.
I have tried to search in many places for this error whilst upgrading but found none, please help.
View 7 Replies
View Related
Feb 22, 2008
I am having an issue running a SP4 upgrade for SQL Server 2000. The sp_vupgrade_replication.out file indicates:
Msg 170, Level 15, State 1, Server MS, Line 1
Line 1: Incorrect syntax near '-'.
The sqlsp.log file indicates:
Process Exit Code: (0)
Error running script: sp_vupgrade_replication (1)
Action CleanUpInstall:
Installation Failed.
Any help would be greatly appreciated.
Thanks.
View 3 Replies
View Related
Jan 11, 2007
I'm carrying out an investigation into how much effort will be involved in upgrading our database from SQL Server 7.0 to SQL Server 2005. I've downloaded the Upgrade Advisor and run in against a copy of our production database. Most of the issues are trivial and I understand how to resolve them apart form one (to me) meaningless one:
When to Fix : Before
Description : Class Not Registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
Details : SVCACCTREQ
That's all the information it gives, except for a "This issue is resolved" checkbox. Anyone got any idea what the problem is, or how I go about tracking down the cause?
I'm running the analysis tool from a W2K Professional Client, connecting to SQL Server 7.0 running on an NT4 Server using Windows authentication. The account I'm connecting with is a member of the System Administrator group in SQL Server and is a local admin on the client, and a member of the Users group on the server.
Any pointers appreciated.
Cheers,
Bill
View 2 Replies
View Related
Dec 19, 2006
Hi,
I just tried to install SP1 for SQL 2005. All of the steps succeeded except for the upgrade for Reporting Services, which failed with the error "Unable to install Windows Installer MSP file". When I checked the log there were a whole host of errors such as
"12/19/2006 09:06:41.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.3Reporting ServicesReportManagerBinja
eportingserviceswebuserinterface.resources.dll"
and
"12/19/2006 09:06:41.203 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.3Reporting ServicesReportManagereshelpf1_rsc_webui_standalone_5yr5.htm"
and
"12/19/2006 09:06:47.093 Failed to read registry key: Debug"
I am running a default instance, and was running the install under an account with local admin privileges.
View 1 Replies
View Related
Feb 15, 2008
I am trying to upgrade SQL 2000 SP3 to SQL 2005 SP2 on a Windows 2003 server with all the latest patches. The SQL 2005 install went through like it was supposed to but when it was nearly finished it gave the message:
" there was an unexpected failiure during the setup wizard. You may review the setup logs and/or click the help button for more info". I'm pretty new to Microsoft SQL so I looked at help and there was no information.
I've tried running setup again and keep getting the above error message. During the install the program says everthing is installed but I've noticed the Management Center is missing.
View 6 Replies
View Related