April 14, 2011 at 12:13 pm
SQL Server Native Client 10.0 is on both machines although the versions were different. I've undated the version on the script machine and it is now the same as SQL Server machine.
I've tested various server settings and still get the same error.
Don't know if it's relevant but SQL is on a 64bit machine and the VBS script is on a 32bit.
April 14, 2011 at 12:23 pm
Processor architecture shouldn't matter for connections.
I've run the script in my environment (different query) and it has worked. I'm not sure what's happening in your environment.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
April 14, 2011 at 12:33 pm
Jack Corbett (4/14/2011)
I've run the script in my environment (different query) and it has worked. I'm not sure what's happening in your environment.
Ditto.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
April 14, 2011 at 1:54 pm
Thanks for trying everyone. Time to take a different route I think.
April 15, 2011 at 3:29 am
I discovered the problem. I followed the method below to set up virtual directories and FTP. I changed the FTP user password today and the site went down and couldn't access IIS features for the site receiving a user error. I then re-created the site with no FTP user and the .VBS script works fine with just the server IP. I don't understand what exactly is happening but it seems the user I created for FTP was restricting access from the remote .VBS script. If anyone can clarify what happen and perhaps a better way to set up FTP that would be appreciated.
http://weblogs.asp.net/owscott/archive/2004/02/05/68423.aspx
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply