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 |
|
davidbanner2k
Starting Member
4 Posts |
 Posted - 2008-03-12 : 15:09:57
|
| What would be the impact of replacing the SQL 2005 90 Tools\Binn folder with the SQL 2000 80 tools\binn folder?A colleague of mine did this in a SQL 2005 production environment so that he could still use isql.exe. Unfortunately, users are getting kicked out of the database and I'm thinking the binn folder may be a factor.Thoughts? |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2008-03-12 : 15:17:26
|
maybe you should fire the coleague  well the binn folder doesn't contain any database engine stuff as far as i know but it contains client services like profiler, database mail wizard etc...but one can never be sure.what do the users do when they get kicked out?_______________________________________________Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenpSSMS Add-in that does a few things: www.ssmstoolspack.com |
 |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-03-12 : 15:30:15
|
| Donot touch any folder of SQL Server. |
|
|
|
davidbanner2k
Starting Member
4 Posts |
Posted - 2008-03-12 : 15:48:20
|
quote:
Originally posted by spirit1
maybe you should fire the coleague well the binn folder doesn't contain any database engine stuff as far as i know but it contains client services like profiler, database mail wizard etc...but one can never be sure.what do the users do when they get kicked out?
Unfortunately, I am not the manager...just the guy who was assigned to fix the problem. The users are usually in the middle of something in the application when they get booted out. The SQL server log shows:Login failed for user "username"Error 18456 Severity 14 State 8Oddly enough, it repeats this log entry 6 times for the same user name.The Windows Event Viewer shows:Failure Audit: Login failed for user "username"Also repeats about 6 times every time it happensThanks for your help. |
|
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2008-03-12 : 15:53:03
|
| well copy the binn from another 2005 installation to your overwritten binn.you should be fine. should being the key word and tell your coworker to use sqlcmd_______________________________________________Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenpSSMS Add-in that does a few things: www.ssmstoolspack.com |
|
|
|
davidbanner2k
Starting Member
4 Posts |
Posted - 2008-03-12 : 16:02:51
|
quote:
Originally posted by spirit1
well copy the binn from another 2005 installation to your overwritten binn.you should be fine. should being the key word and tell your coworker to use sqlcmd
Regarding sqlcmd, we have some old tools running in the background that still use isql.exe. Hence, his hacking of the binn folder. I fully intend to restore the correct binn folder, unfortunately the client is using SQL 2005 Workgroup Edition so we'll probably just repair or reinstall. Thanks again! |
|
|
|
|
|
|
binn folder