Failed to upgrade from SQL Server 2000 to SQL Server 2005

MS SQL SERVER

    Sponsored Links

    Next

  • 1. Altering large amounts of data
    I have imported data into my sql server 2005 management studio from a flat text file. The file is rather large, and i would like to do updates such as changing data types and setting primary and foreign keys. When I try to do the alter table I get the following error: - Unable to modify table. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. I am trying to alter approximatly six millions records, any help would be greatly appreciated Thanks in advance
  • 2. Problem installing SQL Server 2000 Evaluation on XP Pro SP2
    I just got a 3 new identical computers and I am trying to install SQL Server 2000 Evaluation on them. During the installation process, it seems to be working fine until it gets to the part in the installation where it says "Setup is starting the server and installing your chosen configuration." It doesn't seem to go anywhere from here. I've installed the same SQL Server on another laptop before but I'm not sure why it's not finishing up on these computers. One thing that is different is that I'm configuring the new installs to use mix mode authentication as opposed to windows authentication. The new computers are running on XP SP2, while the laptop has SP1. Can one of these be an issue and what else is there for me to do to successfully install SQL Server? TIA, James
  • 3. Performance Monitor Counter Requirement (Error)
    I have tried to install SQL Server Professional Edition, but it failed. Here is the error message : ========= - Performance Monitor Counter Requirement (Error) Messages Performance Monitor Counter Requirement The System Configuration Check for Performance Monitor counter registry value has failed. For details, see How to: Increment the Counter Registry Key for Setup in SQL Server 2005, in the readme file or in SQL Server Books Online. ============ YES, I have tried to increment the counter registry key, BUT I didn't find the keys specified by the documentation. Any hints, please?
  • 4. Difference between Open License version and version given at Launc
    I have a Launch copy as well. Do you know if this version includes the x64 version of SQL 2005? There are filies with x64 listed in the file names. When I install, it seems that only the 32bit version is running. Aaron G. "Scott Townsend" wrote: > We received a copy of SQL 2005 at a recent SF Launch event. We have SA on > SQL Standard and from what I hear we will not see our Open License copy of > SQL until mid December or so. > > The Launch copy is a full version right? Should I just install the Launch > Copy, or should I wait until we get the Open License copy from our SA > subscription? I don't want something down the road (from our SA OL Version) > to not install because I installed the version from the Launch. > > I have a New Server that's burning a hole in the rack waiting for it!!! > > Thanks, > Scott<- > > >

Failed to upgrade from SQL Server 2000 to SQL Server 2005

Postby chaitu » Wed, 29 Oct 2008 21:59:23 GMT

i,

We have release 1 which has SQL Server 2000. Now we are coming up
with release 2 which will have SQL Server 2005. When we are upgrading
from release 1 to release 2, we are also upgrading SQL Server 2000 to
SQL Server 2005. When we are upgrading to SQL Server 2005, we are
getting following -
UpgradeAdvisor: returned -1.
Error message:

Nothing is displaying in error message. Its blank.

In release 2, we have .Net 3.5 SP1 installation also. Previously when
release 2 doesnt have .Net 3.5 SP1 installation, we were able to
upgrade to SQL Server 2005 successfully. Once we have included .Net
3.5 SP1 installation before we acutally upgrade to SQL Server 2005, we
are getting this error.

Is there any thing to do with .Net 3.5 SP1 installation.
Also, in the log files, it is talking about virtualization. But we
are doing installation on actual machine and not on any virtual
machine.

Here is the error message snapshot from the SQL Server log files -

MSI (s) (BC:74) [14:29:02:765]: Doing action:
ValidateUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action ended 14:29:02:
DetectInstallPaths.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value
1.
MSI (s) (BC:A8) [14:29:02:765]: Invoking remote custom action. DLL: C:
\WINDOWS\Installer\MSI245.tmp, Entrypoint: ValidateUpgrade
Action start 14:29:02:
ValidateUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2.
<Func Name='LaunchFunction'>
Function=ValidateUpgrade
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: ValidateUpgrade
PerfTime Start: ValidateUpgrade : Wed Oct 22 14:29:02 2008
<Func Name='ValidateUpgrade'>
Added FTE to SqlUpgrade property
Added REPL to SqlUpgrade property
<Func Name='updateFeatureSellection'>
Running:
CollectInstallCases
at:
Info 2008.2008
/
9
/
22

14
:
29
:
2


Complete:
CollectInstallCases
at:
Info 2008.2008
/
9
/
22

14
:
29
:
2
, returned
true


Running:
DefineFeatureActionRules
at:
Info 2008.2008
/
9
/
22

14
:
29
:
2


Complete:
DefineFeatureActionRules
at:
Info 2008.2008
/
9
/
22

14
:
29
:
2
, returned
true


Running:
DefineInstallActionRules
at:
Info 2008.2008
/
9
/
22

14
:
29
:
2


Complete:
DefineInstallActionRules
at:
Info 2008.2008
/
9
/
22

14
:
29
:
3
, returned
true


Running:
AddInstallCaseActions
at:
Info 2008.2008
/
9
/
22

14
:
29
:
3


Complete:
AddInstallCaseActions
at:
Info 2008.2008
/
9
/
22

14
:
29
:
3
, returned
true


Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0


Action "
languageUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product
MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "differentLanguage_with_1033_MSSQLSERVER SQL 8.0 SQL Server
Standalone Product MSSQLSERVER" returned false.

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0


Action "
maintenance_MSSQLSERVER SQL 8.0 SQL Server Standalone Product
MSSQLSERVER
" will be skipped due to the
following restrictions:


Condition "sameVersion_as_9.0.139906_MSSQLSERVER SQL 8.0 SQL Server
Standalone Product MSSQLSERVER" returned false.

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0


Re: Failed to upgrade from SQL Server 2000 to SQL Server 2005

Postby chaitu » Fri, 31 Oct 2008 15:39:21 GMT

I have found the issue. Problem is Upgrade advisor is failing if the
system has .Net 3.5 SP1 is installed. I found the following workaround
with which upgrade advisor is working fine.

    Once SQL installation starts, create a subdirectory BPAClient
under C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\BPA
directory.and copy BPAClient.dll (from the sibling bin directory) into
this directory.

Can any one suggest how i can proceed on this?



Similar Threads:

1.No SQL Server Report Subscriptions Run after SQL Server 2005 Upgrade from SQL Server 2000

Hello,

We had a running instance of SQL Server 2000 SP4 with SQL Server 2000
Reporting Services (SP2 I think) that had several working e-mail report
subscriptions.

Since the upgrade to SQL Server 2005 with SP1 the subscriptions simply
do not run...no errors in the logs under "C:\Program Files\Microsoft
SQL Server\MSSQL.2\Reporting Services\LogFiles".

All of the SQL Server 2005 services are running as LocalSystem except
for Integration Services and Reporting Services, which are both running
as Network Service.

The only place I find any errors at all is in the SQL Server Agent
logs...there are a couple of jobs that are Report Server related...they
both point to some kind of logon problem...'EXECUTE AS LOGIN' failed
for the requested login 'NT AUTHORITY\NETWORK SERVICE'.  The step
failed.

What what do I need to do in order to get the unattended subscriptions
running again?

Thanks in advancd,

Dwight

2.Upgrade fails: SQL Server Express 2005 to SQL Server 2005

Hi,
I have installed SQL Server Express 2005 on my Windows Small Business Server 
2003 R2 Premium. But I then afterwards noticed that there were two discs 
included with SQL Server 2005 that has no limits in the database sizes as the 
Express version have (4GB MAX). So I wanted to install the better version, 
but the setup ends with a warning saying I should run the setup of SQL Server 
2005 using command lines with the switch SKUUPGRADE=1.

So I inserted the CD that was included with the R2 Premium Edition.
I opened up a command prompt and wrote:

start /wait D:\SQL2005\setup.exe SKUUPGRADE=1 /qb

The installation didn't prompt for anything this time, it just ended without 
any confirmation. I started up "SQL Server Management Studio Express" and it 
said the following services was "Running":  SQL Server (MSSQLSERVER). The 
instance name had changed from (SQLEXPRESS) to (MSSQLSERVER). But I went to 
properties for the service and it still says "Express Edition". So how do I 
manage to install the better version that was included with my package of Win 
SBS 2003 R2 Premium Edition?

3.Upgrade failed - SQL Server 2000 to 2005

After upgrade completed & rebooted the machine, connect to MSSQLSERVER and
the version is 8.0.760, not 9.anything.

I don't even know where to begin figuring out why it did not upgrade even
though the installer appeared to run successfully.

(I did run from cmd line with "setup SKUUPGRADE=1")

-- 
-Richard M. Hartman

186,000 mi/sec: not just a good idea, it's the LAW!


4.SQL Server 2000 Failover Cluster upgrade to SQL Server 2005

I attempted to upgrade my SQL Server 2000 Enterprise Edition (32 bit)
to SQL Severer 2005 EE 32 bit and while the prereqs passed the
installer will not let me select the version 8.00.x (2000 SP4)
database that it finds on the server.

When I ckeck the install details it tells me that
"Your upgrade is blocked becuase of cluster upgrade rules"

I have tried searching the MS site but none of the entries I found
appear to apply.

Any ideas?

-- Mark D Powell --

5.Upgrading SQL Server 2005 JDBC Driver 1.1 from SQL Server 2000 Driver, in Tomcat 5.5 env

Hi all,

I currently have the SQL Server 2000 JDBC driver installed on my
production Tomcat host in /usr/local/tomcat/common/lib.  I have a
datasourced defined in server.xml (yeah, I know it's global, but I have
my reasons ;-)  ) which I link into my servlets via a ResourceLink.
The datasource definition looks like this:

<Resource
    auth="Container"
    driverClassName="com.microsoft.jdbc.sqlserver.SQLServerDriver"
    logAbandoned="true" maxActive="100" maxIdle="50" maxWait="50000"
    name="jdbc/ods"
    removeAbandoned="true"
    type="javax.sql.DataSource"

url="jdbc:microsoft:sqlserver://sql.example.com:1433;DatabaseName=SuperDB"
    username="servlet_user"
    password="xxxxxxxxx"
    />

I was finding that when service was interrupted on the SQL Server end
of things, Tomcat seemed to be hanging onto bad connection pool
objects.  I don't know if this was the fault of the MS driver, or
Tomcat's DBCP libraries.  A connection would be passed to the servlet
which would then throw an exception reporting a "Broken Pipe" upon the
first attempt to execute a query.

So, I saw that the new driver, SQL Server 2005 JDBC v1.1 was out, and
also supported SQL Server 2000.  So, on my test host, I removed the old
jar files and put the new sqljdbc.jar file in tomcat's common/lib
directory.

I updated the data source definition like thus:

<!-- JDBC resource for ODS DB -->
<Resource
    auth="Container"
    driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
    logAbandoned="true" maxActive="100" maxIdle="10" maxWait="50000"
    name="jdbc/ods"
    removeAbandoned="true"
    type="javax.sql.DataSource"
    url="jdbc:sqlserver://sql.example.com:1433;DatabaseName=SuperDB"
    username="servlet_user"
    password="xxxxxxxxx"
    />

That works super.  As you can see not much change with the exception
that the :microsoft is no longer in the url attribute. But I really
struggled with the driverClassName attribute.  When I set
driverClassName to either

 'com.microsoft.sqlserver.jdbc.SQLServerXADataSource'

or

 'com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolDataSource'

I got the exception:

org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create JDBC
driver of class
'com.microsoft.sqlserver.jdbc.SQLServerConnectionPoolDataSource' for
connect URL
'jdbc:sqlserver://sql.example.com:1433;DatabaseName=SuperDB'

Those are the two class names recomended for data source defintions by
the driver's documentation.  I'm not sure if that implies an error in
the docs, or if I'm just not quite understanding how JNDI references,
Tomcat, and this driver work together.  I'm pretty sure Tomcat just
goes ahead and looks for the the connection pooling implementation
within the driver, which is why it was pooling the connections before.


Interesting stuff.  I figured this might be of use to anyone else out
there.

Also, if anybody has any info on why I might have kept running into
this exception with the old driver, I'd be appreciative:

 java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
JDBC]Broken pipe
        at
com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
        at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
Source)
        at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown
Source)
        at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.submitRequest(Unknown
Source)
        at
com.microsoft.jdbc.sqlserver.SQLServerImplStatement.execute(Unknown
Source)
        at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown
Source)
        at
com.microsoft.jdbc.base.BaseStatement.executeQueryInternal(Unknown
Source)
        at
com.microsoft.jdbc.base.BasePreparedStatement.executeQuery(Unknown
Source)
        at
org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:92)
 [snip]

I'll find out whether I still have this problem with the new driver in
my current environment soon.  The solution was to either wait until the
pool of bad connections was exhausted (not acceptable!!!), or to
restart Tomcat to get it to refresh the pool.  

B

6. upgrading sql server 2000 based application to sql server 2005

7. Upgrade of SQL Server 2000 DB to SQL Server 2005 DB

8. Upgrading SQL Server 2000 with Data Replication to SQL Server 2005



Return to MS SQL SERVER

 

Who is online

Users browsing this forum: No registered users and 94 guest