Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 Transact-SQL (2000)
 unable to execute code!

Author  Topic 

Girlnet
Yak Posting Veteran

77 Posts

Posted - 2009-10-01 : 11:14:59
I have this really weird issue that I just can't figure out. I've written a little program (windows forms) that updates a table, renames a file, and sends an email. It works perfectly on the webserver and three other PCs.

Yet when I install the program on a server (windows 2003) with sql on it and run the program - the table never updates. The file is renamed, the email is sent - but no table updates. No errors either. Nothing.

Does anyone know why this would happen? Is there something on the server that is preventing the stored procedure from running?

webfred
Master Smack Fu Yak Hacker

8781 Posts

Posted - 2009-10-01 : 15:07:16
Is your program connecting to the server that you are looking for updates performed?


No, you're never too old to Yak'n'Roll if you're too young to die.
Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2009-10-01 : 15:51:56
is there any instead of update trigger existing on table in that server db?
Go to Top of Page

Girlnet
Yak Posting Veteran

77 Posts

Posted - 2009-10-02 : 15:13:57
Thanks very much for the ideas.

The program is sitting on the sql server. So it's not doing any remote connections. And no, to the triggers.

I'm thinking maybe it's a permission thing. It just seems weird that I can get this to work with other PC - but not the one I need it on.

I've tried changing the authenication modes but I'm still not getting anything.

Go to Top of Page

TG
Master Smack Fu Yak Hacker

6065 Posts

Posted - 2009-10-02 : 17:17:48
- Check the event viewer (application log) of the machine that hosts the program. If there are any sql errors (like permission issues) they should show up there.

- Set up a sql profiler trace to see what commands (if any) are making it to the sql server.

- Test connectivity for that application environment with a simple sql command like "select getdate()"

Be One with the Optimizer
TG
Go to Top of Page

Girlnet
Yak Posting Veteran

77 Posts

Posted - 2009-10-05 : 08:31:15
Turns out it was my connection string (using Windows forms). I added "Persist Security Info=True" and it worked. Weird how it worked on the other 3 pcs but not on the server. Also, MSDN says do use use "True" - yet I had visual studio rebuild the connection string and it inserted it by default.

At least I can go forward now. Thanks everyone! You guys are great here - as usual!
Go to Top of Page
   

- Advertisement -