SQL server license problem with connections

SQL server license problem with connections

Post by Braden Rowle » Fri, 02 Mar 2001 01:36:36

I have been experiencing some problems with an error message which states
that I have exceeded my five licenses and need to upgrade to a full version.
This is the situation:

In my office, we have a 5 - license SQL server to develop a database
application.  We only have 5 users, and therefore, do not get this error
when working locally.  If I try to log into a client's SQL server remotely,
that is when I get this error.  The client has sufficient licenses for 20-30
workstations to access the server.  This leads me to believe that it is
indeed my 5 - license server which is preventing the connection.

Is my server counting all the connections to the remote server when I try to
connect remotely and update tables?  Is there a way around this?  I don't
see why my license should prevent me from connecting to a remote server when
my client has adequate licensing.

If anyone can help with this issue, I would be very grateful.  As it stands
now, I have to convert the updates to text files, transfer the files, then
log on remotely and import the updates.  This process is obviously much more
time consuming than updating directly from my server.

Braden Rowley
Tenet Information Services
Client Support


1. SQL Server 2000 license overriding SQL Server 7.0 license on separate server

We have the following situation.

Server A is a W2K server (not domain controller) with SQL Server 7.0
installed. This SQL server has an Internet connector license.

Server B is a W2K domain controller with SQL Server 2000 Standard
Edition installed.

Server B has a web app that accesses SQL server on Server A. This web
app does not use the database on Server B.

Web clients accessing Server B have their SQL accesses rejected with the
message "Logon failed. The number of users on this 'Standard Edition'
exceeds the maximum of 10 allowed by the license."

Why does the license on B trump the license on A? How do I fix it?

Q153140 appears to be irrelevant. License Manager doesn't show anything
for the SQL Server 2000 installation.

2. performance problems

3. SQL server license and server connections

4. General SQL Question

5. Licensing problems with sql server and sql server desktop

6. y2k-problem i can not print my reports after 2k

7. SQL server 7 connection licensing

8. Sybase and Visual Basic - what tool?

9. Intermittent connection problems with SQL Server connection.

10. seat license or connection license

11. SQL server license problem

12. SQL Server licensing problems

13. SQL 6.5 on Win 2000 Server Licensing Problem