SQL 2008 Maintenance Plan Execution Error
I am trying to setup some backup maintenance job for all the databases in the MSSQL 2008 Web edition server today as I have done for previous MSSQL 2005 Workgroup Edition. The entire setup process are exactly we did in SQL 2005 by going through the Management > Maintenance Plan and dragging and dropping the task that you wish to perform.
Well, sometimes things does not goes as you expect
. When I tried to execute the maintenance plan to verify the plan was setup and should run as it should be, SQL 2008 throws me an error with some Integration Services error. read more
Changing the default SQL 2005 data directory
Default installation of SQL 2005 has the data directory set at C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data. However, if you are looking to setup another RAID volume that separate the database(s) data directory from the default, you may do this by firing up the SQL Server
Management Studio > Right-click the server in the object explorer and select Properties > Database Settings. Change the Data and Log directory to the disk drive that you wish to or any other folders.
Could not load the DLL xplog70.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.)
I was trying to setup a SQL backup maintenance on a SQL 2005 today notice the it does not allow me to do so. At the SQL Management Studio, it shows that the “Agent XPs disabled” at the SQL Server Agent. It looks like this has been miss out to enable during the initial installation. In order to enable this, you will need to run the following T-SQL
use master
go
sp_configure ‘show advanced options’, 1;
GO
RECONFIGURE;
GO
sp_configure ‘Agent XPs’, 1;
go
RECONFIGURE
GO
Alright, everything is set and the message went away. However, it still does not allow me to start the SQL Agent services. The event log captured the following during the service startup:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17750
Date: 10/12/2007
Time: 1:37:19 AM
User: NT AUTHORITY\SYSTEM
Computer: IDOCM
Description:
Could not load the DLL xplog70.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.).For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I try lookup on the SQL installation directory binn folder and to my surprise the xplog70.dll is not there. I copied the dll from another SQL installation server and voila, the SQL Agent services has been started!
MySQL 5.0.x error with PHP 5.2.3
I was trying to setup a new Windows 2003 web server today and everything looks to be in order. It comes to my attention that phpmyadmin has just release 2.11.0 stable version 2 days ago. Without any further hesitation, I downloaded the latest zip files and extracted to the C:\inetpub\wwwroot\phpmyadmin. Next, I install PHP 5.2.3 and MySQL 5.0.45 to the box. While try to check on the PHP installation, it prompts the following on the CLI:
C:\php5>php-cgi.exe -v
PHP 5.2.3 (cgi-fcgi) (built: May 31 2007 09:37:20)
Copyright (c) 1997-2007 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies
with the ionCube PHP Loader v3.1.32, Copyright (c) 2002-2007, by ionCube Ltd., and
with Zend Extension Manager v1.2.0, Copyright (c) 2003-2007, by Zend Technologies
with Zend Optimizer v3.3.0, Copyright (c) 1998-2007, by Zend Technologies
Error in my_thread_global_end(): 1 threads didn’t exist
“Error in my_thread_global_end(): 1 threads didn’t exist” has been discussed heavily in PHP bugs report 41350 Apparently the only way to resolve this is to grab the libmysql.dll from PHP 5.2.1 and replace it on PHP 5.2.2 / 5.2.3
Once the libmysql.dll has been replaced, I have no issues with the CLI test output. However, when I login as root to the Phpmyadmin, it shows me the following screen:

I ended up downgraded the PhpMyadmin version to 2.10.1. I will just have to wait either PHP and MySQL developer to release a patch to correct this.
Maintenance Cleanup Task in SQL 2005
I was checking on one of the MS SQL 2005 Workgroup server today and notice that the disk usage for the server has been used up for more than 50%. It really shocks me! Taking a closer look from the server side, it turns out that the previous Maintenance plan which has been setup to automatically delete the old backup does not have all the backup files deleted as it should.
Done some ‘Googling’ and apparently that there are known issue for the MS SQL 2005 maintenance cleanup task. Some of the options are :
1. Make sure you are running at least MS SQL 2005 SP1 ( at this moment SP2 has been released )
2. The extension file name in to be check for your Maintenance Cleanup task should be *.* instead of .bak / .txt
Micorosoft SQL Server, Error:3154
The following errors pop up today when I was trying to restore a database for a user in SQL 2005.
The backup set holds a backup of a database other than the existing database. RESTORE DATABASE is terminating abnormally. ( Micorosoft SQL Server, Error:3154)
You may get the backup restored using the following T-SQL
RESTORE DATABASE [DBName] FROM DISK = N’C:\DBBackup.bak‘ WITH FILE = 1, REPLACE,STATS = 10
Categories
Recent Posts
- yum update – TypeError: unsubscriptable object
- Magento with Windows IIS
- Helm3 : File Manager Not Showing any Files
- Helm4 Error on Remove Domain
- SQL 2008 Maintenance Plan Execution Error
Recent Comments
- tbx on Cannot create Windows Service for MySQL.Error:0
- bhumi on Cannot create Windows Service for MySQL.Error:0
- Sue on Cannot create Windows Service for MySQL.Error:0
- Shubham on Cannot create Windows Service for MySQL.Error:0
- Tommy on Cannot create Windows Service for MySQL.Error:0

