Can I administer SQL 2000 MSDE Release A from SQL Server's Enterprise
Manager (EM) located on another machine on the same network?
When I try to do this the EM setup wizard locates the host running MSDE but
it cannot connect either with Windows authentication or the strong password
created during MSDE's install.
EM can see other instances of SQL Server 2000 on the network (these are not
MSDE).
MSDE is running on XP (SP1) and EM is running on W2K workstation.
Many thanks.
Even if you can figure out your connectivity problem, it's probably not
legal anyway. From the Appropriate Uses of MSDE FAQ at
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
Q. Can I use SQL Server tools and services in conjunction with MSDE?
A. You can only use SQL Server tools and services in conjunction with
MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
Standard Edition, or Enterprise Edition), and if you are using MSDE in
conjunction with a properly licensed copy of SQL Server 2000. Visit the How
to Buy page for information on obtaining a valid SQL Server license.
Note: The tools and services included with SQL Server Developer
Edition may not be used to manage production server environments.
The following utilities are installed by the MSDE setup application
and are provided without restrictions for use with the copy of MSDE that is
installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe, osql.exe,
sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The
dtsrun.exe utility is also provided, but can only be used to run existing
Data Transformation Services (DTS) packages against the copy of MSDE
installed by your application; it cannot be used to develop new DTS
packages.
There's not enough information in your post to determine whether or not it's
legal, but in the vast majority of instances it's not and I'm told that it
requires a room full of lawyers and white board to figure out. There are a
bunch of 3rd-party tools out there that might be of use. Have a look at
Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
> Can I administer SQL 2000 MSDE Release A from SQL Server's Enterprise
> Manager (EM) located on another machine on the same network?
> When I try to do this the EM setup wizard locates the host running MSDE
> but
> it cannot connect either with Windows authentication or the strong
> password
> created during MSDE's install.
> EM can see other instances of SQL Server 2000 on the network (these are
> not
> MSDE).
> MSDE is running on XP (SP1) and EM is running on W2K workstation.
> Many thanks.
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end
|||Thanks. I think it is an authentication issue rather than a 'property
rights' issue. This is because:
1) I just installed the same version of MSDE on a W98SE machine and was able
to register it successfully with the copy of 'Enterprise manager';
2) I just deleted the XP 'atempted' registration and tried to re-register
it. The dialog "Register SQL Server Messages" returns the error:
"SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
trusted SQL server connection"
Any idea how to make this Server connection trusted?
Thanks!
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> Q. Can I use SQL Server tools and services in conjunction with
MSDE?
> A. You can only use SQL Server tools and services in conjunction
with
> MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
> Standard Edition, or Enterprise Edition), and if you are using MSDE in
> conjunction with a properly licensed copy of SQL Server 2000. Visit the
How
> to Buy page for information on obtaining a valid SQL Server license.
> Note: The tools and services included with SQL Server Developer
> Edition may not be used to manage production server environments.
> The following utilities are installed by the MSDE setup application
> and are provided without restrictions for use with the copy of MSDE that
is
> installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe,
osql.exe,
> sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The
> dtsrun.exe utility is also provided, but can only be used to run existing
> Data Transformation Services (DTS) packages against the copy of MSDE
> installed by your application; it cannot be used to develop new DTS
> packages.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>
|||Hi Andrew,
This message means you don't have Mixed Mode authentication enabled. If you
do have enterprise manager connected, you can change this easily by looking
under the "security" tab in the properties of the server. (Right-click the
server to get to it). You need mixed mode before you can use "sa" or any sql
server username.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
news:OzXHOC3nEHA.2616@.tk2msftngp13.phx.gbl...
> Thanks. I think it is an authentication issue rather than a 'property
> rights' issue. This is because:
> 1) I just installed the same version of MSDE on a W98SE machine and was
able[vbcol=seagreen]
> to register it successfully with the copy of 'Enterprise manager';
> 2) I just deleted the XP 'atempted' registration and tried to re-register
> it. The dialog "Register SQL Server Messages" returns the error:
> "SVR1 - Registration failed for user 'sa'. Reason: Not associated with a
> trusted SQL server connection"
> Any idea how to make this Server connection trusted?
> Thanks!
>
> "Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
> news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> MSDE?
> with
> How
application[vbcol=seagreen]
> is
> osql.exe,
existing[vbcol=seagreen]
> it's
it[vbcol=seagreen]
a[vbcol=seagreen]
> rights.
MSDE[vbcol=seagreen]
are
>
|||Found it. The install command that I used:
SETUP SAPWD="wombat" created 'Windows Only Authentication'. A registry tweak
changed it to mixed, and then I could log on. Not sure exactly why Windows
authentication failed except that the admin name and pwd were different on
the MSDE machine from those on the machine that I was connecting from.
"Stephen Dybing [MSFT]" <stephd@.online.microsoft.com> wrote in message
news:OZrDqW0nEHA.2616@.tk2msftngp13.phx.gbl...
> Even if you can figure out your connectivity problem, it's probably not
> legal anyway. From the Appropriate Uses of MSDE FAQ at
> http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp:
> Q. Can I use SQL Server tools and services in conjunction with
MSDE?
> A. You can only use SQL Server tools and services in conjunction
with
> MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
> Standard Edition, or Enterprise Edition), and if you are using MSDE in
> conjunction with a properly licensed copy of SQL Server 2000. Visit the
How
> to Buy page for information on obtaining a valid SQL Server license.
> Note: The tools and services included with SQL Server Developer
> Edition may not be used to manage production server environments.
> The following utilities are installed by the MSDE setup application
> and are provided without restrictions for use with the copy of MSDE that
is
> installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe,
osql.exe,
> sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The
> dtsrun.exe utility is also provided, but can only be used to run existing
> Data Transformation Services (DTS) packages against the copy of MSDE
> installed by your application; it cannot be used to develop new DTS
> packages.
>
> There's not enough information in your post to determine whether or not
it's
> legal, but in the vast majority of instances it's not and I'm told that it
> requires a room full of lawyers and white board to figure out. There are a
> bunch of 3rd-party tools out there that might be of use. Have a look at
> Aaron's list at http://www.aspfaq.com/show.asp?id=2442.
> --
> Sincerely,
> Stephen Dybing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Andrew Chalk" <achalk@.XXXmagnacartasoftware.com> wrote in message
> news:%23VTyAG0nEHA.1160@.tk2msftngp13.phx.gbl...
>
>
Thursday, February 9, 2012
Administering MSDE with Enterprise Manager
Labels:
administer,
administering,
database,
enterprise,
enterprisemanager,
located,
machine,
manager,
microsoft,
msde,
mysql,
networkwhen,
oracle,
release,
server,
servers,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment