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.
| Author |
Topic |
|
Blav82
Starting Member
2 Posts |
 Posted - 2009-07-01 : 14:13:49
|
| Hello,I have an application that runs on 1 server and connects to another to dump the data. The first has an app with this ConnStr to connect to the sql...[SQL Server]SQLConnStr="Provider=SQLOLEDB.1;Persist Security Info=False;User ID=crawler;password=password;Data Source=zeus;Initial Catalog="InputDatabaseName="crawler"InputURLTableName="url"InputKeywordTableName="client_keyword"InputSpecialWordsTableName="special_words"OutputDatabaseName="crawler"OutputTableName="results"OutputIndexName="results_non_duplicate"OutputTableKeywords="results_keywords"OutputIndexKeywords="results_keywords_non_duplicate"SearchStatusTableName="searchstatus"VisitedLinksTableName="visitedlinks"VisitedLinksIndexName="visitedlinks_non_duplicate"The application worked fine until Saturday, now it failes and I get an error saying that " is not a valid integer value. At first I thought it was because the - Initial Catalog=" - however, it has always been that way and not changed.No updates of any kind have been done to either server. I also tried to modify - Initial Catelog=[tablename] - but when i do that i get an error saying "Unable to connect to the database, make sure the SQL connection File exist!" and a failed SQL authentication error shows in the SQL log. I then reset the password, and make sure the sql user was not logged out- still nothing. I've been stairing at this all day, Please anyone- help with ideas,Thanks |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2009-07-01 : 14:16:19
|
| Initial Catalog is the database name that you want to connect to. If yours is blank and it worked in the past, then it's because the database that you want to connect to is the default database on the crawler acocunt.I really don't think this is a connection string issue as that integer error has nothing to do with connecting. I think you've encountered an application bug and will need to debug it.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog"Let's begin with the premise that everything you've done up until this point is wrong." |
 |
|
|
Blav82
Starting Member
2 Posts |
Posted - 2009-07-01 : 15:03:29
|
| Thank you! It was a bug- the application could not process any cells with blank values- I replaced all blank cells with NULL values and the application started right up. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
Sql 2005 ConnStr authentication issue?