SQL Fails After SP3a Has Been Applied. Slammer?

Jul 23, 2005

A Win2k, SQL2k machine with SP2 that only just now has been updated to SP3a
fails in different ways. Among other things, when I now start Enterprise
Manager, I get a message saying "rebbrui.rll" is missing and the snap-in
fails to initiate. But then the Manager starts anyway.

But the SQL application does not work. I searched around the net, and I
found that it looks as if SQL Slammer has been on the server. I can tell by
the similar symptoms other users have had, allthough I am not sure. Anyway,
when I run some online virusscans and the Symantec SQLexp-tool to remove
Slammer, I am told that the system is virusfree. Is that because SP3a to
SQL2000 automatically got rid of the virus (if any)?

But how do I get the SQL to run without any errors again?

The server also runs in Terminal Application Mode.

Regards, Lars.

View 4 Replies


ADVERTISEMENT

Update To Sp3a

Jan 23, 2004

I'm trying to upgrade my MSDE to sp3a, I'm following the instructions.

c:sql2ksp3MSDE

setup /upgradesp sqlrun DISABLENETWORKPROTOCOLS=1

But receive the following message:

Invalid product code was found. Check if product is installed.

Then

Could not find package to install on the installation media.

Any help?

Thank you.

View 3 Replies View Related

Sql 2000 Sp3a

Aug 5, 2003

Select @@version does not know the difference between SP3 and SP3A.

Does anyone know of a SQL statement that will let me know if I have SP3A??

Thanks.

View 5 Replies View Related

Cannot Get SP3a To Install

Jun 24, 2004

We have the rtm version of SQL 2000 and have spent the last 2.5 hours trying to apply SP3a. Nothing on the microsoft support site has pointed us to the solution.

Basically, we start the install after shutting down the services, answer all the questions and then when it starts to copy files it fails with an error
'microsoft data access component failed (-1).

Looking in c:winntdatestup.log, the error is unknown. The c:winntsqlsrp.log file is not touched.

We tried renaming the odbcconf.dll file per a microsoft article and no joy.

We also restored mdac_type.exe file per microsoft article and no joy.

Trying to install SP1 and SP2 - same results.

Anyone got any ideas besides it's time to call Microsoft?
:confused:

View 2 Replies View Related

Sp3a Does Not Seem To Apply

Feb 26, 2004

I am trying to install sql server sp3a. I checked the version before and after the sp is applied, and it shows:

8.00.194

Now, according to the sp3a readme:

http://support.microsoft.com/default.aspx?scid=/support/servicepacks/SQL/2000/SP3ReadMe.asp

the following versions should show:

SQL Server 2000 Original Release 8.00.194 RTM
Database Components SP1 or Desktop Engine SP1 8.00.384 SP1
Database Components SP2 or Desktop Engine SP2 8.00.534 SP2
Database Components SP3 or SP3a, or Desktop Engine SP3 or SP3a 8.00.760 SP3

This would imply that after installing sp3a and restarting, the version reported should now be 8.00.760. However, it still shows 8.00.194. So it appears to have not really installed, althought the sp3a installation ran without incident. So, how can I get the sp3a to not just act like it installed, but actually get it to install? Also, I have shut down all mssql services and rebooted, applied patch, and rebooted again. Doesn't help.
Also, if it is really installing, is there another way to tell?

Anyway, I really need to be able to install sp3a to see if it fixes another problem I'm having. Unfortunetly, since I can't even tell if the sp3a is installing, I can't tell if it really doesn't help or not. Thanks.

Tony F

View 2 Replies View Related

SP3a Installs SP1

Oct 20, 2005

I really don't understand this, in an attempt to upgrade/install SP3a, I download the file sql2kdesksp3.exe, which from the documentation, you can either use for upgrading or new installs. I run a new install; in the new instance, I execute "select @@version" and get "Service Pack 1"??

View 8 Replies View Related

SQL 2000 SP3a To SP4

Apr 30, 2008



Our environment is currently running on SQL 2000 sp3a (win2003) and I'm having an issue with 'max worker threads', so I opened a ticket with Microsoft.
They tell me that SP3a is no longer support and I have to upgrade all our servers to SP4.

We had an issue in my previous company and I was told by a consultant that I shouldn't install SP4 because it caused a lot of issues. I'm aware of the 'AWE enabled' issue, are there any others I should watch out for?

Thanks

View 2 Replies View Related

SQL Server 2000 SP3a

Sep 16, 2004

Hi, I've downloaded the SP3a for sql server from the microsoft website. I unpackaged the files into a folder and ran the file setup.bat. I recieved an error that setupsql.exe file was not found. I think theres a folder missing called Setup under the X86 folder. Is there a way I can fix this????????

View 1 Replies View Related

Error On Sp3a URGENT HELP !!

Jul 9, 2004

After past MDAC it fails running 1st script with error sp3_serv_uni.SQL(1) PLEASE HELP

View 2 Replies View Related

Restore System Dbs From SP3 To SP3a?

Jan 14, 2005

Can system databases (master, model, msdb) backed up from SQL2k SP3 be restored to an instance of SP3a? Can they be restored from SP3a to SP3? TIA!

View 4 Replies View Related

SP3a Support And MSDE

Aug 21, 2007

Hi

Now that support for SQL SP3a has been removed, how does this affect MSDE installations? We've got lots of products installed that have come with MSDE backends, all on SP3a. Is it up to the individual vendors as to whether they continue to support on this version? Backup Exec and Insight Manager are 2 that spring to mind.

thanks

View 1 Replies View Related

Upgrade MSDE With SP3a With SP4

Jun 1, 2006

Hi,
I'm trying to upgrade MSDE with SP4.
I used the following in command prompt.
setup /upgradesp sqlrun INSTANCENAME=MSDEINSTANCE SECURITYMODE=SQL UPGRADEUSER=username UPGRADEPWD=userpassword /L*v C:MSDELog.log
i got the message "Please go the control panel to install and configure system components."
What does it mean?
How to upgrade it?I have tried to edit the line with *V, and using the sa username and password, but i get the same message.
RegardsKenneth Davidsen

View 1 Replies View Related

DDL Statements Should Be Applied To All 25 Servers

Aug 7, 2002

Hi All,
We have a development server and about 25 Production servers. Whenever we did any DDL modification to development, it should be applied to all 25 different servers. I am trying to find a way to apply the changes to these servers from Development server without going to each server and run the script. Is there any way I can automate this action. There is no replication in all these servers. Can you please advise me on how to do this. This is a high priority task i have been assigned and I would appreciate any comments asap.
Thanks in advance.

--Jay

View 1 Replies View Related

How Do I Tell What Hotfixes Have Been Applied To An Instance?

Aug 31, 2007



How do I tell what hotfixes have been applied to an instance?

Thanks

View 3 Replies View Related

Subset_filterclause Not Applied At The Subscriber

Nov 6, 2006

I am using merge replication between SQL Server 2005 and SQL Express. Some of the articles in my publication have filter conditions. Changes to subscription databases are being applied to the publication database without regard to these filters.

The easiest way to see this problem is to create a merge publication with a single table article with @subset_filterclause of '0 = 1'. Any inserts to the publication database will not be propagated to the subscription database, but inserts to the subscription database will be propagated to the publication database. Can this be right?

View 4 Replies View Related

Row Count AFTER Filter Has Been Applied.

May 7, 2008



Is there a way to get a count of all the rows (total) after a filter has been applied at the row level?

Ie. Revenue has 11 rows but once the 6 blank ones are filtered count the total number of rows. So it should return 5.

View 1 Replies View Related

Foreach Variable Cannot Be Applied

Apr 30, 2007

I have created a foreach container to capture values from a query and run a script for each line. For some reason though I can't get past the variable mapping.



The SQL Task that is linked to the Foreach container is somthing like this:

SELECT str1, str2, str2, nValue1, nValue2

FROM MyTable



In the SQL Task I've set the following

ResultSet = Full Result Set

Connection Type = OLE DB

Result Name = 0



I've created the following Variables with a Package scope



s1 as String

s2 as String

s3 as String

n1 as Double

n2 as Double



When I run the package I get the following errors

Foreach variable mapping number 4 to variable "User : : n1" cannot be applied

Foreach variable mapping number 5 to variable "User : : n2" cannot be applied



The data type of nValue1 and nValue2 in MyTable are both numeric(19,4)



In setting the variable types in the package it seems that the closest to numeric(19,4) would be double. Is this why it is failing? Is there any way around it? I just need to pass the variables which are numeric and have decimal places.



Any insight would be greatly appreciated.



Regards,

Bill

View 3 Replies View Related

Subscriptions Invalid After SP Applied

Aug 29, 2006

Hello,

I finished applying SP 1 to sql2k5. Under the replication monitor all of the subscriptions now look like [].databasename when they were originally [subscriber1].databasename. Under Mgmt Studio I see the subscriptions correctly. When I try and replicate I get the message "The subscription to publication 'pub_databasename has expired or does not exist." I have tried to reinitialize the subscriptions but it doesn't work. Is there a way to solve this without have to drop the subscriptions and add them again as I do not want to lose the changes that were made on the subscriptions. We are using merge replication. Thanks.



John

View 16 Replies View Related

How Is 4GB Max Database Size Applied?

Oct 11, 2006

Is the 4GB Database size calculated by totalling up the size of all the databases in an instance OR against each individual DB in an instance (e.g. you can have an unlimited number of DB each up to 4GB in size)?
TIA
Antony

View 3 Replies View Related

Does The MSDE2000 Sp3a Come With Northwind Database

Jan 30, 2004

I just downloaded and installed MSDE2000 sp3a for winform and asp.net
quickstart tutorial. But I found it has no sample database such as pubs
and northwind. It used to have these databases. At least in last September
when .Net web Matrix came out.

If this is the case, can someone tell me where to get the sql scripts
to create Northwind database in MSDE?
Becasue the winform tutorial uses this database.

Thanks in advance!

Lei Xu

View 1 Replies View Related

MSDE SP3a Upgrade Problem

Jun 14, 2004

I just upgraded my desktop engine MSDE 1.0 to MSDE 2000 SP3a. Everything seemed to go well, MSSQLSERVER AND SQLSERVER Agent Services are running, problem is, I can no longer see the particular instance on the network from Enterprise Manager.

The installation instructions specified that if the Instance was to accept connections from applications on other computers not to specify the DISABLENETWORKPROTOCOLS parameter, so I didn't.

I'm a little green with this, can anyone suggest a place to start troubleshooting?

View 1 Replies View Related

SP3a And Strong Password Problem

Jul 23, 2005

I urgently need tom use SP3a upgrade the instance of SQLServer200MSDE runing on my local machine but I am having problems in doing so.My first problem is that when I start the set up procedure I get themessage"A strong SA password is required for security reasons. Please useSAPWD switch to supply the same"Currently the sa password isAbc/def/ghk1Which I think is a 'strong password' according to the microsoft rulesathttp://www.microsoft.com/resources/...sword_tips.mspxI would be grateful if someone could confirm that Abc/def/ghk1 is astrong password.If anyone could point me to some published informal help on installingSP3a then that would also be very helpful (I do of course have the MSread me file). If anyone has a sample command line entry for theupdating then I would find that extremely useful. There is oneinstance of MSDE on my machine, named NetSDK.Best wishes, John Morgan

View 6 Replies View Related

SP3a Installation- Cannot Find Setupsql.exe

Jul 20, 2005

