SQL Server 2005 agent job runs a SSIS package ( Analysis Services Processing Task) fails

Hi,
SQL Server 2005 standard edition.
I have a SSIS package which has a Analysis Services Processing Task. I have tested the package in BIDS and it runs ok. But when I created a agent job and run it from the job it reports error:
Code: 0xC0012024 Source: Analysis Services Processing Task Description: The task "Analysis Services Processing Task" cannot run on this edition of Integration Services.
It requires a higher level edition.
This is the result of select @@version
Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86) Nov 24 2008 13:01:59 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Any idea?

Hi,
SQL Server 2005 standard edition.
I have a SSIS package which has a Analysis Services Processing Task. I have tested the package in BIDS and it runs ok. But when I created a agent job and run it from the job it reports error:
Code: 0xC0012024 Source: Analysis Services Processing Task Description: The task "Analysis Services Processing Task" cannot run on this edition of Integration Services. It
requires a higher level edition.
This is the result of select @@version
Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86) Nov 24 2008 13:01:59 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Any idea?
Anyway, I have found a work around:
http://technet.microsoft.com/en-us/library/ff929186.aspx

Similar Messages

How to pass parameters to sql agent job run configured ssis package

Hi all,
I have a big problem at my small project.
I build my SSIS package that get its variables values from a configuration file..
and when i build a SQL agent job to run this package in a schedule i set the values of variables in it .. but in run-time the package still get its parameters from the configuration file !??
any help please ?

>SQL agent job to run this package in a schedule i set the values of variables in it
One way, setup a configuration table for the package. Let the package read the values for the variables from there.
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

How to get the SQL Signon that Agent Jobs "Run As" or "Executed as User"

How to get the SQL Signon that Agent Jobs "Run As" or "Executed as User"?
I have an install SQL scripts that creates a Linked Server. I want to put some security on the Linked Server and only grant the Agent Job Signon (the "Run As" or "Executed as User") access to the linked server. I need to retrieve the
Agent Job Signon (something like "NT SERVICE\SQLAgent$FIDEV360BI02").
I could query certain jobs and SUBSTRING the Message column - using some form of the query below, which would return "Executed as user: NT SERVICE\SQLAgent$SSDEVBI02. The step succeeded." But that is pretty imprecise.
use msdb
SELECT [JobName] = JOB.name,
[Step] = HIST.step_id,
[StepName] = HIST.step_name,
[Message] = HIST.message,
[Status] = CASE WHEN HIST.run_status = 0 THEN 'Failed'
WHEN HIST.run_status = 1 THEN 'Succeeded'
WHEN HIST.run_status = 2 THEN 'Retry'
WHEN HIST.run_status = 3 THEN 'Canceled'
END,
[RunDate] = HIST.run_date,
[RunTime] = HIST.run_time,
[Duration] = HIST.run_duration,
[Retries] = HIST.retries_attempted
FROM sysjobs JOB
INNER JOIN sysjobhistory HIST ON HIST.job_id = JOB.job_id
-- CHANGE THIS
-- WHERE JOB.name like '%GroupMaster%' or Job.name like '%etlv%'
ORDER BY HIST.run_date, HIST.run_time

by default all sql jobs are executed as sql server agent account, unless otherwise a proxy is setup.
you can get the proxy information as Olaf mentioned, if the proxy_id is null for the step, it implies that the job step was executed as sql server service account and in such case it will be null
so, if it is null, it ran as sql server agent account.
so, one work around is get the sql server agent service account and if the proxy is null, that means it ran as sql server agent account, so, use isnull function. the disadvantage would be if the sql server agent account was switched, you might not get the
accurate information as the new account will show up though the job really ran as old account, to get this information, you need to get this from the logmessage column as you mentioned above.
try this code...
/*from sql 2008r2 sp1, you get the service accounts using tsql,otherwise you have to query the registry keys*/
declare @sqlserveragentaccount varchar(2000)
select @sqlserveragentaccount= service_account
from sys.dm_server_services
where servicename like '%sql%server%agent%'
select message,isnull(name,@sqlserveragentaccount) as AccountName
from sysjobhistory a inner join sysjobsteps b
on a.step_id=b.step_id and a.job_id=b.job_id
left outer join sysproxies c on c.proxy_id=b.proxy_id
Hope it Helps!!

SSIS Analysis Services Processing Task - which object is being processed?

Hi
I've just fallen down the hole dug by a gotcha in the SSIS Analysis Services Processing task (let's call it the ASPT as it's too long to type).
I was doing testing yesterday, targeting a test database. The way things are set up here is that we have two structurally-identical databases (let's call them SSASLive and SSASTest) on the same SSAS server.
The SSIS package includes an Analysis Services Processing task that processes a partition of a measure group in a cube.
So I changed the properties of the AS Connection Manager in the package to point to database SSASTest. Then, because I'm paranoid, and don't trust the Editor for the ASPT, I edited the object to be processed, by deleting the existing object from the
list and re-adding it (going down the tree: database SSASTest, cube TheCube, measure group TheMassiveMeasureGroup, partition CurrentMonth).
This is an annoying necessity, because: the ASPT editor doesn't allow you to see exactly what the object(s) in the list to be processed are, by e.g. double-clicking on them. All you can see is the lowest-level object name, which could be just
"Current Month". Current Month what? There's no way of telling.
Test worked fine. I made sure the AS Connection manager was reset to point to SSASLive, and deployed the package.
This morning, the package ran, and processed the partition in database
SSASTest. What happened? Looking in the Code view of the package, I found the XMLA behind the Processing task: the database name is literally specified in the XMLA, and completely ignores the Catalog of the AS connection. This information
is not exposed anywhere in the UI view of the package.
It's a bit like the dangerous annoyance when testing SSIS package Exec SQL tasks, where a previous developer has insisted on fully-qualifying object names: SELECT * FROM LiveDatabase.dbo.ATable. You're working with a connection to a test database,
but it makes not difference...
But at least that problem is clearly visible. I know that specifying the database name is normal in XMLA tasks: but at least the SSIS editor should allow you to see what the setting is.

No, the point is that the Connection Manager's Initial Catalog setting (whether hard-coded or set by any of the configuration methods) has no effect on the database addressed by the Analysis Services Processing task.
Steps to reproduce:
1. Create an Analysis Services database containing a cube (or select an existing one): let's call it ASDB1.
2. Make a copy of it on the same server, e.g. by backing up and restoring: let's call it ASDB_Copy
2. Set up an SSIS package with a Connection Manager pointing to ASDB1
3. Create an Analysis Services Processing task, using the Connection Manager, processing any particular SSAS object.
4. Run the package. The SSAS object in ASDB1 is processed (not the object in ASDB_Copy). (Confirm by checking the Last Processed date in SSMS, Properties).
5. Change the Connection Manager's Initial Catalog setting to point to ASDB_Copy.
6. Run the package. The SSAS object in ASDB1 is processed, not the object in ASDB_Copy. The Connection Manager's Initial Catalog setting has no effect on the AS Processing Task. Examining the Code view of the package confirms that the XMLA
behind the task specifies the database as well as the AS object. (and this database setting is still ASDB1).
The fix would be for SSIS to perform validation of AS objects referenced by the AS Processing Task whenever its Connection manager is pointed to a different database, and to update the XMLA accordingly.
Also, it would be useful to be able to see exactly what the objects listed in the Processing Task are. The information shown is just not sufficient to identify the object to the developer. I may have dozens of measure groups with a partition
called Current Month - but "Current Month" is all I can see in the editor, and there's no way to e.g. double-click on an item in the list and get the full object identification (Cube X, measure group Y, partition Current Month). Sure,
I can go and look at the XMLA, but that's fiddly: if there's going to be a wrapper around the XMLA (which is what the AS Processing Task is), then it should be unambiguous.

SQL server 2005 SP3 can run SAP B1 2005A SP01 PL51

Hi All,
I could successfully install SAP B1 2005A SP01 PL51 in the SQL server 2005 SP3.
In this link:
http://service.sap.com/smb/sbo/platforms
you won't find it such info.
Why I upgrade, it is caused by the printing error issue using citrix.
Anyone of you that have problem after run the B1 on that SQL, pls share.
Someone who need webex file that shows the install process can request it to me. Let me know.
Rgds,

Hi Arshdeep,
Thx for your reply. I just wonder why SAP did not inform the availability SP3 from Microsoft and the explanation about the inapplicable of SP3 for SAP B1 in the B1 platform link.
I have tested without using any steps and any other procedures. Practice is a good lesson to learn for me. Nevertheless, one concern from modern customers are the compatibility or adaptibility of SAP B1 to Microsoft product especially SQL since it is one of database platform.
Old-fashioned customer will disregard that because they will think as long as my SAP B1 and SQL server still run well, I don't care..
Rgds,

How to Create a SQL Agent Job For A SSIS Package with Sql Server Authentication

Hi ALl,
I have a SSIS package which basically has a data flow task in which i pull the data from one server and copy it into another server and my source server is the one where i dont have windows authentication and i have to only use a sql server authentication
. This package runs fine if i click the server connection properties type the password and save it.
Now, my task is to set up a sql agent job which basically uses a proxy account and takes this package from the file system and runs it.But when i try to run this package, its failing with an error saying
"Login Failed For rpt5user" where rpt5user is the username for my sql server authentication of the source connection.
Can someone please help me with any suggestions on how to do this?
I have heard that we can achieve it by using xml config file which i have never used and i am trying to google around but for no luck.
So, If someone can please throw any suggestions or ideas on this it would be great.
Thanks

You need to add password as a config item and set it from the file source or sql table
see this as an example
http://blogs.msdn.com/b/runeetv/archive/2009/12/22/ssis-package-using-sql-authentication-and-dontsavesensitive-as-protectionlevel.aspx
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

HOw to avoid DeadLocks when you schedule a Sql Server Agent Job and calling SSIS packages

Hi All,
I have scheduled 2 packages in in Sql Server Agent jobs .
First job which is having Package 1 executing at 11 AM and where I am inserting the data in the table.
Second job which is having Package 2 executing at 12 AM and where I am updating the data in the table based on the first job inserted records.
When I am executing my first job it taking more time and executing till 12 AM and from 12 AM my job 2 also starting ,so getting deadlocks conflicts because inserting happening from job1 and updating happening from Job 2.
How to avoid deadlocks and fix the issue.
Please Suggest .
Thanks & Regards,
Anand

Hi Anand,
Here is another solution, you can set the Job 2 not to run based on a schedule, and create another SQL Server Agent Job which starts at 12 AM and run with a specified time interval to execute a SQL statement in which you do the following steps:
1. Get the status information of Job 1 using the statement:
DECLARE @i int;
EXEC @i = msdb.dbo.sp_help_job @job_name = ‘Job Name'
2. If the value of @i is 1 which means the status of job 1 is success and current time is, then start the job 2. So, the statement is as follows:
IF @I = 1
EXEC msdb.dbo.sp_start_job @job_name= ‘Job Name’
Regards,
Mike Yin
TechNet Community Support

List of SQL server Agent jobs for a SSIS package

Hello everyone,
Can you please help me in trying to list all the jobs that have a particular ssis jobs. I saw that all the jobs and jobs steps with the query:
SELECT
   Srv.srvname AS ServerName,
   Job.name AS JobName,
   JStep.step_id,
   JStep.step_name AS StepName,
   JStep.command,
   Job.enabled
FROM   dbo.sysjobs Job
JOIN   dbo.sysjobsteps JStep
   ON JStep.job_id = Job.job_id
JOIN   MASTER.dbo.sysservers Srv
   ON Srv.srvid = Job.originating_server_id
--WHERE JStep.subsystem='SSIS'
WHERE    JStep.step_name = <Job_step_name>
And also found sysssispackages table for all ssis packages. But I am not sure how to link the package to job. Please help me.
Thanks in advance.

Try this:
USE MSDB
GO
SELECT
sj.job_id as JobId,
sj.name as JobName,
sjs.step_name as StepName,
sjs.Command as Command
FROM sysjobs sj
INNER JOIN sysjobsteps sjs
    ON(sj.job_id = sjs.job_id)
    WHERE sjs.subsystem = 'SSIS'
GO
or here is an
article that uses PowerShell
Andy Tauber
Data Architect
The Vancouver Clinic
Website | LinkedIn
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and
"Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

Join the SQL Server Msdb.dbo.SysJobSteps to the SSIS Package table dbo.sysssispackages

I have the following query which returns jobs and jobsteps - for those items which have SSIS Packages attached, I would like to include a link to the results of this query below - to the actual SSIS Package Id - Can someone tell me what the column is that
references the two ?
dbo.sysssispackages= dbo.SysJobSteps
I could parse the "command" label - but would prefer something along the lines of job_id unique identifier.
SELECT
Job.job_id,
Job.name,
Job.enabled,
Job.description,
Job.date_created,
Job.Date_modified,
Step.Step_Id,
Step.step_name,
Step.subsystem,
Step.command,
Step.server,
Step.database_name,
step.last_run_duration,
Step.Last_run_date
FROM Msdb.dbo.SysJobs JOB
INNER JOIN Msdb.dbo.SysJobSteps STEP ON STEP.Job_Id = JOB.Job_Id
John

Parse the command column to get the SSIS package file name may be your only option here.

Copy table from Ms SQL Server 2005 to Oracle with SSIS package

Hi all
I am witting an SSIS package to copy 2 tables from Ms SQL Server 2005 to an Oracle 10g database.
Problem: I can only see the Microsoft OLDB Provider for Oracle and it is too slow. How can I use the Oracle ODBC in aMs SQL Server 2005 or building a .net SSIS package.
thanks

Yes I am able to see the driver on the Data Source (ODBC), I also created a connection to the Oracle database. The problem in Ms SQL Server 2005 is that the ODBC connection I created is not listed. None of the lo local connections are listed, only Microsoft OLEDB connections

SQL Server 2005 - JdbcRowSetImpl

I have a Java Studio Creator JSF web application that runs well on Sql Server 2000. I moved the database to Sql Server 2005 but my application is not working correctly now.
When I pass a parameter to a JdbcRowSetImpl object and execute, I get the following error message - "The cursor type/concurrency combination is not supported." .
I just downloaded the latest SQL Server 2005 driver (sqljdbc.jar) and configured the datasource to use that driver but the same issue is happening.
Does anyone know how to use a JdbcRowSetImpl object for SQL Server 2005

Hi,
SQL Server 2005 standard edition.
I have a SSIS package which has a Analysis Services Processing Task. I have tested the package in BIDS and it runs ok. But when I created a agent job and run it from the job it reports error:
Code: 0xC0012024 Source: Analysis Services Processing Task Description: The task "Analysis Services Processing Task" cannot run on this edition of Integration Services. It
requires a higher level edition.
This is the result of select @@version
Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86) Nov 24 2008 13:01:59 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Any idea?
Anyway, I have found a work around:
http://technet.microsoft.com/en-us/library/ff929186.aspx

WRITEBACK + SQL SERVER 2005

Hi,
I am trying to implement Writeback functionality with SQL SERVER 2005 as back end database. Can anybody explain me with the steps involved?
I am tried what venkat explained in his bizint blog. But in the dashboard, the update button is grayed out and the error is the associated sql template not found on server. The name in the table properties and in the webmessage name are one and the same.
Thanks,
Ramya

Hi,
SQL Server 2005 standard edition.
I have a SSIS package which has a Analysis Services Processing Task. I have tested the package in BIDS and it runs ok. But when I created a agent job and run it from the job it reports error:
Code: 0xC0012024 Source: Analysis Services Processing Task Description: The task "Analysis Services Processing Task" cannot run on this edition of Integration Services. It
requires a higher level edition.
This is the result of select @@version
Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86) Nov 24 2008 13:01:59 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Any idea?
Anyway, I have found a work around:
http://technet.microsoft.com/en-us/library/ff929186.aspx

Oracle provider Issue in SQL Server 2005

Hi all,
On the dev server, I'm using SSAS 2005 (32-bytes) + Oracle provider for OLE DB to access my Oracle Database and it works perfectly.
On the production server, SSAS 2005 is running on a 64-bytes platform.
The Oracle client 10.2.0.1.0 (64 bits) has been installed containing the Oracle provider for OLE DB but unfortunately the Oracle provider for OLE DB does not appear in the list in BIDS when trying to create a date source.
Could someone help ?
Regards,
Juan

After much grief I figured this out and this works for me going from x64 sql 05 on windows server 2003 to x86 oracle 10g on another windows server 2003 box...
Software Prerequisites
•     x64 Oracle Client:
http://www.oracle.com/technology/software/products/database/oracle10g/htdocs/10201winx64soft.html
•     x64 Oracle Data Access Components (ODAC) http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
•     x86 Oracle Client:
http://www.oracle.com/technology/software/products/database/oracle10g/htdocs/10201winsoft.html
•     SQL Server 2005 SP2 (x64):
http://www.microsoft.com/downloads/details.aspx?FamilyID=D07219B2-1E23-49C8-8F0C-63FA18F26D3A&displaylang=en
Patch Level Required (As of Thursday, July 31, 2008):
•     Microsoft SQL Server Management Studio: 9.00.3042.00
•     Microsoft Analysis Services Client Tools: 2005.090.3042.00
•     Microsoft Data Access Components (MDAC): 2000.086.3959.00 (srv03_sp2_rtm.070216-1710)
•     Microsoft MSXML: 2.6 3.0 4.0 6.0
•     Microsoft Internet Explorer: 7.0.5730.13
•     Microsoft .NET Framework: 2.0.50727.42
•     Operating System: 5.2.3790
•     Oracle Data Access Components (ODAC): 10.2.0.3.00 (64-bit Oracle10g Release 2 ODAC for Windows x64)
1. install the x64 and x86 oracle clients on the mssql box
2. install the odac on the mssql
3. Verify that the registry settings at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI and
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSDTC\MTxOCI
are correct:
a.     OracleOciLib = oci.dll
b.     OracleSqlLib = orasql10.dll
c.     OracleXaLib = oraclient10.dll
4. Verify that your tnsnames.ora and sqlnet.ora files have the correct info to connect to the source Oracle 10g (x86) 32 bit source. Note if there is a DNS or other name resolution problem in the environment you may need to change your host entry in your tnsnames file to be the actual I.P. address of the source Oracle box, until the network issue is resolved by the applicable environments network engineer. Additionally, note that if your client tnsnames.ora file is not configured to match the network topology in use, you will have issues… loopback configurations particularly cause grief.
5. Update Machine.config Add the following binding policy:
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Oracle.DataAccess" publicKeyToken="89b483f429c47342" />
<bindingRedirect oldVersion="2.0.0.0-10.9.9.9" newVersion="2.102.3.2" />
</dependentAssembly>
</assemblyBinding>
</runtime>
6. Save the following as a *.reg file and run it...
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSDTS\Setup\WizardPath]
@="C:\\Progra~2\\Microsoft SQL Server\\90\\DTS\\Binn\\DTSWizard.exe"
7. Save the following as a *.bat file...
rem Progra~2 is short path name for "Program Files (x86)" and works around an Oracle client bug that doesn't like the ()'s in the path
start /B "C:\Progra~2\Microsoft Visual Studio 8\Common7\IDE" "C:\Progra~2\Microsoft Visual Studio 8\Common7\IDE\devenv.exe"
8. Save the following as a *.bat file...
start /B "C:\Progra~2\Microsoft SQL Server\90\Tools\binn\VSShell\Common7\IDE" "C:\Progra~2\Microsoft SQL Server\90\Tools\binn\VSShell\Common7\IDE\SqlWb.exe"
9. Create a shortcut that points to each of the batch files you just created and only launch BIDS or SSMS from those *.bat files...
10. create your packages, etc., as normal, but you will not be able to fully test them from BIDS or SSMS because they are 32 bit running in 64 bit o/s...
11. Create a job with a line similar to the following as a cmdexec type of job...
"C:\Progra~2\Microsoft SQL Server\90\DTS\Binn\DTExec.exe" /FILE "C:\SomeWidget.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
12. your done...
Best Regards, from a Las Vegas Bohemian...

SQL Server 2005 Dev Integration Services Fail

I've got VS2005 v.8.0.50727.867 (vsvista.050727-8600) on my 64bit Windows 7 box. I am trying to install SQL Server 2005 Integration Services on this Win7 box so I can load and edit the Win XP SSIS projects that I had on my XP box. So far I've
not been able to successfully install the Integration Services with a failed permission on the SQL**DTD.msi file.....I've copied this file locally and tried to run it and it would start but then would give permission error.
Is there an inherent incompatibility running SSIS projects in SQL Server 2005 on a 64bit Win 7 box? Worked great on my XP box.
I've been "upgrading" the SSIS projects to VS2008 since I was able to get SSIS installed. Any ideas what I need to do to get this beast to work?
TIA
Harry

Thanks Alberto
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version      : Professional Service Pack 1 (Build 7601)
Time            : Mon Aug 25 09:31:30 2014
DT0315 : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features,
install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL
Server in Books Online.
DT0315 : Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS).
Machine         : DT0315
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_1.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_1.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_1.log
Machine         : DT0315
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_2.log
Machine         : DT0315
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_1.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_2.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_2.log
Machine         : DT0315
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_3.log
Machine         : DT0315
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_2.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_3.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_3.log
Machine         : DT0315
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_4.log
Machine         : DT0315
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_3.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_4.log
Machine         : DT0315
Product         : Microsoft VSS Writer for SQL Server 2012
Product Version : 11.0.2100.60
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SqlWriter_1.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_4.log
Machine         : DT0315
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLSupport_5.log
Machine         : DT0315
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLNCLI_4.log
Machine         : DT0315
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_OWC11_5.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BOL_1.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_BackwardsCompat_5.log
Machine         : DT0315
Product         : Integration Services
Error           : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Integration Services (64-bit)
Product Version : 9.00.1399.06
Install         : Failed
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_DTS.log
Last Action     : InstallFinalize
Error String    : Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing
32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.
Error Number    : 29549
Machine         : DT0315
Product         : SQLXML4
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_1.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 (64-bit)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQL.log
Machine         : DT0315
Product         : SQLXML4
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_SQLXML4_2.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Analysis Services (64-bit)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_AS.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Notification Services (64-bit)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_NS.log
Machine         : DT0315
Product         : Microsoft SQL Server 2005 Tools (64-bit)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0007_DT0315_Tools.log
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

SQL Server 2005 SP2 install on Vista

Hi,
I have all updates for Vista, tried to install SQL Server 2005 SP2, the following log file:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version      : Professional (Build 6000)
Time            : Wed Mar 26 12:20:54 2008
USER-PC : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
Machine         : USER-PC
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SqlWriter_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_2.log
Machine         : USER-PC
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_2.log
Machine         : USER-PC
Product         : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQL.log
Machine         : USER-PC
Product         : Workstation Components, Books Online and Development Tools
Warning         : Warning 28123.Warning: SQL Server Setup cannot install this feature because a different edition of this feature is already installed. For more information, see 'Version and Edition Upgrades' in SQL Server Books Online.
Machine         : USER-PC
Product         : Microsoft SQL Server 2005 Tools Express Edition
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_Tools.log
Setup succeeded with the installation, inspect the log file completely for status on all the components.
Time            : Wed Mar 26 12:23:51 2008
==============================================================
When I try to start SQL Server it times out. SQL Server Express is running ok.
Can you help me get this started?
Thank you,
Lucy

This is the previous errorlog:
2008-04-09 11:47:06.27 Server      Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Evaluation Edition on Windows NT 6.0 (Build 6000: )
2008-04-09 11:47:06.27 Server      (c) 2005 Microsoft Corporation.
2008-04-09 11:47:06.27 Server      All rights reserved.
2008-04-09 11:47:06.27 Server      Server process ID is 240.
2008-04-09 11:47:06.27 Server      Authentication mode is WINDOWS-ONLY.
2008-04-09 11:47:06.27 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2008-04-09 11:47:06.27 Server      This instance of SQL Server last reported using a process ID of 4180 at 4/5/2008 11:17:36 AM (local) 4/5/2008 6:17:36 PM (UTC). This is an informational message only; no user action is required.
2008-04-09 11:47:06.27 Server      Registry startup parameters:
2008-04-09 11:47:06.27 Server      -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2008-04-09 11:47:06.27 Server      -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2008-04-09 11:47:06.27 Server      -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2008-04-09 11:47:06.32 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2008-04-09 11:47:06.32 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2008-04-09 11:47:06.50 Server      Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2008-04-09 11:47:06.55 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2008-04-09 11:47:06.64 Server      The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.
2008-04-09 11:47:06.64 Server      Database mirroring has been enabled on this instance of SQL Server.
2008-04-09 11:47:06.64 spid4s      Starting up database 'master'.
2008-04-09 11:47:06.80 spid4s      4 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:07.06 spid4s      SQL Trace ID 1 was started by login "sa".
2008-04-09 11:47:07.10 spid4s      Starting up database 'mssqlsystemresource'.
2008-04-09 11:47:07.13 spid4s      The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid4s      Server name is 'USER-PC'. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid9s      Starting up database 'model'.
2008-04-09 11:47:07.53 spid9s      Clearing tempdb database.
2008-04-09 11:47:08.11 Server      A self-generated certificate was successfully loaded for encryption.
2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv6> 1433].
2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv4> 1433].
2008-04-09 11:47:08.17 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2008-04-09 11:47:08.17 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2008-04-09 11:47:08.17 Server      Server is listening on [ ::1 <ipv6> 1434].
2008-04-09 11:47:09.12 spid9s      Starting up database 'tempdb'.
2008-04-09 11:47:09.47 spid12s     The Service Broker protocol transport is disabled or not configured.
2008-04-09 11:47:09.47 spid12s     The Database Mirroring protocol transport is disabled or not configured.
2008-04-09 11:47:09.53 spid12s     Service Broker manager has started.
2008-04-09 11:51:06.92 Server      CPU time stamp frequency has changed from 1662000 to 199683 ticks per millisecond. The new frequency will be used.
2008-04-09 11:55:07.29 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 11:55:07.29 Server      CPU time stamp frequency has changed from 199683 to 136029 ticks per millisecond. The new frequency will be used.
2008-04-09 12:23:09.84 Server      CPU time stamp frequency has changed from 136029 to 586928 ticks per millisecond. The new frequency will be used.
2008-04-09 12:59:13.12 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 13:07:13.85 Server      CPU time stamp frequency has changed from 586928 to 824822 ticks per millisecond. The new frequency will be used.
2008-04-09 13:47:17.50 Server      CPU time stamp frequency has changed from 824822 to 140502 ticks per millisecond. The new frequency will be used.
2008-04-09 14:07:19.33 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:07:24.80 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:11:25.16 Server      CPU time stamp frequency has changed from 140502 to 1413355 ticks per millisecond. The new frequency will be used.
2008-04-09 15:15:25.53 Server      CPU time stamp frequency has changed from 1413355 to 161989 ticks per millisecond. The new frequency will be used.
2008-04-09 15:19:25.89 Server      CPU time stamp frequency has changed from 161989 to 134822 ticks per millisecond. The new frequency will be used.
2008-04-09 16:23:31.73 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 17:23:37.20 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:11:41.58 Server      CPU time stamp frequency has changed from 134822 to 154257 ticks per millisecond. The new frequency will be used.
2008-04-09 18:23:42.67 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:23:42.67 Server      CPU time stamp frequency has changed from 154257 to 134721 ticks per millisecond. The new frequency will be used.
2008-04-09 18:35:43.79 Server      CPU time stamp frequency has changed from 134721 to 151448 ticks per millisecond. The new frequency will be used.
2008-04-09 18:43:44.51 Server      CPU time stamp frequency has changed from 151448 to 125134 ticks per millisecond. The new frequency will be used.
2008-04-09 19:15:47.35 Server      CPU time stamp frequency has changed from 125134 to 182297 ticks per millisecond. The new frequency will be used.
2008-04-09 19:23:48.08 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 19:27:48.45 Server      CPU time stamp frequency has changed from 182297 to 120770 ticks per millisecond. The new frequency will be used.
2008-04-09 19:47:50.27 Server      CPU time stamp frequency has changed from 120770 to 1370171 ticks per millisecond. The new frequency will be used.
2008-04-09 20:07:52.10 Server      CPU time stamp frequency has changed from 1370171 to 106932 ticks per millisecond. The new frequency will be used.
2008-04-09 20:23:53.56 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 20:35:54.65 Server      CPU time stamp frequency has changed from 106932 to 88924 ticks per millisecond. The new frequency will be used.
2008-04-09 20:51:56.11 Server      CPU time stamp frequency has changed from 88924 to 102106 ticks per millisecond. The new frequency will be used.
2008-04-09 20:59:56.84 Server      CPU time stamp frequency has changed from 102106 to 118592 ticks per millisecond. The new frequency will be used.

SQL Server 2005 agent job runs a SSIS package ( Analysis Services Processing Task) fails

Similar Messages

Maybe you are looking for