Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts

Wednesday, March 28, 2012

Problem restoring SQL Svr 2000 Master db - wrong server version?

I'm trying to rebuild from a meltdown. I'm using disk backup files. I
could have sworn that I had SQL Server 2000 SP3 installed on the old
machine, but maybe not.

With SP3 installed, I get a message along the lines that the restore
can't be done because the backup was created using server version
134218262 and this server is version 134218488.

I've searched the documentation and can't find any reference to those
version numbers.

In any case, I thought SQL Server 2000 could restore backups created
on any SP level to any SP level.

Any ideas?

--
Regards.
Richard.On Tue, 13 Jan 2004 06:30:12 GMT, Richard Sherratt
<richard.sherratt@.NOTHINGHEREbrunsley.com.au> wrote:

>I'm trying to rebuild from a meltdown. I'm using disk backup files. I
>could have sworn that I had SQL Server 2000 SP3 installed on the old
>machine, but maybe not.

Ooop. Sorry. I had SP2 installed.

--
Regards.
Richard.|||"Richard Sherratt" <richard.sherratt@.NOTHINGHEREbrunsley.com.au> wrote in
message news:dp7700dtggi3ev97mmgfgtacct926mjdb4@.4ax.com...
> On Tue, 13 Jan 2004 06:30:12 GMT, Richard Sherratt
> <richard.sherratt@.NOTHINGHEREbrunsley.com.au> wrote:
> >I'm trying to rebuild from a meltdown. I'm using disk backup files. I
> >could have sworn that I had SQL Server 2000 SP3 installed on the old
> >machine, but maybe not.
> Ooop. Sorry. I had SP2 installed.

You mention the master DB in the subject.

I believe the system databases (Master, Model, MSDB) have to be restored to
the same level service pack they were backed up from.

Otherwise you're right. You can restore different SP levels of dbs to
different servers.

>
> --
> Regards.
> Richard.|||"Greg D. Moore \(Strider\)" <mooregr@.greenms.com> wrote in message news:<eRSMb.72883$Dq1.66308@.twister.nyroc.rr.com>...
> "Richard Sherratt" <richard.sherratt@.NOTHINGHEREbrunsley.com.au> wrote in
> message news:dp7700dtggi3ev97mmgfgtacct926mjdb4@.4ax.com...
> > On Tue, 13 Jan 2004 06:30:12 GMT, Richard Sherratt
> > <richard.sherratt@.NOTHINGHEREbrunsley.com.au> wrote:
> > >I'm trying to rebuild from a meltdown. I'm using disk backup files. I
> > >could have sworn that I had SQL Server 2000 SP3 installed on the old
> > >machine, but maybe not.
> > Ooop. Sorry. I had SP2 installed.
> You mention the master DB in the subject.
> I believe the system databases (Master, Model, MSDB) have to be restored to
> the same level service pack they were backed up from.
> Otherwise you're right. You can restore different SP levels of dbs to
> different servers.

As part of a D&R test we restored databases to new servers, much the
same as you appear to be trying.

My best guess is that you have a different server name. We made sure
that the servers had the same name as the 'real' ones. If you are
dealing with a meltdown, this might actually help because your client
software won't have to be modified for the new server name.
>
> > --
> > Regards.
> > Richard.|||On Tue, 13 Jan 2004 13:59:38 GMT, "Greg D. Moore \(Strider\)"
<mooregr@.greenms.com> wrote:

<snip
>You mention the master DB in the subject.
>I believe the system databases (Master, Model, MSDB) have to be restored to
>the same level service pack they were backed up from.
>Otherwise you're right. You can restore different SP levels of dbs to
>different servers.

Thanks. That would explain it.

--
Regards.
Richard.

Friday, March 23, 2012

problem pushing subscriber updates to publisher in transactional replication -

I have a primary and secondary servers both running Windows 2000 SP3 with SQL 2000 SP3. I have set up transactional replication with the primary server as publisher and the secondary server has the distributor and subscriber DB. I am testing the scenerio where my primary server goes down and I have to make updates to the secondary server until my primary server comes back up. I am able to update my subscriber database and the transactions go into the MSreplication_queue table to be pushed back to the primary when it comes back up. When I bring the primary server back up and start the queue agent job it starts pushing the transactions over and then stops after 4 or 5 transactions with the error "Failed while applying queued message to publisher". I have attached part of the log file for the agent below

dbserver2.Old_Processing: {? = call dbo.sp_getsqlqueueversion (?, ?, ?, ?)}
dbserver2.Old_Processing: {? = call dbo.sp_replsqlqgetrows (N'DBSERVER', N'Old_Processing', N'Old_Processing')}
[4/15/2004 3:59:47 PM]dbserver2.distribution: exec dbo.sp_helpdistpublisher @.publisher = N'DBSERVER'
Connecting to DBSERVER 'DBSERVER.Old_Processing'
DBSERVER.Old_Processing: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Old_Processing', 21)}
SQL Command : <exec [dbo].[sp_MSsync_ins_IQ2KProcSystem_1] N'dbserver2', N'Old_Processing', '072175', '2004-03-19 00:00:00.000', 1>
DBSERVER.Old_Processing: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Old_Processing', 15)}
SQL Command : <exec [dbo].[sp_MSsync_ins_NightlyProcess_1] N'dbserver2', N'Old_Processing', '072175', '2004-03-19 00:00:00.000', '2004-04-15 15:56:44.623000000', 'Begin ProcessIQ2KSystem', 'AB14E5D7-C81D-4A39-A8F5-51F1C48227B0', '17E5D98F-EDF0-41D0-9991-97511B850720', 1>
SQL Command : <exec [dbo].[sp_MSsync_upd_IQ2KProcSystem_1] N'dbserver2', N'Old_Processing', '072175', '2004-03-19 00:00:00.000', 1>
DBSERVER.Old_Processing: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Old_Processing', 7)}
SQL Command : <exec [dbo].[sp_MSsync_upd_TheatreProcess_1] N'dbserver2', N'Old_Processing', '072175', 1, '2004-03-19 00:00:00.000', 1, NULL, '79A114D6-FF31-4E37-AC2D-90C0A0114F40', '072175', 1, '2004-03-19 00:00:00.000', 0, NULL, 'AF61A098-44A3-45D7-B25B-E8EA9CD464A1', 0x2800, 1>
Failed while applying queued message to publisher
Disconnecting from DBSERVER 'DBSERVER'
Worker Thread 692 : Task Failed
Disconnecting from dbserver2 'dbserver2'
Processed 3 queued trans, 3 cmds, 0 conflicts
Queue Reader aborting

In the sql server logs I am getting this message:
Replication-Replication Transaction Queue Reader Subsystem: agent Repl Queue Reader failed. Failed while applying queued message to publisher.
Error: 14151, Severity: 18, State: 1

Any help would be greatly appreciatedFew suggestions:
Refer to SQLAgent log for further information.
Meanwhile, stopping and restarting SQLServerAgent may allow you to temporarily resolve the problem that you are experiencing.

Did you try to forcefully terminate any replication agents in task manager by any chance?

Finally, running the snapshot agent from the command line may allow you to determine whether it was the snapshot agent that crashed unexpectedly.|||Originally posted by Satya
Few suggestions:
Refer to SQLAgent log for further information.
Meanwhile, stopping and restarting SQLServerAgent may allow you to temporarily resolve the problem that you are experiencing.

Did you try to forcefully terminate any replication agents in task manager by any chance?

Finally, running the snapshot agent from the command line may allow you to determine whether it was the snapshot agent that crashed unexpectedly.

The SQLAgent log did not have any errors in it

Stopping and restarting SQLServerAgent did not allow me to temporarily resolve this problem. I still get the same error.

I did not forcefully terminate any replication agents in task manager.

Should I run the snapshot agent from the command line or the queue agent since the queue agent is what is failing?

I tried running the queue agent from the command line and it failed with the same error as above|||Check whether the KBA [http://support.microsoft.com/default.aspx?scid=kb;EN-US;294970] is any good to you.|||I don't think that is my problem. The only way I have been able to get the queue agent to work again is to either drop and readd the subscription or reinitialize the subscription. Of course when I do this it wipes out any updates that have been done to the subscriber.

Friday, March 9, 2012

Problem looping DTS and BCP within a Stored procedure

All,

This is the scenerio

SP=Stored Procedure

I call SP1 which calls a DTS package.

DTS package calls SP2 and SP2 calls SP3 and SP 4 using an IF condition

SP3 has 3 BCP OUT commands after which it calls SP1 again

Now, the problem is that if I follow all the steps, then only 1 of the BCP command executes and the control exits out of SP3 and returns control to SP1.

If I ignore SP1 and DTS and run SP2 independently, then all BCP steps in SP3 are executed and control returns to SP2

I ma not sure if using DTS and BCP in SQL stored procedures might cause any problems

Appreciate your helpIt seems like your DTS is executing under a different security context than when you execute your SP3 from QA. Are you checking for errors after each BCP in your SP3? If you're calling your BCP using xp_cmdshell, - consider doing INSERT @.temp_tbl exec master.dbo.xp_cmdshell [....].

Saturday, February 25, 2012

Problem Installing SQL 2000 Sp4

While upgrading Sql 2000 Sp3 thge installer is starting to install the service pack. But after running the scripts he gives a very strange error.

error running: 80sp4-tools.sql (1).

after searching and living on google for 3 days for information about this error, I'am no

really desperate.

I hope someone help me or tell me more about this error.

thanks so far


See the following thread...it may help you...

http://www.ureader.com/message/647952.aspx

|||

Thanks MohammedU,

That problem looks exactly as my problem but, the sp4 is starting to install till script 80sp4-tools.sql. and then the installer stops with the same as in the given thread.

the only error that was given in the log file was "(1)"

thanks so far.

Problem Installing FTS

Hi there,
I have SQL Server SP3 (DEV Ed) Installed on my machine.
Select @.@.Version:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation Developer Edition on Windows
NT 5.1 (Build 2600: Service Pack 2)
I have popped in the SQL Server CD and ticked the FTS box and installed FTS.
After install i started the search service but FTS is still not enabled in
EM. I looked under Support Services in EM but FTS is not listed there.
Have I missed something? Do I need to re-install SP3 after I installed FTS
from the original SQL Server CD?
Cheers
Ash Moollan
www.moollan.net
what happens when you issue a select serverproperty('isfulltextinstalled')
If 1 is returned, SQL FTS is installed.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Ash Moollan" <ashraf@.moollan.net> wrote in message
news:efMqGi4zFHA.2960@.tk2msftngp13.phx.gbl...
> Hi there,
> I have SQL Server SP3 (DEV Ed) Installed on my machine.
> Select @.@.Version:
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation Developer Edition on
Windows
> NT 5.1 (Build 2600: Service Pack 2)
> I have popped in the SQL Server CD and ticked the FTS box and installed
FTS.
> After install i started the search service but FTS is still not enabled in
> EM. I looked under Support Services in EM but FTS is not listed there.
> Have I missed something? Do I need to re-install SP3 after I installed FTS
> from the original SQL Server CD?
> Cheers
> Ash Moollan
> www.moollan.net
>
|||Hi Hilary,
Thanks for prompt reply.
Statement returns 0 (zero).
However the SQL Server CD shows the full text search as ticked (installed).
Thanks
Ash Moollan
www.moollan.net
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ObOlu85zFHA.736@.tk2msftngp13.phx.gbl...
> what happens when you issue a select serverproperty('isfulltextinstalled')
> If 1 is returned, SQL FTS is installed.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Ash Moollan" <ashraf*NOSPAM@.moollan.net> wrote in message
> news:efMqGi4zFHA.2960@.tk2msftngp13.phx.gbl...
> Windows
> FTS.
>
|||Ash,
Under what account do you have the SQL Server (MSSQLServer) service started
& running? The "system account" (LocalSystem), a DOMAIN\Account or a "Local
Windows account"? If the latter, you may want to review this KB article:
Q270671 (Q270671) PRB: Full Text Search Menus Are Not Enabled for Local
Windows NT Accounts
http://support.microsoft.com/default...;en-us;q270671
Also, confirm that the FTS components are installed via the following sql
code (1 = installed)
SELECT FullTextServiceProperty('IsFulltextInstalled')
Finally, if you installed the FTS components AFTER you applied SP3, then yes
you should re-apply SP3 to get the SP3 fixes for the FTS and MSSearch
components.
Hope that helps!
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Ash Moollan" <ashraf@.moollan.net> wrote in message
news:efMqGi4zFHA.2960@.tk2msftngp13.phx.gbl...
> Hi there,
> I have SQL Server SP3 (DEV Ed) Installed on my machine.
> Select @.@.Version:
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation Developer Edition on
> Windows NT 5.1 (Build 2600: Service Pack 2)
> I have popped in the SQL Server CD and ticked the FTS box and installed
> FTS. After install i started the search service but FTS is still not
> enabled in EM. I looked under Support Services in EM but FTS is not listed
> there.
> Have I missed something? Do I need to re-install SP3 after I installed FTS
> from the original SQL Server CD?
> Cheers
> Ash Moollan
> www.moollan.net
>
|||Ash,
You can remove (or un-tick) the checkmark via deleting or renaming this
registry key (remove <Instance_Name>, if this is not an named instance
installation of SQL Server 2000)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\<Instance_Name>\Tracking\
{E07FDDA7-5A21-11d2-9DAD-00C04F79D434}
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Ash Moollan" <ashraf@.moollan.net> wrote in message
news:unQVhB6zFHA.3780@.TK2MSFTNGP12.phx.gbl...
> Hi Hilary,
> Thanks for prompt reply.
> Statement returns 0 (zero).
> However the SQL Server CD shows the full text search as ticked
> (installed).
> Thanks
> Ash Moollan
> www.moollan.net
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ObOlu85zFHA.736@.tk2msftngp13.phx.gbl...
>
|||John,
Worked Great!
Thanks
Ash Moollan
www.moollan.net
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OgaJFF6zFHA.2880@.TK2MSFTNGP12.phx.gbl...
> Ash,
> Under what account do you have the SQL Server (MSSQLServer) service
> started & running? The "system account" (LocalSystem), a DOMAIN\Account or
> a "Local Windows account"? If the latter, you may want to review this KB
> article:
> Q270671 (Q270671) PRB: Full Text Search Menus Are Not Enabled for Local
> Windows NT Accounts
> http://support.microsoft.com/default...;en-us;q270671
> Also, confirm that the FTS components are installed via the following sql
> code (1 = installed)
> SELECT FullTextServiceProperty('IsFulltextInstalled')
> Finally, if you installed the FTS components AFTER you applied SP3, then
> yes you should re-apply SP3 to get the SP3 fixes for the FTS and MSSearch
> components.
> Hope that helps!
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Ash Moollan" <ashraf@.moollan.net> wrote in message
> news:efMqGi4zFHA.2960@.tk2msftngp13.phx.gbl...
>

Monday, February 20, 2012

Problem inserting into a Text field in a temp table after SP3

I have a stored proc that is inserting data into a Text field. This was
working fine on Friday, but today throws the following error:
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 55 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Yesterday we upgraded our SQL server from SP2 to SP3, and today we upgraded
3 to 3a after finding this problem. We found the KB article 817359 which
seems to be related, but if we change their example from nText & nVarchar to
Text and Varchar we still get the error (the same one as above). Can anyone
tell me how to fix this problem?
TIA
Ron LounsburyRon,
You should contact PSS to report this. An AV normally means a bug in
sqlserver. You should not be charged for this incident.
--
-oj
RAC v2.2 & QALite!
http://www.rac4sql.net
"Ron Lounsbury" <rlounsbury AT Progeny DOT net> wrote in message
news:uwvRfPrsDHA.1788@.tk2msftngp13.phx.gbl...
> I have a stored proc that is inserting data into a Text field. This was
> working fine on Friday, but today throws the following error:
> ODBC: Msg 0, Level 19, State 1
> SqlDumpExceptionHandler: Process 55 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> Yesterday we upgraded our SQL server from SP2 to SP3, and today we
upgraded
> 3 to 3a after finding this problem. We found the KB article 817359 which
> seems to be related, but if we change their example from nText & nVarchar
to
> Text and Varchar we still get the error (the same one as above). Can
anyone
> tell me how to fix this problem?
> TIA
> Ron Lounsbury
>|||OJ
Thanks for the response. It was a bug that they have a fix for, but you
have to call them to get it.
Ron Lounsbury
"oj" <nospam_ojngo@.home.com> wrote in message
news:eJjF$jrsDHA.4056@.TK2MSFTNGP11.phx.gbl...
> Ron,
> You should contact PSS to report this. An AV normally means a bug in
> sqlserver. You should not be charged for this incident.
> --
> -oj
> RAC v2.2 & QALite!
> http://www.rac4sql.net
>
> "Ron Lounsbury" <rlounsbury AT Progeny DOT net> wrote in message
> news:uwvRfPrsDHA.1788@.tk2msftngp13.phx.gbl...
> > I have a stored proc that is inserting data into a Text field. This was
> > working fine on Friday, but today throws the following error:
> >
> > ODBC: Msg 0, Level 19, State 1
> > SqlDumpExceptionHandler: Process 55 generated fatal exception c0000005
> > EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> >
> > Yesterday we upgraded our SQL server from SP2 to SP3, and today we
> upgraded
> > 3 to 3a after finding this problem. We found the KB article 817359
which
> > seems to be related, but if we change their example from nText &
nVarchar
> to
> > Text and Varchar we still get the error (the same one as above). Can
> anyone
> > tell me how to fix this problem?
> >
> > TIA
> > Ron Lounsbury
> >
> >
>