current config: Windows XP SP1, SQL Server 2000trying to install : SP3a on SQL Server 20001. I downloaded the three files of the service pack from(http://www.microsoft.com/downloads/...&displaylang=en)..2. Saved the three files to a same local directory d:sqlsvr3a.3. Click through each and extracted them to same local directoryd:sql2ksp33. when I try to run the d:sql2ksp3setup.bat, it tells me thatx86setupsetupsql.exe is not found. Indeed, the file is not there inthe extracted folders.Is this a common problem, or am I missing something ?-thanks

View 1 Replies View Related

SP3a + Extended Procedures = Not Nice (help!)

Jul 20, 2005

Hi(sorry this has turned into a bit of an epic...thought I'd as theexperts!)SQL 2k, sp3a. Dual xeon 2.4. 2 gig ram. everything on a 3 disk raid 5.Microsoft SQL Server 2000 - 8.00.760 (Intel X86)Enterprise Edition on Windows NT 5.0 (Build 2195: )Problem seems to be some extended procs that seemed to be running fineon a 'vanilla' install on a different server now seem to be failing.Failures occuring c 6 - 10 hours.Sometimes the failure logs as the xp failure with severity 20 that Ikindof expect :s. other times absolutely nothing is logged.There are a variety of error messages - or sometimes nothing at all.http://www.mapinfo.com/common/docs/.../SWMSS48_RN.pdfdescribes one of our issues, which seems to come out on the restartafter a failure:Error event id is 19011, Message "SuperSocket info:ConnectionListen(Shared-Memory (LPC)) : Error 5."That site suggests:[color=blue]>Workaround>Suggested solutions include:>• Obtain a hotfix from Microsoft (http://www.microsoft.com). You will[/color]need to >cite the 94302[color=blue]>reference number.>• Turn off shared memory in the client network configuration utility[/color]to >disable shared[color=blue]>memory.>• Replace the SQL Server SSMSLPCN.DLL with the SSMSLPCN.DLL[/color](8.00.540) from >SQL[color=blue]>Server 2000 Service Pack 2.[/color]- but I cant find any sensible information which describes this tocorrelate! Searching MS for that number (94302) came up with zip.The dll version we are running is 2000.80.760.0, although earlierversions are elsewhere on the server (disk images).Interesting to note that we seem to be able to replicate the 'leakage'of improperly closed handles on this version, but not on the oldserver runningthat dll version 2000.80.194.0. This I understood to have been fixedin sp3.On one failure we caught the following (involving our extended procs):2004-02-15 15:03:31.40 spid58 Error: 0, Severity: 20, State: 02004-02-15 15:03:31.40 spid58 Stored function'xp_Contest_CalculateScores' in the library 'e:sqlxpga_procs.dll'generated an access violation. SQL Server is terminating process 58..2004-02-15 15:04:32.14 spid64 Error: 0, Severity: 20, State: 02004-02-15 15:04:32.14 spid64 Stored function 'xp_XML_GetSubTree'in the library 'e:sqlxpga_procs.dll' generated an access violation.SQL Server is terminating process 64..2004-02-15 15:04:48.48 spid53 Using 'dbghelp.dll' version '4.0.5'*Dump thread - spid = 53, PSS = 0x472d7200, EC = 0x725fc098*Stack Dump being sent to e:sqlMSSQLlogSQLDump0001.txt* ************************************************** ******************************* BEGIN STACK DUMP:* 02/15/04 15:04:48 spid 53This was followed about a minute later by:2004-02-15 15:04:55.75 spid53 Stack Signature for the dump is0x1CC032652004-02-15 15:04:55.75 spid53 SQL Server Assertion: File:<recbase.cpp>, line=1378Failed Assertion = 'm_offBeginVar < m_SizeRec'.2004-02-15 15:04:55.89 spid53 Using 'dbghelp.dll' version '4.0.5'*Stack Dump being sent to e:sqlMSSQLlogSQLDump0002.txt2004-02-15 15:04:56.01 spid53 SqlDumpExceptionHandler: Process 2292generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQLServer is terminating this process.* ************************************************** ******************************* BEGIN STACK DUMP:* 02/15/04 15:04:55 spid 53As a side issue we have a number of 'initialisation of notify failed'notes.Any one have any clue about this?Might the DLL need rolling back?Is sp3a knacked for extended procs?Is there some daft setting I've missed :/Any good events to track in particular?Cheers all!

View 1 Replies View Related

DTS Import Not Working After SP3a Upgrade

Jul 20, 2005

I have a DTS package that is importing a fixed length file.After installing SP3a (on PERSONAL & DEVELOPER edition) it will notallow me to assign more than 125 fixed length column positions.After hitting the Finish & OK button it just wipes out the columnsettings.I've reinstalled both Personal & Developer edition. DTS will allowmore than 125 prior to the service pack.

View 2 Replies View Related

Installing SQL Server 2000 SP3a

Jul 9, 2007

I got this message from
Backup Exec for Windows Servers Environment Check 1.0 for SBS1
QUOTE

An instance of Microsoft SQL 2000 was found that is not updated to Service Pack 3a.

An instance of Microsoft SQL Server was found that is not updated to the correct service pack. Using this SQL Server instance with Backup Exec may cause errors. To install Backup Exec successfully, upgrade this SQL Server to Service Pack 3a, or select another instance.


Instance: SBSMONITORING, Version: 2000 SP 3a
Instance: SHAREPOINT, Version: 2000 SP 3a
Instance: BKUPEXEC, Version: 2000 SP 3a
Instance: PADMINISTRATOR, Version: 2000 SP 3a
Instance: MICROSOFT##SSEE, Version: 2000

UNQUOTE



My Question is how to upgrade the instance : "MICROSOFT##SSEE, Version: 2000" to SP 3a?

View 7 Replies View Related

Failed To Upgrade MSDE2000 SP3a To SP4

Aug 24, 2006

Hi,

Recently when i try to upgrade my current MSDE 2000 (SP3a) to SP4, the system just keep on failing me. Here is the scenario:

1. Download the MSDE2000 SP4 from microsoft

2. Extract the SP4

3. Run the following command in either the command prompt or via a batch file:

echo off
echo "Start to Upgrade MSDE SP4 ... "
setup.exe /UPGRADESP SQLRUN INSTANCENAME=JSNG SECURITYMODE=SQL UPGRADEUSER=sa UPGRADEPWD=Th3B3st /L*v c:MSDE_Log.log
echo "SP4 Upgrade Process completed!"

4. Once the above batch file was runned, the standard SQL configuration screen (gathering information) will be triggered.

5. However after a while the installation will just stopped.

6. When i checked on the log, i have found out that the failure of installation is due to the system has failed to configure the server. PFB for the last few rows of the verbose log:

=== Logging stopped: 8/22/2006 17:36:49 ===
MSI (c) (90:88) [17:36:49:865]: Note: 1: 1729
MSI (c) (90:88) [17:36:49:865]: Product: Microsoft SQL Server Desktop Engine -- Configuration failed.

MSI (c) (90:88) [17:36:49:865]: Grabbed execution mutex.
MSI (c) (90:88) [17:36:49:865]: Cleaning up uninstalled install packages, if any exist
MSI (c) (90:88) [17:36:49:865]: MainEngineThread is returning 1603
=== Verbose logging stopped: 8/22/2006 17:36:49 ===

7. When i check the MSI Installer Event ID at Microsoft site, it just said that this is the server configuration problem and i cant find any solution.

Any forumers here experience the above before? Mind to share some thoughts?

FYI, my current MSDE configuration is as follow:

- MSDE 2000 Release A (SP3a - 8.00.760)

- Installed Instance = JSNG



Thanks.

regards,

JS

View 1 Replies View Related

Kb934459 Has Anyone Applied This Post Sp2 Hotfix??

Aug 28, 2007

I'm running sql server 2005 servicepack 2 build 3042 (32bit)

has anyone had any problems with this hotfix????

http://support.microsoft.com/kb/934459

View 9 Replies View Related

Recovery :: Undo Applied Transaction Log?

Oct 21, 2015

USE [master]
RESTORE DATABASE [EmployeeRecovered] FROM  DISK = N'D:BackupsNormalEmployeeFULL.BAK' WITH  FILE = 1,  
MOVE N'Employee' TO N'D:MSSQLDATAEmployeeRecovered1.mdf',  
MOVE N'Employee_log' TO N'D:MSSQLLOGEmployeeRecovered1_log.ldf',  
NOUNLOAD,  STATS = 5, NORECOVERY

[Code] ....

Now I realze the recovery point is somewhere in TranBackup2.trn and need to go back to the state where only TranBackup1.trn is applied. How can i do this ?

View 4 Replies View Related

TFS Transaction Log Backups Failing After SQL/SP2 Applied

May 29, 2007

The SQL server transition log backups for the ReportServer and ReportServerTempDB databases have stopped working ever since I applied SQL Server SP2 to my TFS. I know this because I know the date the SQL SP was applied and I see that my transaction logs started to fail immediately after application of the SP. This is noted because the backup logs for SQL server start to contain the failure immediately after SP2 application. The failure is because the databases are now set to the simple recovery model (or they were set to the simple model before application of SP2 and the previous SQL server allowed or properly ignored transaction log backups with the simple database recovery model). Why is this failing since the backup task indicates that databases with simple recovery are automatically excluded? Is the reportserver and reportservertempdb both supposed to be simple recovery? I thought reportserver was usually full recovery.



Here's the contents of TfsTransactionLogBackup_20070308160004.txt before the SP2 application:






Code SnippetMicrosoft(R) Server Maintenance Utility (Unicode) Version 9.0.2047
Report was generated on "TEAMSERVER".
Maintenance Plan: TfsTransactionLogBackup
Duration: 00:00:00
Status: Succeeded.
Details:






Here's the contents of TfsTransactionLogBackup_Subplan_20070308180007.txt immediately after application of SP2:






Code Snippet

NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3042
Report was generated on "TEAMSERVER".
Maintenance Plan: TfsTransactionLogBackup
Duration: 00:00:05
Status: Warning: One or more tasks failed..
Details:
Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-08T18:00:02.
Task end: 2007-03-08T18:00:02.
Failed:(0) Database 'ReportServer' will not be backed up because it does not have its recovery model set to Full or BulkLogged.

Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-08T18:00:02.
Task end: 2007-03-08T18:00:02.
Failed:(0) Database 'ReportServerTempDB' will not be backed up because it does not have its recovery model set to Full or BulkLogged.

Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-08T18:00:03.
Task end: 2007-03-08T18:00:03.
Failed:(-1073548784) Executing the query "BACKUP LOG [ReportServer] TO DISK = N'E:\SQL Server\Database Services\MSSQL.1\MSSQL\Backup\ReportServer_backup_200703081800.trn' WITH NOFORMAT, NOINIT, NAME = N'ReportServer_backup_20070308180002', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Command:BACKUP LOG [ReportServer] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupReportServer_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''ReportServer_backup_20070308180002'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [ReportServerTempDB] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupReportServerTempDB_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''ReportServerTempDB_backup_20070308180002'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsWorkItemTracking] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsWorkItemTracking_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsWorkItemTracking_backup_20070308180002'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsIntegration] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsIntegration_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsIntegration_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsVersionControl] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsVersionControl_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsVersionControl_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsWorkItemTrackingAttachments] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsWorkItemTrackingAttachments_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsWorkItemTrackingAttachments_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsActivityLogging] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsActivityLogging_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsActivityLogging_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsBuild] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsBuild_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsBuild_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [STS_Config_TFS] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupSTS_Config_TFS_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''STS_Config_TFS_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [STS_Content_TFS] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupSTS_Content_TFS_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''STS_Content_TFS_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TFSWarehouse] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTFSWarehouse_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TFSWarehouse_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10


Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-08T18:00:03.
Task end: 2007-03-08T18:00:03.
Failed:(-1073548784) Executing the query "BACKUP LOG [ReportServerTempDB] TO DISK = N'E:\SQL Server\Database Services\MSSQL.1\MSSQL\Backup\ReportServerTempDB_backup_200703081800.trn' WITH NOFORMAT, NOINIT, NAME = N'ReportServerTempDB_backup_20070308180002', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Command:BACKUP LOG [ReportServer] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupReportServer_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''ReportServer_backup_20070308180002'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [ReportServerTempDB] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupReportServerTempDB_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''ReportServerTempDB_backup_20070308180002'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsWorkItemTracking] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsWorkItemTracking_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsWorkItemTracking_backup_20070308180002'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsIntegration] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsIntegration_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsIntegration_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsVersionControl] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsVersionControl_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsVersionControl_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsWorkItemTrackingAttachments] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsWorkItemTrackingAttachments_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsWorkItemTrackingAttachments_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsActivityLogging] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsActivityLogging_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsActivityLogging_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsBuild] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsBuild_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsBuild_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [STS_Config_TFS] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupSTS_Config_TFS_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''STS_Config_TFS_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [STS_Content_TFS] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupSTS_Content_TFS_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''STS_Content_TFS_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TFSWarehouse] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTFSWarehouse_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TFSWarehouse_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10





And here it is after the KB934458 has been applied:






Code Snippet

NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3054
Report was generated on "TEAMSERVER".
Maintenance Plan: TfsTransactionLogBackup
Duration: 00:00:06
Status: Warning: One or more tasks failed..
Details:
Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-05-01T08:00:03.
Task end: 2007-05-01T08:00:04.
Failed:(0) Database 'ReportServer' will not be backed up because it does not have its recovery model set to Full or BulkLogged.

Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-05-01T08:00:03.
Task end: 2007-05-01T08:00:04.
Failed:(0) Database 'ReportServerTempDB' will not be backed up because it does not have its recovery model set to Full or BulkLogged.

Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-05-01T08:00:04.
Task end: 2007-05-01T08:00:04.
Failed:(-1073548784) Executing the query "BACKUP LOG [ReportServer] TO DISK = N'E:\SQL Server\Database Services\MSSQL.1\MSSQL\Backup\ReportServer_backup_200705010800.trn' WITH NOFORMAT, NOINIT, NAME = N'ReportServer_backup_20070501080004', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.


Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-05-01T08:00:04.
Task end: 2007-05-01T08:00:04.
Failed:(-1073548784) Executing the query "BACKUP LOG [ReportServerTempDB] TO DISK = N'E:\SQL Server\Database Services\MSSQL.1\MSSQL\Backup\ReportServerTempDB_backup_200705010800.trn' WITH NOFORMAT, NOINIT, NAME = N'ReportServerTempDB_backup_20070501080004', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly





.





View 13 Replies View Related

Can't Open Encrypted Package After SP1 Applied

Jun 2, 2006

I have a problem where after applying SQl Server 2005 SP1 to my workstation, where it presumably updates Visual Studio, I cannot open a package that is password protected and was created before applying SP1. My colleague has not applied SP1 and can still open the package, but I don't even get prompted for the password.

Has anyone else come across this?

View 7 Replies View Related

MSDE 2000 SP3a Install Failure

Feb 3, 2004

I am getting an error when installing SP3a of MSDE. I get the error message "The instance name specified is invalid." This is the first SQL database installed, so there is no instance name. I have tried "default" and "MSSQLSERVER" as instance names without success.

your help is appreciated.

View 1 Replies View Related

Mobsync.exe Errors After Installing Sql Server Sp3a

Apr 28, 2004

Server : w2k server sp4
Tablet : w2k sp4
Sql Server 2000

A few days ago we upgraded our servers and tablet pc's with sql server sp3a. At the same time we also changed the publisher and it now uses a static filter to reduce the number of records in the tablet database. Since we have done this we have been getting an error message when we try to synchronize via the windows synchronization manager on our tablet pc's. The error message is "mobsync.exe has generated errors and will be closed by windows. You will need to restart the program. I looked up the error message and it is a stack overflow. This does not happen every time but about 50% of the time. We can always sync from within enterprise manager and everything works fine every time.

If any one has any ideas I would greatly appreciate it and thank you in advance.

View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved