Jordan (none@here.com) writes:
> Windows 2003 server with SQL 2000 latest SP. SQL 2000 is installed in
> mixed mode. I have packages like Microsoft Dynamics that have their own
> program security that work fine, however I have this one package that
> also has its own program security and no users other than Domain Admins
> can get into the program.
>
> Domain Admins can launch the program and get to the programs logon
> screens, however all other users can't even get into the programs logon
> screen without getting a "Primary Server Connection Could not be
> established" error message.
Can non-domain admins connect to SQL Server through say Query Analyzer or
OSQL, using Windows authentication?
I have no idea what this package is doing, and since the error message
it generates appears to be its own, it's difficult to say what the
message actually reflects. Since you say that users cannot get to the
primary logon screen, this would indicate that they do not even reach
SQL Server. But it is difficult to see how that could be affected by
whether they are admins or not.
I think the best would be to contact the support provider for this
package. If this is non-existent and you have to troubleshoot this
yourself, I suggest using Profiler to see it makes any connection
under the hood. Or search on the web to see if other have had issues
with this package.
--
Erland Sommarskog, SQL Server MVP, esquel RemoveThis @sommarskog.se
Links for SQL Server Books Online:
SQL 2008:
http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005:
http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000:
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx