February 19, 2008 at 3:24 pm
I have an application that connects to SQL 2K, after the move of the DB's to a new server,
I get a message when in the application when clicking on a link that is supposed to open the customer's info in a browser: "unable to open http://servername/scripts/idi/distsumsetdirect.idc?Acctnum=XXXXX. Cannot download the information you requested". How would I fix this? I restored the website in IIS from tape backup. Same error.
February 19, 2008 at 8:31 pm
Did you change your link string accordingly?
February 19, 2008 at 8:38 pm
No cluster. just the server name I am referring to
I do not know how to change a link string. How do I do that?
February 20, 2008 at 6:57 pm
How do I change link strings?
February 20, 2008 at 8:33 pm
In the .IDC file there is a setting named Datasource. That is an ODBC Data Source Name (DSN). The DSN contains the name of the database server. If that hasn't been changed it would still be trying to access the old server. To change, use the Control Panel applet named ODBC Adminstrator and look for the DSN from the .IDC file.
February 20, 2008 at 8:52 pm
Datasource: WEB SQL
Username: ReadOnlyIntranet
Template: DistSumSetDirect.htx
SQLStatement:
+SELECT Core.dbo.Customer.CustID
+ FROM Core.dbo.Customer
+ WHERE (Core.dbo.Customer.CustID=%AcctNum%)
This is what the idc file says.
There are a about 20 idc files in the scripts/idi folder. The Datasource says Web SQL. That is not the name of my sql server. Do I remove Web SQL and type in the name of my sql server?
February 20, 2008 at 9:11 pm
So Do I create a DSN? User, System, or File DSN? I wish I knew how to fix this.
Its driving me crazy and I have users screaming at me to fix these links on the intranet.
February 20, 2008 at 9:36 pm
Did you see a DSN named "WEB SQL" in the ODBC Administrator?
If it's there you'd open that up to change the server name.
February 21, 2008 at 6:36 am
No its not there. Do I need to add it then?
February 21, 2008 at 8:53 am
That's where I'd start. Add a System DSN named "WEB SQL" on the IIS server that hosts the IDC files.
If it's still not working after that posting additional information such as your server OS and IIS version might help.
February 21, 2008 at 9:09 am
Below is what the .idc file looks like....
Datasource: Web SQL
Username: ReadOnlyIntranet
Template: DistSumSetDirect.htx
SQLStatement:
+SELECT Core.dbo.Customer.CustID
+ FROM Core.dbo.Customer
+ WHERE (Core.dbo.Customer.CustID=%AcctNum%)
I added a system DSN - Web SQL pointing to the local SQL Server. It did not work.
It is Windows 2000 SP4, on SQL2000 SP4.
This all started b/c I had to rebuild the server. Formatted the drive and reinstalled everyting.
Performed a restore on all databases except the system databases (MSDB, Model, Master, Tempdb, and Northwind). I hvae backups of the system db's but I cannot restore them if I need to b/c the backups are on SP3a and the SQL2000 is on SP4 now b/c I upgraded to SP4. Is this a problem now?
February 21, 2008 at 11:34 am
Can you login to the SQL server using Query Analyzer with the 'ReadOnlyIntranet' username and run the query that's in your IDC file?
Another thing to check is that the website is configured to run "Scripts and Executables".
February 21, 2008 at 11:40 am
I just noticed that the Datasource: Web SQL is not right. Shouldnt the Datasource: be the name of the server? Web SQL is not the name of the SQL Server. I dont know the password for ReadOnlyIntranet. Is ReadOnlyIntranet a domain or local account?
February 21, 2008 at 4:15 pm
No, the DSN is a logical name that holds which driver and server to connect to. The DSN name you see in your IDC file just has to match a valid system DSN.
Can you access the database using ANY account from Query Analyzer? There's not much point in going further until you can do that.
Domain or local? If you see a 'ReadOnlyIntranet' account in your domain that answers that question.
The lack of a "Password:" field would seem to indicate that the 'ReadOnlyIntranet' account was configured as the account for Anonymous login in IIS for that website. That account would also have a matching server login in SQL.
Also, if you recreate the server login in SQL you may have to re-associate that with the database user for your database depending on whether that was originally a local or domain account.
Another problem you might run into is that you didn't mention restoring the IIS metabase which contained your websites configuration information.
Good luck.
February 21, 2008 at 5:30 pm
Thanks , but I got it working. All links are querying the databases as they should.
The site was created in Frontpage 2K from what it looks like. Re establishing the System DSN and
connecting the links in FP to the db seemed to work
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply