March 24, 2009 at 10:28 pm
I want to configure a alias, and couldnt find any protocols listed in SQL server native client configuration inside sql server configuration manager.
Any Help is appreciated
March 25, 2009 at 12:56 am
What you mean no protocols if the Protocol NET Libraries are missing you'll have to reinstall to get them fixed.
To add an aliases do this:
1) Run SQL Server Configuration Manger.
2) Select SQL Native Client 10.0 Configuration
3) Select Aliases
4) Right click, New Alias.
5) Enter in Alias Name, Port (1433 default), enter in current server name.
6) Click OK.
Thanks.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
March 25, 2009 at 1:03 am
Thanks for the reply,
i am aware of configuring alias but i cannot find any protocols in the client protocols list. I never came across such scenario, i was trying to avoid reinstall since it is a production box.
March 25, 2009 at 1:07 am
Hmmm on your production box you don't have any NET libraries? But it is working? That is strange; I ran into it once but my production box was not working. And only article I could find (sorry don't have link) recommend reinstalling. Sorry.
Mohit.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
March 25, 2009 at 9:58 am
Thanks for reply,
I have no clue because i just came on board yesterday (server was setup a week ago ) and saw this, i guess have to re-install!!!
Is there any other alternative: all i need is to pull some data from remote SQL server via ssis.
March 25, 2009 at 10:53 am
The NET Library information resides in following registery key:
HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib
Under there you should have folder for each protocol ..
Attached is Reg file for that you can try importing it, but I am afarid it might not work.
Permission on that key are inherted from parent key.
Thanks.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
March 25, 2009 at 4:12 pm
Thank You very much i really appreciate your time. as you said its a big issue, Just found that my team member moved sql server installation from c: to d: drive but registry for client components still points to c: I guess we will have to do a new install.
March 25, 2009 at 4:43 pm
I have moved SQL installs from one drive to another; but never binaries. I usually only relocate the data/log files if needed.
I would ask your co-worker not to do that in future heh, I think it's more headach then you want. SQL makes man registery entries to register services and such properly and if you don't repoint properly number of things can break.
Since he moved the binaries you might need to look at manual uninstall, please reference http://support.microsoft.com/kb/909967.
Thanks.
Mohit.
Edit: Included Manual Uninstall Instructions.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply