Quantcast
Channel: Forum SQL Server Database Engine
Viewing all articles
Browse latest Browse all 15889

Firing custom assembly

$
0
0

Hello,

I have an unsafe assembly that executes/exits any exe file the user sets up

To start an application would be:
"EXEC sp_myassembly @path='notepad.exe", @start=1;"

To exit:
"EXEC sp_myassembly @path='notepad.exe', @start=0;"

The problem that I have is that when is being started, the user name that interacts is "SYSTEM" and is not visible to the desktop. I had this problem before and the solution was to check an option under the SQL server's service called: "Allow service to interact with desktop". There is no problem at one of the servers that run Windows 2003 Server, but now there's a new server with Windows 2008 Server O.S. that doesn't allow to interact with desktop eventhough I followed the same steps like I did on Windows2003's...

I got rid of an annoying popup by disabling a service called "Interactive Services Detection" and still nothing.

What can I do in order to make it work?

NOTE: This procedure runs under a scheduled job every morning (around 01-01:20am).

Thanks


JaimePR,


Viewing all articles
Browse latest Browse all 15889

Trending Articles