Processing of AS2005 cube from Integration Services package: Operation completed with 882 proble

Hi!

I did not now if I should post it in the Integration Services forum, but I believe this post is more AS related. Anyway, I am processing my cubes in SSIS after some loading of data. I use the SSIS log provider for SQL Server to log errors, and I get the following error message in the message column of a row in sysdtslog90:

"Server: Operation completed with 882 problems logged."

I wonder, where can I find this log? Is there some default location in AS or do I have to enable another log event than OnError or OnWarning in SSIS?

Thanks!

I'm guessing I'm looking for the Dimension key error log path when it is set for (default).

I found something here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1284202&SiteID=1

Seems like you have to set the location in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Config\msmdsrv.ini. Now I get a key error logfile, but it is empty =/. I've restarted the AS service and set the ErrorLog elements in the ini to:

<ErrorLog>
<ErrorLogFileName>OLAPErrorLog.log</ErrorLogFileName>
<ErrorLogFileSize>4</ErrorLogFileSize>
<KeyErrorAction>0</KeyErrorAction>
<KeyErrorLogFile>KeyErrorLogFile.log</KeyErrorLogFile>
<KeyErrorLimit>0</KeyErrorLimit>
<KeyErrorLimitAction>0</KeyErrorLimitAction>
<LogErrorTypes>
<KeyNotFound>1</KeyNotFound>
<KeyDuplicate>0</KeyDuplicate>
<NullKeyConvertedToUnknown>0</NullKeyConvertedToUnknown>
<NullKeyNotAllowed>1</NullKeyNotAllowed>
</LogErrorTypes>
<IgnoreDataTruncation>0</IgnoreDataTruncation>
</ErrorLog>

I've also tested the following without success:

<ErrorLog>
<ErrorLogFileName>OLAPErrorLog.log</ErrorLogFileName>
<ErrorLogFileSize>4000000</ErrorLogFileSize>
<KeyErrorAction>1</KeyErrorAction>
<KeyErrorLogFile>KeyErrorLogFile.log</KeyErrorLogFile>
<KeyErrorLimit>1</KeyErrorLimit>
<KeyErrorLimitAction>1</KeyErrorLimitAction>
<LogErrorTypes>
<KeyNotFound>1</KeyNotFound>
<KeyDuplicate>1</KeyDuplicate>
<NullKeyConvertedToUnknown>1</NullKeyConvertedToUnknown>
<NullKeyNotAllowed>1</NullKeyNotAllowed>
</LogErrorTypes>
<IgnoreDataTruncation>0</IgnoreDataTruncation>
</ErrorLog>

More info here, but it does not get you that much wiser: http://technet.microsoft.com/en-us/library/ms174827.aspx

Seems like you do have to set the ErrorLog properties manually for each cube (Process > Change Settings > Use custom error configuration).

Process task hangs running bcp

We are attempting to use Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00 to run a BCP command from a Process task. We are able to do so without a problem when running it interactively, but when run as a SQL Server Agent job the bcp process never completes and the job hangs indefinitely.

We also tried using a Script task for this, with the same result.

Has anyone else run into this problem?

Thanks,

Ron

What happens if you run it from dtexec? (i.e. from the command-line).

If it executes successfully using dtexec then its most likely a security issue.

-Jamie

|||

Jamie,

Thank you for your reply. Yes, the BCP processing works fine when I run the package interactively in Management Studio. However, I don't see how it could be a security issue, because the account that SQL Server Agent is running under is in the Administrators group on the server, and the BCP output is going to a share on that same server. I double checked, and the Administrators group has full control permission on both the share and the folder.

Is there anyone that has been successful in running BCP in an SSIS Process task under SQL Server Agent?

Thanks,

Ron

|||this link might help: http://support.microsoft.com/kb/918760|||

Thank you for the suggestion, Duane. In this case, though, the package executes, it just hangs on the Process task that executes the BCP command.

The security level of the package is DontSaveSensitive, and the Agent service account has full permissions to the file system, so it does not seem likely that lack of permissions is the issue.

Ron

|||

We stumbled upon the solution for this, but it does seem that a glitch in SSIS may be the root cause.

When running BCP in a Process task, the path to the BCP executable must be provided. When running a package interactively a UNC path name to bcp.exe works fine, but when run as a job the UNC path name somehow causes the process to hang indefinitely. Changing the notation from "\\<servername>\c$\Program Files\..." to "c:\Program Files\..." fixes the problem.

Is there any valid reason that this should be the case?

Thanks,

Ron

Process Cube using Integration Services

Hi,

I want to process my cube using Process Data and Process Index instead of the Process Full. However, after configuring the 2 Analysis Services Processing Tasks (one for process data and the other for process index) and were executed sequentially (process data first then process index), I got this error:

Errors in the metadata manager. The process type specified for the CASES cube is not valid since it is not processed

Have I done the right thing?

The reason why I prefer using the Process Data and then Process Index, it's because it is much faster than the latter.

cherriesh

It's interesting that you're seeing an error, because 'Process Full' is nothing more than 'Process Data' and then 'Process Index' under the covers.

I'll admit that I was skeptical that executing the two sequentially was faster for you than process full, but I found an Analysis Services best practices whitepaper that confirmed this could happen.

http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/ssaspbpr.mspx

Are you sure you are using 'Process Data' on the cube object itself and not a measure group or partition?

Also, you may want to post this question in the Analysis Services forum.

|||

Hi,

I did the process data for both the dimensions and cube. and did also process index for the two.

am i right there?

cherriesh

|||

I think that might be your issue. If it processes a dimension after the cube that would explain the error message you received on the step to process the index. Try doing process data for just the cube (it should do the dimensions as part of this).

Process AS2000 DataBase from SQL2005 Server Agent

Hi!

Want to process AS2000 DataBase that is located on one server

from 2005 ServerAgent that is located on other server.

SQL2005 Integration Services allows processing only of 2005 OLAP Databases.

I could send an xmla-script to as2000 from a task o ServerAgent2005 but

I've read that AS2000 doesn't support xmla scripts with process command.

How could I do this without migrating 2000 databases to 2005?

Thank you in advanced. Mastroyani .

You could create a DTS package that contains the AS2000 processing tasks you need. The package could the be run with dtsrun.exe from your agent job.|||

The problem is, that on AS2000 machine there's only AnalysisServices installed

(No SQL Server and also no DTS).

Are there some other possibilities?

|||You have an option of writing a small DSO program which processes whatever you need, and then you can launch this program from DTS on any machine you want to.|||Спасибо! :) Так и сделал.