Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

SQLOLEDB connection in a NS task...

Updated: 25 May 2010 | 3 comments
gpglang's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

This is really strange and I hope somebody can bring some sence to this

I have made a vbs script with a logging sub-routine:
- reads MachineGUID from Registry
- uses this to find some information in the hd_asset_view
- writes this data into another part of the registry
Every now and then I call the log-subroutine to see which values are used, etc
When I execute this on a client computer with cscript or wscript it runs suberb.

Now I need this to run real-time when I choose to. So a NS task seemed to be the best choice
First I entered this vbs script into the task, which failed.
I changed it to a command task that:
- copies the vbs script to %tmp%
- executes : start /wait wscript.exe temp3.vbs
- copies log file back to the NS-server
- pause
Then I saw what went wrong, but I do not understand.
WSH msg pops up with error: Login failed for user 'TEST\XPSP3$' (TEST is domain and XPSP3 is hostname client) code 80040E4D.

So Task is running on "Altiris Agent Credentials".
I changed that to specific user and used the same credential... IT WORKED!!!

So:
- locally it runs no matter what user
- as task with "Agent Credentials" is fails
- as task with specific user (the SAME as Agent Credentials!!!) is works!

Please enlight me... I am flabbergasted here. Bug by design?

Comments

Pikoshi's picture
10
Jul
2009
2 Votes +2
Login to vote

What I suspect and it looks

What I suspect and it looks like from our setup here is that the NS agent is running as the local system account, instead of with a specific user name.  If you go to a client computer, bring up the services running on the machine, then look at the log on tab of the agent service you will see it running as the local system account.

If your question was answered, mark the anwser as the solution
Give thumbs up if you found a post helpful

jharings's picture
10
Jul
2009
0 Votes 0
Login to vote

Excellent idea Pikoshi!

If I thought it would do any good, I'd slap myself upside the head (but who knows what it would knock lose).

The agent should be running with local system by default, and depending on what you are trying to do here, local system wouldn't have any access to a network location, or a database connection (unless of course it was local, and you had rights setup that way).

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

gpglang's picture
13
Jul
2009
0 Votes 0
Login to vote

Thx for this picture...

Thx Pikoshi... you made the picture complete
jharings, I did the slapping as "I deserved it".. my bells are still ringing ;-)
Guido

Guido Langendorff
Arrow ECS Netherlands
Netherlands

Select "Mark as Solution" when it has resolved your problem.
Give a "Thumps up" when you like the comment or "Thumps down" when n