Untill a few days back everyting was fine but since recently my DTS which was scheduled to process a cube now fails. I looked at the detais of the scheduled job and in summary this is the message that it shows:

....Error string: Unable to connect to the registry on the server (UKT19), or you are not a member of the OLAP Administrators group on this server....

I have not made any changes and thus do not understand this problem. The strange part is that when I manually run the DTS, it works fine.

Any clues??

Thanks.

************************************************** ********************
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

Hi

One of the differences between running the DTS using Enterprise Manager and
running the DTS as a job, is the user context. When you use Enterprise
Manager (ore command prompt), the package is run in the context of the logon
user (usually your personal account). When you execute through a job, the
package is run with the creditentials of the startup account for the SQL
Server Agent Service.

Check which user creditentials the agent runs under. Then check the users
memberships on the server.



"Learner" wrote:

The other possibility is that multiple instances may be trying to do an
administrative function at the same time. See this kb article.
http://support.microsoft.com/default...b;en-us;814414
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Markus" <Markus (AT) discussions (DOT) microsoft.com> wrote

the scheduled job and in summary this is the message that it shows:
server....

I am having the exact same problem. Running DTS package with "Process Cube"
task works fine interactively, but fails when scheduled via SQL Agent. I
understand that the difference is security context, but for the life of me I
can't figure it out. I made sure that SQL Agent account is a member of
"OLAPAdministrators" and Analysis Services account is "sysadmin" on SQL
Server (although this is likely overkill), but I am still getting the same
error.

"Learner" wrote: