This is a discussion on Re: DSO and/or xp_cmshell permissions within the SQL Server Data Warehousing forums, part of the Microsoft SQL Server category; --> still no luck! "oj" <nospam_ojngo@home.com> wrote in message news:O8fC96WUDHA.1872@TK2MSFTNGP12.phx.gbl... > See if this article helps... > > http://support.microsoft.com/default...;en-us;Q264155 > ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| still no luck! "oj" <nospam_ojngo@home.com> wrote in message news:O8fC96WUDHA.1872@TK2MSFTNGP12.phx.gbl... > See if this article helps... > > http://support.microsoft.com/default...;en-us;Q264155 > > -- > -oj > RAC v2.2 & QALite! > http://www.rac4sql.net > > > "chris trailer" <wlieberman@xtiva.com> wrote in message > news:OPNj1xWUDHA.372@tk2msftngp13.phx.gbl... > > Hi, > > > > I have a vb app that is executed from the xp_cmdshell stored proc. Within > > the exe is the use of DSO to process some cubes. My SQL2K Ent SP2 server > > uses the System account to start the sql service. The system account has > > full control of the vb .exe. > > > > When i run the script from query analyzer on the machine i get an error > > reported back from the vb app: Object variable or with block not set, the > > source is DSO. However when i run the app via a command prompt on the > same > > machine it runs fine. > > > > Of course in the test environment it runs fine from tsql. > > > > Could this be permissions on the OLAP server? > > > > Any thoughts would be appreciated. > > > > .chris. > > > > > > |
| ||||
| Thanks... i actually figured it out. The Test environment had permissions on the OLAP server that put the Everyone "user" intot he Local OLAP Administrators group. Don't know why it was setup like that, but i did have to do with the olap permissioning. However, i cannot allow that in production, so i'll be setting up the sql service AD account and put that account into the olap admin group. Thanks for your efforts and quick attention!!! ..c. "oj" <nospam_ojngo@home.com> wrote in message news:epW586gUDHA.1776@TK2MSFTNGP09.phx.gbl... > You need to verify the account in which sqlserver is started. If the vb app > is doing something on a network shared, this sqlserver account must also > have access to the network resources. This is why it's important to use a > domain account as the startup account for sqlserver. So far, we're only > talking of the case where the user who invokes "xp_cmdshell" is also part of > sqlserver sysadmin group. If this user is not then the proxy account will be > used. That's the reason for the article I posted. > > g'luck. > -- > -oj > RAC v2.2 & QALite! > http://www.rac4sql.net > > > "chris trailer" <wlieberman@xtiva.com> wrote in message > news:uTy3q1gUDHA.2360@TK2MSFTNGP10.phx.gbl... > > still no luck! > > > > > > "oj" <nospam_ojngo@home.com> wrote in message > > news:O8fC96WUDHA.1872@TK2MSFTNGP12.phx.gbl... > > > See if this article helps... > > > > > > http://support.microsoft.com/default...;en-us;Q264155 > > > > > > -- > > > -oj > > > RAC v2.2 & QALite! > > > http://www.rac4sql.net > > > > > > > > > "chris trailer" <wlieberman@xtiva.com> wrote in message > > > news:OPNj1xWUDHA.372@tk2msftngp13.phx.gbl... > > > > Hi, > > > > > > > > I have a vb app that is executed from the xp_cmdshell stored proc. > > Within > > > > the exe is the use of DSO to process some cubes. My SQL2K Ent SP2 > > server > > > > uses the System account to start the sql service. The system account > > has > > > > full control of the vb .exe. > > > > > > > > When i run the script from query analyzer on the machine i get an > error > > > > reported back from the vb app: Object variable or with block not set, > > the > > > > source is DSO. However when i run the app via a command prompt on the > > > same > > > > machine it runs fine. > > > > > > > > Of course in the test environment it runs fine from tsql. > > > > > > > > Could this be permissions on the OLAP server? > > > > > > > > Any thoughts would be appreciated. > > > > > > > > .chris. > > > > > > > > > > > > > > > > > > > > |