I was trying to fix a broken subscription and when I tried to delete the subscription I got an error message that said 'SQl replication does not support nicknames such as """" or local. I did notice that when I look under the Sql server group , my publisher is listed as 'Local' and not the name of the server. I looked at a 3.1 amnd it looks correct. I have several installs that all look the same.
You can correct it by using dbhelper but you cannot do it manually. Has anyone seen this behaviour and how do I correct it. LHOST file is okay.
That's just how the SQL Enterprise Manager software is looking at your SQL server. By default, when you fire up SQL Enterprise Manager on the box itself, the SQL Server instance on the machine itself shows up as local. If it's causing a problem, you can deregister the "local" SQL server and then reregister it as its true hostname, and this should eliminate the error.
Your right it is scary but thats what I did. My concern is where did this bug show up as I have 3.3.3 systems that are okay and some that are not. The other thing is you can use 'dbhelper' to recreate but I find it flakey sometimes and like to rebuild manually.
The lhosts file was okay and has been from day one. I have 4 other sites in the same state.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.