SQLBrowser 将无法启动
Windows Server 2003 x64 上的 SQL Server 2005 x64，具有多个实例（默认 + 2 个指定实例）。工程师将服务器移至不同的域。从那时起，无法让 SQLBrowser 启动。仍然能够查询默认实例，并且可以通过端口（TCP：主机名，端口#）访问命名实例。在服务器上时，可以使用 SSMS 连接到实例，从这个角度来看一切都很好。 SQL Server 日志中没有错误。
当 SQLBrowser 启动时，EventViewer.Application 中的一个条目表示指定实例之一具有无效配置，但我无法弄清楚什么是无效的。启动继续，下一条消息显示“SQLBrowser 服务无法建立 SQL 实例和连接发现。”接下来，它启用实例和连接发现支持；接下来，是关于具有无效配置的同一命名实例的另一条消息；然后一个事件表明 SQLBrowser 已启动；最后，一个事件显示 SQLBrowser 服务已关闭。
我让 SQLBrowser 通过临时重命名注册表项来解决第一个命名实例的问题，现在可以通过名称而不是端口来访问第二个命名实例。尽管如此，仍无法按名称访问第一个命名实例。
建议？
SQL Server 2005 x64 on Windows Server 2003 x64, with multiple instances (default + 2 named). Engineers moved server to a different domain. Since then, cannot get SQLBrowser to start. Still able to query the default instance, and can access named instances by port (TCP:hostname,port#). When on server, can use SSMS to connect to the instances, all is well from that perspective. No errors in the SQL Server logs.
As SQLBrowser is starting, an entry in EventViewer.Application says that one of the named instances has an invalid configuration, but I haven't been able to figure out what is invalid. Startup continues, and next message says "The SQLBrowser service was unable to establish SQL instance and connectivity discovery." Next, it enables instance and connectivity discovery support; next, another message about that same named instance having an invalid configuration; then an event says that SQLBrowser has started; last, an event shows the SQLBrowser service has shutdown.
I got SQLBrowser to get past the issue with the first named instance by temporarily renaming a registry entry, and now the second named instance can be accessed by name rather than port. Still, cannot access the first named instance by name.
Advice?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
事实证明，问题是卸载了 2000 的几个实例后留下的一些旧密钥。Microsoft 指导我删除了这些密钥，SQLBrowser 立即启动了。
The problem turned out to be some old keys left behind by uninstalls of a few instances of 2000. Microsoft walked me through removing the keys, and SQLBrowser fired right up.