User Profile

Collapse

Profile Sidebar

Collapse
jdaelhousen
jdaelhousen
Last Activity: Nov 3 '08, 05:22 PM
Joined: Jul 18 '08
Location:
  •  
  • Time
  • Show
  • Source
Clear All
new posts

  • No offense taken, however I am a developer and know how to write .net exe modules and have been doing so for several years. What I'm not familiar with are account permissions because I'm not a network administrator. And don't take this the wrong way because I appreciate your help, but other than the impersonation class that didn't fix the issue, you didn't suggest anything that I haven't already tried. So I think I need to present my issue to...
    See more | Go to post

    Leave a comment:


  • Well the impersonation code didn't seem to work. After referencing the ImpersUser dll in my project, I tried running the 1 line of code to impersonate as the NT AUTHORITY\SYSTE M user. No errors were thrown so i'm assuming that the impersonation as NT AUTHORITY\SYSTE M went through ok, but I still could not open up the access database. I'm really stumped here.
    See more | Go to post

    Leave a comment:


  • Thanks, kenobewan. I'll give this a whirl later tonight when I get some time and reply back with my results. It does appear from first glance that this might be the issue.

    Thanks again....
    See more | Go to post

    Leave a comment:


  • I apologize, my previous reply was a bit confusing after I reread it. First to answer your question, I am planning to automate this task with the scheduled task only on the server that the exe is currently sitting. It will not be deployed anywhere else.

    But I think I might have miscommunicated what's actually going on here. Let me take a step back and reconfirm what's going on:

    If I double click the .exe everything...
    See more | Go to post

    Leave a comment:


  • Yes, it does come down to permissions which is what I'm trying to figure out. Let's start simpler:

    I'm an admin on the server. If the .exe works fine and can open instances of MSAccess when I double click it, why does it fail to instantiate MSAccess when a scheduled task runs the executable as the NT AUTHORITY\syste m user? What am I missing here?

    Thanks,

    John...
    See more | Go to post

    Leave a comment:


  • Accessing MSAccess dll's from a Windows Scheduled Task

    I have a bit of a problem I'm hoping someone can shed some light on...

    I have a VB.Net console application written in VS 2003 that produces a .exe file that now sits on a Windows 2000 server directory. This exe does the following 3 things:

    1.) Using the VB Interaction SaveSetting() method, it programmaticall y updates the system registry under the HKEY_CURRENT_US ER\SOFTWARE key and saves a directory location used by...
    See more | Go to post
No activity results to display
Show More
Working...