January 24, 2011 at 1:01 am
Isn't backing up, that is. It seems to run, and the job says it completed successfully, but nothing happens. On this server we have two 2005 SP3 instances, production and development on this server, along with three 2008 instances. SSIS backup maint plans for both 2005 instances do not work and both instances have no other maint plans. The 2008 backup maint plans work fine. I'm also able to manually and through scheduled jobs back up databases, logs, etc., so I don't think it's permissions.
I have the job step writing output to a file and a table, but it's just showing completion. Is there any switches that I don't know of that might give more detailed logging?
A previous question posted here at SSC, http://www.sqlservercentral.com/Forums/Topic738022-357-1.aspx asked a similar question and the last suggestion was to re-register the DTS DLL, pointing to a post on MSDN. I'm a little hesitant to do this and possibly risk breaking the 2008 maint plans. I'm getting the same error reported, that the variable \Package\Subplan_1.Disable cannot be found, I delete the variable and the job seems to run (but doesn't).
Any suggestions? It isn't critical that maintenance plans work on 2005 as I can do multi-generation backups through scripts, which is the goal. It's just easier if I can get it working through the maint plan. Not breaking 2008 is more important than fixing 2005 as there are two production instances there plus one development, and the 2005 databases are slowly getting migrated to 2008 (probably just in time for the next generation of SQL Server to come out).
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
January 24, 2011 at 8:09 am
If you look at the path where the backups should be, they are not there ?
If you query the backup history files, does it say they were backed up at that time ?
How long does the job run, and can you look at the inputbeuffer while it's running ?
January 24, 2011 at 7:36 pm
--There are no files being written to the directory specified in the maintenance plan.
--Looking at the dbo.backupset table, there is no activity at the time the job runs or when I manually start it. The job is to back up all user database, 8 in total.
--The job takes less than 2 seconds to run, as two of the databases are 20 gig, this is an unreasonably short period of time. I caught an inputbuffer, but I'm not sure what I should be looking for. I used the script at http://www.sqlservercentral.com/scripts/Miscellaneous/30742/ to capture them to text.
[edit]
Forgot to mention, if I View History of the maintenance plan directly, there's nothing there. And I've also tried creating new jobs and they behave the same way. I have not yet tried making a job to do something like ETL rather than backups, that'll probably be my next step.
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
February 9, 2011 at 4:45 pm
(I started writing this probably over a week ago and somehow never posted it!)
I just completed a further test. I have a server that has only had 2005 installed on it. I was able to create an SSIS/BIDS project, pointing to the mixed 2005/2008 server, and read the contents of a table and write it to a file. I then tried to create a similar project using 2005 BIDS on the mixed version server with no luck. I start SSIS, try to create the project, enter the project name, and it produces the following error message immediately:
Unable to cast COM object of type ‘Microsoft.SqlServer.Dts.Runtime.Wrapper.PackageNeutralClass’ to interface type ‘Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSContainer90’. This operation failed because the QueryInterface call on the COM component for the interface with IID ‘{88DFE892-E9D8-4D23-9739-DA807BCDC2AC}’ failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)).
Anyway, I also asked this on an MSDN forum. The basic answer is that if you have both 2005 and 2008 on the same server, the 2008 SSIS clobbers the 2005 SSIS and things like maintenance plans no longer work.
So a big BOOOO to Microsoft for not doing a better job of isolating their DLLs between versions. I'm very disappointed.
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply