File system error when trying to log output of XMLA script in Error Configuration


i'm having trouble following xmla script:

<batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine"><errorconfiguration xmlns:xsd="http://www.w3.org/2001/xmlschema" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2" xsi:type="errorconfiguration">
<
keyerrorlogfile>\\dfspath\logfile.log</keyerrorlogfile>
<
keyerrorlimitaction>stoplogging</keyerrorlimitaction>
<
nullkeynotallowed>ignoreerror</nullkeynotallowed>
</
errorconfiguration>

<process>
<
type>processfull</type>
<
object>
<
databaseid>myssascatalog</databaseid>
<
dimensionid>mydimension</dimensionid>
</
object>
</
process>
</
batch>


error message: <error errorcode="3238133761" description="file system error: following error occurred while opening file '\\dfspath\logfile.log': access denied. ." source="microsoft sql server 2005 analysis services" helpfile="" />

here i've done:

1. tried script against analysis services running on 3 machines, xp 32-bit box, an xp 64-bit box, , server 2003 32-bit box.

2. on of these machines, analysis services process running under domain account. domain admin , have full access dfs path locations i've tried.

3. run script on each of them.

4. on the xp 32-bit instance, works fine. on other machines, error message:
<error errorcode="3238133761" description="file system error: following error occurred while opening file '\\dfspath\logfile.log': access denied. ." source="microsoft sql server 2005 analysis services" helpfile="" />

from can tell, common difference between instance works , don't server or server-like (i understand xp 64-bit not simple 64 bit version of xp 32-bit, more scaled down version of server2003 64-bit). therefore, not think issue analysis services, rather security issue regarding services , access rights external paths.

things i've tried without success:
- mapping log location drive.
- adding dfs path trusted sites (our dfs listed in internet zone).
- adding dsf path caspol fulltrust code group.
- giving "everyone" access dfs path.
- trying output log different shared path, \\somemachine\asharedfolder

does have ideas? appreciated! thanks.
keith

it worked writing local path. found solution last night:

i've been stumped time on , domain security setting.
this affect service running on server or xp64 box trying access
a network path. here obscure fact regarding services running on servers:

when set them run user, don't run that
user in normal sense. instead use user account "delegate"
for service. there account setting under "active directory users
and computers" domain admin snap-in called "account trusted delegation".
when checked box , let settings propagate, problem went away.

thanks help.

keith



SQL Server  >  SQL Server Analysis Services



Comments

Popular posts from this blog

Conditional formatting a graph vertical axis in SSRS 2012 charts

Register with Power BI failed

SQL server replication error Cannot find the dbo or user defined function........