Good Day
SQL 2000 - just started recieving the following when loading Enterprise
Manager directly on the server console (from a workstation is fine)
'Connection to application failed. Ensure that no program modules have
been deleted'
I tried re-installing both OS & SQL service packs to see if a DLL or
something was missing - but am still receiving the error - any ideas ?
Thanks!
Hi
Can you open MMC and other add-ins without getting this error?
Can you open SQL Server Enterprise Manager.msc from within MMC?
John
"ERoss" wrote:
> Good Day
> SQL 2000 - just started recieving the following when loading Enterprise
> Manager directly on the server console (from a workstation is fine)
> 'Connection to application failed. Ensure that no program modules have
> been deleted'
> I tried re-installing both OS & SQL service packs to see if a DLL or
> something was missing - but am still receiving the error - any ideas ?
> Thanks!
>
|||In article <818FA874-C913-4C1C-93FB-3B62B00E0770@.microsoft.com>,
jbellnewsposts@.hotmail.com says...[vbcol=seagreen]
> Hi
> Can you open MMC and other add-ins without getting this error?
> Can you open SQL Server Enterprise Manager.msc from within MMC?
> John
> "ERoss" wrote:
Good Point & thanks -
MMC.exe runs OK - I added various snapins - all worked successfully -
tried to add enterprise manager.msc - it blows withthe same error
Thanks
|||Hi
You don't say what service pack you are on!
But you could try renaming the MMC and loading the renamed file (which seems
to sometimes work!), renaming the MMC file and installing a service pack, or
copy the MMC from another machine that is on the same fix level.
John
"ERoss" wrote:
> In article <818FA874-C913-4C1C-93FB-3B62B00E0770@.microsoft.com>,
> jbellnewsposts@.hotmail.com says...
> Good Point & thanks -
> MMC.exe runs OK - I added various snapins - all worked successfully -
> tried to add enterprise manager.msc - it blows withthe same error
> Thanks
>
|||In article <CD313813-AB93-40D6-90A4-8BF3DB4682F5@.microsoft.com>,
jbellnewsposts@.hotmail.com says...
SQL is SP4 -
I had re-applied that service pack -
But I will retry after renaming the enterprise manager.msc file
Thanks!
> Hi
> You don't say what service pack you are on!
> But you could try renaming the MMC and loading the renamed file (which seems
> to sometimes work!), renaming the MMC file and installing a service pack, or
> copy the MMC from another machine that is on the same fix level.
> John
>
Showing posts with label workstation. Show all posts
Showing posts with label workstation. Show all posts
Thursday, March 22, 2012
Enterprise Mgr Error
Good Day
SQL 2000 - just started recieving the following when loading Enterprise
Manager directly on the server console (from a workstation is fine)
'Connection to application failed. Ensure that no program modules have
been deleted'
I tried re-installing both OS & SQL service packs to see if a DLL or
something was missing - but am still receiving the error - any ideas ?
Thanks!Hi
Can you open MMC and other add-ins without getting this error?
Can you open SQL Server Enterprise Manager.msc from within MMC?
John
"ERoss" wrote:
> Good Day
> SQL 2000 - just started recieving the following when loading Enterprise
> Manager directly on the server console (from a workstation is fine)
> 'Connection to application failed. Ensure that no program modules have
> been deleted'
> I tried re-installing both OS & SQL service packs to see if a DLL or
> something was missing - but am still receiving the error - any ideas ?
> Thanks!
>|||In article <818FA874-C913-4C1C-93FB-3B62B00E0770@.microsoft.com>,
jbellnewsposts@.hotmail.com says...
> Hi
> Can you open MMC and other add-ins without getting this error?
> Can you open SQL Server Enterprise Manager.msc from within MMC?
> John
> "ERoss" wrote:
> > Good Day
> >
> > SQL 2000 - just started recieving the following when loading Enterprise
> > Manager directly on the server console (from a workstation is fine)
> >
> > 'Connection to application failed. Ensure that no program modules have
> > been deleted'
> >
> > I tried re-installing both OS & SQL service packs to see if a DLL or
> > something was missing - but am still receiving the error - any ideas ?
> >
> > Thanks!
> >
Good Point & thanks -
MMC.exe runs OK - I added various snapins - all worked successfully -
tried to add enterprise manager.msc - it blows withthe same error
Thanks|||Hi
You don't say what service pack you are on!
But you could try renaming the MMC and loading the renamed file (which seems
to sometimes work!), renaming the MMC file and installing a service pack, or
copy the MMC from another machine that is on the same fix level.
John
"ERoss" wrote:
> In article <818FA874-C913-4C1C-93FB-3B62B00E0770@.microsoft.com>,
> jbellnewsposts@.hotmail.com says...
> > Hi
> >
> > Can you open MMC and other add-ins without getting this error?
> >
> > Can you open SQL Server Enterprise Manager.msc from within MMC?
> >
> > John
> >
> > "ERoss" wrote:
> >
> > > Good Day
> > >
> > > SQL 2000 - just started recieving the following when loading Enterprise
> > > Manager directly on the server console (from a workstation is fine)
> > >
> > > 'Connection to application failed. Ensure that no program modules have
> > > been deleted'
> > >
> > > I tried re-installing both OS & SQL service packs to see if a DLL or
> > > something was missing - but am still receiving the error - any ideas ?
> > >
> > > Thanks!
> > >
> Good Point & thanks -
> MMC.exe runs OK - I added various snapins - all worked successfully -
> tried to add enterprise manager.msc - it blows withthe same error
> Thanks
>|||In article <CD313813-AB93-40D6-90A4-8BF3DB4682F5@.microsoft.com>,
jbellnewsposts@.hotmail.com says...
SQL is SP4 -
I had re-applied that service pack -
But I will retry after renaming the enterprise manager.msc file
Thanks!
> Hi
> You don't say what service pack you are on!
> But you could try renaming the MMC and loading the renamed file (which seems
> to sometimes work!), renaming the MMC file and installing a service pack, or
> copy the MMC from another machine that is on the same fix level.
> John
>
SQL 2000 - just started recieving the following when loading Enterprise
Manager directly on the server console (from a workstation is fine)
'Connection to application failed. Ensure that no program modules have
been deleted'
I tried re-installing both OS & SQL service packs to see if a DLL or
something was missing - but am still receiving the error - any ideas ?
Thanks!Hi
Can you open MMC and other add-ins without getting this error?
Can you open SQL Server Enterprise Manager.msc from within MMC?
John
"ERoss" wrote:
> Good Day
> SQL 2000 - just started recieving the following when loading Enterprise
> Manager directly on the server console (from a workstation is fine)
> 'Connection to application failed. Ensure that no program modules have
> been deleted'
> I tried re-installing both OS & SQL service packs to see if a DLL or
> something was missing - but am still receiving the error - any ideas ?
> Thanks!
>|||In article <818FA874-C913-4C1C-93FB-3B62B00E0770@.microsoft.com>,
jbellnewsposts@.hotmail.com says...
> Hi
> Can you open MMC and other add-ins without getting this error?
> Can you open SQL Server Enterprise Manager.msc from within MMC?
> John
> "ERoss" wrote:
> > Good Day
> >
> > SQL 2000 - just started recieving the following when loading Enterprise
> > Manager directly on the server console (from a workstation is fine)
> >
> > 'Connection to application failed. Ensure that no program modules have
> > been deleted'
> >
> > I tried re-installing both OS & SQL service packs to see if a DLL or
> > something was missing - but am still receiving the error - any ideas ?
> >
> > Thanks!
> >
Good Point & thanks -
MMC.exe runs OK - I added various snapins - all worked successfully -
tried to add enterprise manager.msc - it blows withthe same error
Thanks|||Hi
You don't say what service pack you are on!
But you could try renaming the MMC and loading the renamed file (which seems
to sometimes work!), renaming the MMC file and installing a service pack, or
copy the MMC from another machine that is on the same fix level.
John
"ERoss" wrote:
> In article <818FA874-C913-4C1C-93FB-3B62B00E0770@.microsoft.com>,
> jbellnewsposts@.hotmail.com says...
> > Hi
> >
> > Can you open MMC and other add-ins without getting this error?
> >
> > Can you open SQL Server Enterprise Manager.msc from within MMC?
> >
> > John
> >
> > "ERoss" wrote:
> >
> > > Good Day
> > >
> > > SQL 2000 - just started recieving the following when loading Enterprise
> > > Manager directly on the server console (from a workstation is fine)
> > >
> > > 'Connection to application failed. Ensure that no program modules have
> > > been deleted'
> > >
> > > I tried re-installing both OS & SQL service packs to see if a DLL or
> > > something was missing - but am still receiving the error - any ideas ?
> > >
> > > Thanks!
> > >
> Good Point & thanks -
> MMC.exe runs OK - I added various snapins - all worked successfully -
> tried to add enterprise manager.msc - it blows withthe same error
> Thanks
>|||In article <CD313813-AB93-40D6-90A4-8BF3DB4682F5@.microsoft.com>,
jbellnewsposts@.hotmail.com says...
SQL is SP4 -
I had re-applied that service pack -
But I will retry after renaming the enterprise manager.msc file
Thanks!
> Hi
> You don't say what service pack you are on!
> But you could try renaming the MMC and loading the renamed file (which seems
> to sometimes work!), renaming the MMC file and installing a service pack, or
> copy the MMC from another machine that is on the same fix level.
> John
>
Wednesday, March 21, 2012
Enterprise Manager Under XP
Just installed SQL on an XP client (my workstation). When I run enterprise manager, I have found that I no longer have toolbars (command bars) in the child windows (i.e. design table, open table, etc.). The toolbar buttons appear in the main window but not in the child window. This only appears to happen with XP (not in 2000). A buddy of mine is having the same issue.
Anybody know how to get my child window toolbars back? Thanks...Originally posted by pate
Just installed SQL on an XP client (my workstation). When I run enterprise manager, I have found that I no longer have toolbars (command bars) in the child windows (i.e. design table, open table, etc.). The toolbar buttons appear in the main window but not in the child window. This only appears to happen with XP (not in 2000). A buddy of mine is having the same issue.
Anybody know how to get my child window toolbars back? Thanks...
Menu>VIEW>CUSTOMIZE
??|||Originally posted by Brett Kaiser
Menu>VIEW>CUSTOMIZE
??
Been there and tried every possible option available without any luck...|||Originally posted by pate
Just installed SQL on an XP client (my workstation). When I run enterprise manager, I have found that I no longer have toolbars (command bars) in the child windows (i.e. design table, open table, etc.). The toolbar buttons appear in the main window but not in the child window. This only appears to happen with XP (not in 2000). A buddy of mine is having the same issue.
Anybody know how to get my child window toolbars back? Thanks...
I never did like xp...why that platform?
Anybody know how to get my child window toolbars back? Thanks...Originally posted by pate
Just installed SQL on an XP client (my workstation). When I run enterprise manager, I have found that I no longer have toolbars (command bars) in the child windows (i.e. design table, open table, etc.). The toolbar buttons appear in the main window but not in the child window. This only appears to happen with XP (not in 2000). A buddy of mine is having the same issue.
Anybody know how to get my child window toolbars back? Thanks...
Menu>VIEW>CUSTOMIZE
??|||Originally posted by Brett Kaiser
Menu>VIEW>CUSTOMIZE
??
Been there and tried every possible option available without any luck...|||Originally posted by pate
Just installed SQL on an XP client (my workstation). When I run enterprise manager, I have found that I no longer have toolbars (command bars) in the child windows (i.e. design table, open table, etc.). The toolbar buttons appear in the main window but not in the child window. This only appears to happen with XP (not in 2000). A buddy of mine is having the same issue.
Anybody know how to get my child window toolbars back? Thanks...
I never did like xp...why that platform?
Monday, March 19, 2012
Enterprise Manager Server Registration General Network Error
I'm having problems Registering servers in Enterrpise Manager.
This problem is workstation specific.
Workstation is XP Pro SP1, in an Active Directory domain. Only protocol in
machine is TCP/IP.
I have 4 machines with identical hardware ghosted from one source image and
all have the problem. hardware isn't the problem. I have at least one
other Win XP Pro computer built from a different build that has the problem.
User logs on using Active Driectory account. Opens Enterprise Manager,
register SQL server, types server name, uses NT Authentication. Error
returned is "General Network Error, check you network documentation"
Registration using SQL Authentication works fine (using SQL Authentication
is NOT an option for security reasons)
Same user can perform the same task using the same Active Directory
credentials using a different machine, so the account is not the problem.
This machine has different hardware, runs Windows 2000 Pro.
I can use this Windows 2000 machine on the same network port that the other
machine is on and don't have a problem. The network from the NIC to the
server isn't the problem.
I tried updating MDAC from 2.7 to 2.8 with no change.
SQL Server in question is newly build SQL 2000 SP3a with NO load on it
(application vendor hasn't installed software yet).
Query Analyzer has the same problem.
I tried using ODBCPING.EXE and received this response:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Gene
ral network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Conn
ectionRead
(recv()).
A similar error came up from Query Analyzer.
I did find 2 different SQL servers that will allow registrations, but these
users don't need access to those servers.
What do I need to look at on this client to correct this problem?
Scott Beginkb below has some good troubleshooting steps
http://support.microsoft.com/defaul...kb;en-us;827422
Andy.
"Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
> I'm having problems Registering servers in Enterrpise Manager.
> This problem is workstation specific.
> Workstation is XP Pro SP1, in an Active Directory domain. Only protocol
> in
> machine is TCP/IP.
> I have 4 machines with identical hardware ghosted from one source image
> and
> all have the problem. hardware isn't the problem. I have at least one
> other Win XP Pro computer built from a different build that has the
> problem.
> User logs on using Active Driectory account. Opens Enterprise Manager,
> register SQL server, types server name, uses NT Authentication. Error
> returned is "General Network Error, check you network documentation"
> Registration using SQL Authentication works fine (using SQL Authentication
> is NOT an option for security reasons)
> Same user can perform the same task using the same Active Directory
> credentials using a different machine, so the account is not the problem.
> This machine has different hardware, runs Windows 2000 Pro.
> I can use this Windows 2000 machine on the same network port that the
> other
> machine is on and don't have a problem. The network from the NIC to the
> server isn't the problem.
> I tried updating MDAC from 2.7 to 2.8 with no change.
> SQL Server in question is newly build SQL 2000 SP3a with NO load on it
> (application vendor hasn't installed software yet).
> Query Analyzer has the same problem.
> I tried using ODBCPING.EXE and received this response:
>
> COULD NOT CONNECT TO SQL SERVER
> SQLState: 08S01 Native Error: 11
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Ge
neral
> network
> error. Check your network documentation.
> SQLState: 01000 Native Error: 10054
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Co
nnectionRead
> (recv()).
> A similar error came up from Query Analyzer.
> I did find 2 different SQL servers that will allow registrations, but
> these
> users don't need access to those servers.
> What do I need to look at on this client to correct this problem?
> Scott Begin
>
>
>|||I looked at the article
I've tried the suggestions listed, but with no luck
1) Check DNS.
I can ping the server by name from the affected client. (rules out name
resolution)
I can register the server by name using SQL Authentication (rules out name
resolution)
I can register the server by IP address (rules out name resolution)
2) Verify the enabled protocols and aliases
Working Windows 2000 machine has Named Pipes and TCP/IP configured. Not
working XP machine matches. No aliases defined on either machine.
Everything else in Client Network Utility is the same on both machines.
3) Verify that the instance of SQL Server is listening Correctly
Have working Windows 2000 machine that can connect to this instance of SQL
Server using NT Authentication. XP Machine can connect to this instance of
SQL Server using SQL Authentication but NOT NT Authentication. As Suggested
by the article, the SQL Server log shows it is listening on port 1433
correctly.
Instance is running correctly.
4) Troubleshoot MDAC Issues
Windows 2000 Pro machine that works is running MDAC 2.7 SP1 Refresh
Windows XP Machine that doesn't work is running MDAC 2.8 RTM
ODBC Ping on 2000 machine that works shows the connection is being opened
properly.
ODBC Ping on XP machine that doesn't shows the following errors:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Gene
ral network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Conn
ectionRead
(recv()).
Seems to be an ODBC Issue
5) Troubleshoot firewall Issues:
Not applicable. There isn't a firewall between the client and server.
6) Troubleshoot Authentication and Security Issues
I use Active Directory Account on Windows 2000 machine. NT Authentication
works. I use same Active Directory account on Windows XP machine, doesn't
work.
Problem isn't authentication / security
7) Troubleshoot Stress on TCP/IP sockets
One of the servers being connected is a new server, without an application
running on it I don't think the stress on the TCP/IP sockets is the issue
8) See if teh instance of SQL Server is started in single user mode
I can connect to the server from other workstations simultaneously, so this
isn't the problem
9) Verify Named Pipes connectivity to SQL Server
Not trying to use Named Pipes to connect.
10) Troubleshoot conenctions that time otu during the recovery process.
These servers have been running anywhere from 1 day to 4 months. Recovery
process isn't going on. If this were a problem, I couldn't connect from th
e
Windows 2000 machine.
11) Test different ways to connect to the instance of SQL Server
Use SQL Authentication: Works from affected machine
From other data sources: Enterprise manager Fails NT Authentication, works
SQL; ODBC fails NT authentication, works SQL; Query Analyzer fails NT
Authentication, works SQL;
Using other protocols: Not an option. Must use TCP/IP
Different Login Account: why? The login account works on another computer
Put entry in hosts file: Why, resolution not problem
Connect from SQL Server: Works
Connect using IP address: Fails NT Authenticatiion/ works SQL Authenticatio
n
Specify port: Why? This doesn't seem to be the problem
12) Capture Network Traces:
Haven't tried this
The recurring theme you should see in what I have done is NT Authentication
doesn't work from this client. SQL Authentication does work from this
client. There is some setting / Driver or something that prevents it from
working.
Any other Ideas?
Scott Begin
scott@.thebegins.com
"Andy Ball" wrote:
> kb below has some good troubleshooting steps
> http://support.microsoft.com/defaul...kb;en-us;827422
> Andy.
> "Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
> news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
>
>
This problem is workstation specific.
Workstation is XP Pro SP1, in an Active Directory domain. Only protocol in
machine is TCP/IP.
I have 4 machines with identical hardware ghosted from one source image and
all have the problem. hardware isn't the problem. I have at least one
other Win XP Pro computer built from a different build that has the problem.
User logs on using Active Driectory account. Opens Enterprise Manager,
register SQL server, types server name, uses NT Authentication. Error
returned is "General Network Error, check you network documentation"
Registration using SQL Authentication works fine (using SQL Authentication
is NOT an option for security reasons)
Same user can perform the same task using the same Active Directory
credentials using a different machine, so the account is not the problem.
This machine has different hardware, runs Windows 2000 Pro.
I can use this Windows 2000 machine on the same network port that the other
machine is on and don't have a problem. The network from the NIC to the
server isn't the problem.
I tried updating MDAC from 2.7 to 2.8 with no change.
SQL Server in question is newly build SQL 2000 SP3a with NO load on it
(application vendor hasn't installed software yet).
Query Analyzer has the same problem.
I tried using ODBCPING.EXE and received this response:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Gene
ral network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Conn
ectionRead
(recv()).
A similar error came up from Query Analyzer.
I did find 2 different SQL servers that will allow registrations, but these
users don't need access to those servers.
What do I need to look at on this client to correct this problem?
Scott Beginkb below has some good troubleshooting steps
http://support.microsoft.com/defaul...kb;en-us;827422
Andy.
"Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
> I'm having problems Registering servers in Enterrpise Manager.
> This problem is workstation specific.
> Workstation is XP Pro SP1, in an Active Directory domain. Only protocol
> in
> machine is TCP/IP.
> I have 4 machines with identical hardware ghosted from one source image
> and
> all have the problem. hardware isn't the problem. I have at least one
> other Win XP Pro computer built from a different build that has the
> problem.
> User logs on using Active Driectory account. Opens Enterprise Manager,
> register SQL server, types server name, uses NT Authentication. Error
> returned is "General Network Error, check you network documentation"
> Registration using SQL Authentication works fine (using SQL Authentication
> is NOT an option for security reasons)
> Same user can perform the same task using the same Active Directory
> credentials using a different machine, so the account is not the problem.
> This machine has different hardware, runs Windows 2000 Pro.
> I can use this Windows 2000 machine on the same network port that the
> other
> machine is on and don't have a problem. The network from the NIC to the
> server isn't the problem.
> I tried updating MDAC from 2.7 to 2.8 with no change.
> SQL Server in question is newly build SQL 2000 SP3a with NO load on it
> (application vendor hasn't installed software yet).
> Query Analyzer has the same problem.
> I tried using ODBCPING.EXE and received this response:
>
> COULD NOT CONNECT TO SQL SERVER
> SQLState: 08S01 Native Error: 11
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Ge
neral
> network
> error. Check your network documentation.
> SQLState: 01000 Native Error: 10054
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Co
nnectionRead
> (recv()).
> A similar error came up from Query Analyzer.
> I did find 2 different SQL servers that will allow registrations, but
> these
> users don't need access to those servers.
> What do I need to look at on this client to correct this problem?
> Scott Begin
>
>
>|||I looked at the article
I've tried the suggestions listed, but with no luck
1) Check DNS.
I can ping the server by name from the affected client. (rules out name
resolution)
I can register the server by name using SQL Authentication (rules out name
resolution)
I can register the server by IP address (rules out name resolution)
2) Verify the enabled protocols and aliases
Working Windows 2000 machine has Named Pipes and TCP/IP configured. Not
working XP machine matches. No aliases defined on either machine.
Everything else in Client Network Utility is the same on both machines.
3) Verify that the instance of SQL Server is listening Correctly
Have working Windows 2000 machine that can connect to this instance of SQL
Server using NT Authentication. XP Machine can connect to this instance of
SQL Server using SQL Authentication but NOT NT Authentication. As Suggested
by the article, the SQL Server log shows it is listening on port 1433
correctly.
Instance is running correctly.
4) Troubleshoot MDAC Issues
Windows 2000 Pro machine that works is running MDAC 2.7 SP1 Refresh
Windows XP Machine that doesn't work is running MDAC 2.8 RTM
ODBC Ping on 2000 machine that works shows the connection is being opened
properly.
ODBC Ping on XP machine that doesn't shows the following errors:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Gene
ral network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]Conn
ectionRead
(recv()).
Seems to be an ODBC Issue
5) Troubleshoot firewall Issues:
Not applicable. There isn't a firewall between the client and server.
6) Troubleshoot Authentication and Security Issues
I use Active Directory Account on Windows 2000 machine. NT Authentication
works. I use same Active Directory account on Windows XP machine, doesn't
work.
Problem isn't authentication / security
7) Troubleshoot Stress on TCP/IP sockets
One of the servers being connected is a new server, without an application
running on it I don't think the stress on the TCP/IP sockets is the issue
8) See if teh instance of SQL Server is started in single user mode
I can connect to the server from other workstations simultaneously, so this
isn't the problem
9) Verify Named Pipes connectivity to SQL Server
Not trying to use Named Pipes to connect.
10) Troubleshoot conenctions that time otu during the recovery process.
These servers have been running anywhere from 1 day to 4 months. Recovery
process isn't going on. If this were a problem, I couldn't connect from th
e
Windows 2000 machine.
11) Test different ways to connect to the instance of SQL Server
Use SQL Authentication: Works from affected machine
From other data sources: Enterprise manager Fails NT Authentication, works
SQL; ODBC fails NT authentication, works SQL; Query Analyzer fails NT
Authentication, works SQL;
Using other protocols: Not an option. Must use TCP/IP
Different Login Account: why? The login account works on another computer
Put entry in hosts file: Why, resolution not problem
Connect from SQL Server: Works
Connect using IP address: Fails NT Authenticatiion/ works SQL Authenticatio
n
Specify port: Why? This doesn't seem to be the problem
12) Capture Network Traces:
Haven't tried this
The recurring theme you should see in what I have done is NT Authentication
doesn't work from this client. SQL Authentication does work from this
client. There is some setting / Driver or something that prevents it from
working.
Any other Ideas?
Scott Begin
scott@.thebegins.com
"Andy Ball" wrote:
> kb below has some good troubleshooting steps
> http://support.microsoft.com/defaul...kb;en-us;827422
> Andy.
> "Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
> news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
>
>
Enterprise Manager Server Registration General Network Error
I'm having problems Registering servers in Enterrpise Manager.
This problem is workstation specific.
Workstation is XP Pro SP1, in an Active Directory domain. Only protocol in
machine is TCP/IP.
I have 4 machines with identical hardware ghosted from one source image and
all have the problem. Hardware isn't the problem. I have at least one
other Win XP Pro computer built from a different build that has the problem.
User logs on using Active Driectory account. Opens Enterprise Manager,
register SQL server, types server name, uses NT Authentication. Error
returned is "General Network Error, check you network documentation"
Registration using SQL Authentication works fine (using SQL Authentication
is NOT an option for security reasons)
Same user can perform the same task using the same Active Directory
credentials using a different machine, so the account is not the problem.
This machine has different hardware, runs Windows 2000 Pro.
I can use this Windows 2000 machine on the same network port that the other
machine is on and don't have a problem. The network from the NIC to the
server isn't the problem.
I tried updating MDAC from 2.7 to 2.8 with no change.
SQL Server in question is newly build SQL 2000 SP3a with NO load on it
(application vendor hasn't installed software yet).
Query Analyzer has the same problem.
I tried using ODBCPING.EXE and received this response:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(recv()).
A similar error came up from Query Analyzer.
I did find 2 different SQL servers that will allow registrations, but these
users don't need access to those servers.
What do I need to look at on this client to correct this problem?
Scott Begin
kb below has some good troubleshooting steps
http://support.microsoft.com/default...b;en-us;827422
Andy.
"Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
> I'm having problems Registering servers in Enterrpise Manager.
> This problem is workstation specific.
> Workstation is XP Pro SP1, in an Active Directory domain. Only protocol
> in
> machine is TCP/IP.
> I have 4 machines with identical hardware ghosted from one source image
> and
> all have the problem. Hardware isn't the problem. I have at least one
> other Win XP Pro computer built from a different build that has the
> problem.
> User logs on using Active Driectory account. Opens Enterprise Manager,
> register SQL server, types server name, uses NT Authentication. Error
> returned is "General Network Error, check you network documentation"
> Registration using SQL Authentication works fine (using SQL Authentication
> is NOT an option for security reasons)
> Same user can perform the same task using the same Active Directory
> credentials using a different machine, so the account is not the problem.
> This machine has different hardware, runs Windows 2000 Pro.
> I can use this Windows 2000 machine on the same network port that the
> other
> machine is on and don't have a problem. The network from the NIC to the
> server isn't the problem.
> I tried updating MDAC from 2.7 to 2.8 with no change.
> SQL Server in question is newly build SQL 2000 SP3a with NO load on it
> (application vendor hasn't installed software yet).
> Query Analyzer has the same problem.
> I tried using ODBCPING.EXE and received this response:
>
> COULD NOT CONNECT TO SQL SERVER
> SQLState: 08S01 Native Error: 11
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General
> network
> error. Check your network documentation.
> SQLState: 01000 Native Error: 10054
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (recv()).
> A similar error came up from Query Analyzer.
> I did find 2 different SQL servers that will allow registrations, but
> these
> users don't need access to those servers.
> What do I need to look at on this client to correct this problem?
> Scott Begin
>
>
>
|||I looked at the article
I've tried the suggestions listed, but with no luck
1) Check DNS.
I can ping the server by name from the affected client. (rules out name
resolution)
I can register the server by name using SQL Authentication (rules out name
resolution)
I can register the server by IP address (rules out name resolution)
2) Verify the enabled protocols and aliases
Working Windows 2000 machine has Named Pipes and TCP/IP configured. Not
working XP machine matches. No aliases defined on either machine.
Everything else in Client Network Utility is the same on both machines.
3) Verify that the instance of SQL Server is listening Correctly
Have working Windows 2000 machine that can connect to this instance of SQL
Server using NT Authentication. XP Machine can connect to this instance of
SQL Server using SQL Authentication but NOT NT Authentication. As Suggested
by the article, the SQL Server log shows it is listening on port 1433
correctly.
Instance is running correctly.
4) Troubleshoot MDAC Issues
Windows 2000 Pro machine that works is running MDAC 2.7 SP1 Refresh
Windows XP Machine that doesn't work is running MDAC 2.8 RTM
ODBC Ping on 2000 machine that works shows the connection is being opened
properly.
ODBC Ping on XP machine that doesn't shows the following errors:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(recv()).
Seems to be an ODBC Issue
5) Troubleshoot firewall Issues:
Not applicable. There isn't a firewall between the client and server.
6) Troubleshoot Authentication and Security Issues
I use Active Directory Account on Windows 2000 machine. NT Authentication
works. I use same Active Directory account on Windows XP machine, doesn't
work.
Problem isn't authentication / security
7) Troubleshoot Stress on TCP/IP sockets
One of the servers being connected is a new server, without an application
running on it I don't think the stress on the TCP/IP sockets is the issue
8) See if teh instance of SQL Server is started in single user mode
I can connect to the server from other workstations simultaneously, so this
isn't the problem
9) Verify Named Pipes connectivity to SQL Server
Not trying to use Named Pipes to connect.
10) Troubleshoot conenctions that time otu during the recovery process.
These servers have been running anywhere from 1 day to 4 months. Recovery
process isn't going on. If this were a problem, I couldn't connect from the
Windows 2000 machine.
11) Test different ways to connect to the instance of SQL Server
Use SQL Authentication: Works from affected machine
From other data sources: Enterprise manager Fails NT Authentication, works
SQL; ODBC fails NT authentication, works SQL; Query Analyzer fails NT
Authentication, works SQL;
Using other protocols: Not an option. Must use TCP/IP
Different Login Account: why? The login account works on another computer
Put entry in hosts file: Why, resolution not problem
Connect from SQL Server: Works
Connect using IP address: Fails NT Authenticatiion/ works SQL Authentication
Specify port: Why? This doesn't seem to be the problem
12) Capture Network Traces:
Haven't tried this
The recurring theme you should see in what I have done is NT Authentication
doesn't work from this client. SQL Authentication does work from this
client. There is some setting / Driver or something that prevents it from
working.
Any other Ideas?
Scott Begin
scott@.thebegins.com
"Andy Ball" wrote:
> kb below has some good troubleshooting steps
> http://support.microsoft.com/default...b;en-us;827422
> Andy.
> "Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
> news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
>
>
This problem is workstation specific.
Workstation is XP Pro SP1, in an Active Directory domain. Only protocol in
machine is TCP/IP.
I have 4 machines with identical hardware ghosted from one source image and
all have the problem. Hardware isn't the problem. I have at least one
other Win XP Pro computer built from a different build that has the problem.
User logs on using Active Driectory account. Opens Enterprise Manager,
register SQL server, types server name, uses NT Authentication. Error
returned is "General Network Error, check you network documentation"
Registration using SQL Authentication works fine (using SQL Authentication
is NOT an option for security reasons)
Same user can perform the same task using the same Active Directory
credentials using a different machine, so the account is not the problem.
This machine has different hardware, runs Windows 2000 Pro.
I can use this Windows 2000 machine on the same network port that the other
machine is on and don't have a problem. The network from the NIC to the
server isn't the problem.
I tried updating MDAC from 2.7 to 2.8 with no change.
SQL Server in question is newly build SQL 2000 SP3a with NO load on it
(application vendor hasn't installed software yet).
Query Analyzer has the same problem.
I tried using ODBCPING.EXE and received this response:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(recv()).
A similar error came up from Query Analyzer.
I did find 2 different SQL servers that will allow registrations, but these
users don't need access to those servers.
What do I need to look at on this client to correct this problem?
Scott Begin
kb below has some good troubleshooting steps
http://support.microsoft.com/default...b;en-us;827422
Andy.
"Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
> I'm having problems Registering servers in Enterrpise Manager.
> This problem is workstation specific.
> Workstation is XP Pro SP1, in an Active Directory domain. Only protocol
> in
> machine is TCP/IP.
> I have 4 machines with identical hardware ghosted from one source image
> and
> all have the problem. Hardware isn't the problem. I have at least one
> other Win XP Pro computer built from a different build that has the
> problem.
> User logs on using Active Driectory account. Opens Enterprise Manager,
> register SQL server, types server name, uses NT Authentication. Error
> returned is "General Network Error, check you network documentation"
> Registration using SQL Authentication works fine (using SQL Authentication
> is NOT an option for security reasons)
> Same user can perform the same task using the same Active Directory
> credentials using a different machine, so the account is not the problem.
> This machine has different hardware, runs Windows 2000 Pro.
> I can use this Windows 2000 machine on the same network port that the
> other
> machine is on and don't have a problem. The network from the NIC to the
> server isn't the problem.
> I tried updating MDAC from 2.7 to 2.8 with no change.
> SQL Server in question is newly build SQL 2000 SP3a with NO load on it
> (application vendor hasn't installed software yet).
> Query Analyzer has the same problem.
> I tried using ODBCPING.EXE and received this response:
>
> COULD NOT CONNECT TO SQL SERVER
> SQLState: 08S01 Native Error: 11
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General
> network
> error. Check your network documentation.
> SQLState: 01000 Native Error: 10054
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (recv()).
> A similar error came up from Query Analyzer.
> I did find 2 different SQL servers that will allow registrations, but
> these
> users don't need access to those servers.
> What do I need to look at on this client to correct this problem?
> Scott Begin
>
>
>
|||I looked at the article
I've tried the suggestions listed, but with no luck
1) Check DNS.
I can ping the server by name from the affected client. (rules out name
resolution)
I can register the server by name using SQL Authentication (rules out name
resolution)
I can register the server by IP address (rules out name resolution)
2) Verify the enabled protocols and aliases
Working Windows 2000 machine has Named Pipes and TCP/IP configured. Not
working XP machine matches. No aliases defined on either machine.
Everything else in Client Network Utility is the same on both machines.
3) Verify that the instance of SQL Server is listening Correctly
Have working Windows 2000 machine that can connect to this instance of SQL
Server using NT Authentication. XP Machine can connect to this instance of
SQL Server using SQL Authentication but NOT NT Authentication. As Suggested
by the article, the SQL Server log shows it is listening on port 1433
correctly.
Instance is running correctly.
4) Troubleshoot MDAC Issues
Windows 2000 Pro machine that works is running MDAC 2.7 SP1 Refresh
Windows XP Machine that doesn't work is running MDAC 2.8 RTM
ODBC Ping on 2000 machine that works shows the connection is being opened
properly.
ODBC Ping on XP machine that doesn't shows the following errors:
COULD NOT CONNECT TO SQL SERVER
SQLState: 08S01 Native Error: 11
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
error. Check your network documentation.
SQLState: 01000 Native Error: 10054
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(recv()).
Seems to be an ODBC Issue
5) Troubleshoot firewall Issues:
Not applicable. There isn't a firewall between the client and server.
6) Troubleshoot Authentication and Security Issues
I use Active Directory Account on Windows 2000 machine. NT Authentication
works. I use same Active Directory account on Windows XP machine, doesn't
work.
Problem isn't authentication / security
7) Troubleshoot Stress on TCP/IP sockets
One of the servers being connected is a new server, without an application
running on it I don't think the stress on the TCP/IP sockets is the issue
8) See if teh instance of SQL Server is started in single user mode
I can connect to the server from other workstations simultaneously, so this
isn't the problem
9) Verify Named Pipes connectivity to SQL Server
Not trying to use Named Pipes to connect.
10) Troubleshoot conenctions that time otu during the recovery process.
These servers have been running anywhere from 1 day to 4 months. Recovery
process isn't going on. If this were a problem, I couldn't connect from the
Windows 2000 machine.
11) Test different ways to connect to the instance of SQL Server
Use SQL Authentication: Works from affected machine
From other data sources: Enterprise manager Fails NT Authentication, works
SQL; ODBC fails NT authentication, works SQL; Query Analyzer fails NT
Authentication, works SQL;
Using other protocols: Not an option. Must use TCP/IP
Different Login Account: why? The login account works on another computer
Put entry in hosts file: Why, resolution not problem
Connect from SQL Server: Works
Connect using IP address: Fails NT Authenticatiion/ works SQL Authentication
Specify port: Why? This doesn't seem to be the problem
12) Capture Network Traces:
Haven't tried this
The recurring theme you should see in what I have done is NT Authentication
doesn't work from this client. SQL Authentication does work from this
client. There is some setting / Driver or something that prevents it from
working.
Any other Ideas?
Scott Begin
scott@.thebegins.com
"Andy Ball" wrote:
> kb below has some good troubleshooting steps
> http://support.microsoft.com/default...b;en-us;827422
> Andy.
> "Scott Begin" <ScottBegin@.discussions.microsoft.com> wrote in message
> news:3CF7A011-A316-493B-9EFB-D45434373BCF@.microsoft.com...
>
>
Sunday, March 11, 2012
Enterprise Manager on a workstation
Hi
I have a customer who uses SQL running on an SBS2000 server for several
applications. They have asked if
they can install SQL Enterprise manager on a workstation to manage an
Internet booking system they use.
Can anyone suggest any issues with this please? I'm assuming that there's a
licensing issue, but would there also be a network issue?
Regards
Nick
As long as the workstation has a licence to use the SQL Server it can also
use the managing tools.
There are no Networking issues as far as the EM is also only just a client
app with some more features than only quering or manipulating some data.
HTH, Jens Smeyer.
http://www.sqlserver2005.de
"Nick Hill" <please@.dont.use> schrieb im Newsbeitrag
news:d3jfu0$4ft$1$8302bc10@.news.demon.co.uk...
> Hi
> I have a customer who uses SQL running on an SBS2000 server for several
> applications. They have asked if
> they can install SQL Enterprise manager on a workstation to manage an
> Internet booking system they use.
> Can anyone suggest any issues with this please? I'm assuming that there's
> a licensing issue, but would there also be a network issue?
> Regards
> Nick
>
|||There is no problem in principle running Enterprise Manager or any of
the other client tools on a client PC - they are designed for that. You
need either a Client Access Licence or a Processor Licence for the
server.
If you are thinking about access over the Internet however, you won't
have the necessary ports open, except maybe via a secure VPN. You'll
most likely want some kind of remote access solution and then run EM
from there.
David Portas
SQL Server MVP
|||Doesn't MSDE come with the Enterprise Manager and as far as i know the MSDE
is free.
Does that mean that using the Enterprise Manager that MSDE comes with to
connect to another SQL server engine requires a licence?
-Ash
"David Portas" wrote:
> There is no problem in principle running Enterprise Manager or any of
> the other client tools on a client PC - they are designed for that. You
> need either a Client Access Licence or a Processor Licence for the
> server.
> If you are thinking about access over the Internet however, you won't
> have the necessary ports open, except maybe via a secure VPN. You'll
> most likely want some kind of remote access solution and then run EM
> from there.
> --
> David Portas
> SQL Server MVP
> --
>
|||> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
MSDE comes with OSQL , no EM :-)
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
But there is a webTool from MS to administer SQl Server Databases with basic
functionality:
http://www.microsoft.com/downloads/d...DisplayLang=en
HTH, Jens Smeyer
http://www.sqlserver2005.de
"Ash Metry" <AshMetry@.discussions.microsoft.com> schrieb im Newsbeitrag
news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...[vbcol=seagreen]
> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
> -Ash
> "David Portas" wrote:
|||MSDE does not come with Enterprise Manager. The MSDE license does not cover
using Enterprise Manager.
Geoff N. Hiten
Microsoft SQL Server MVP
"Ash Metry" <AshMetry@.discussions.microsoft.com> wrote in message
news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...[vbcol=seagreen]
> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
> -Ash
> "David Portas" wrote:
|||Ya i remember now.
Sorry about that, I posted without thinking.
"Geoff N. Hiten" wrote:
> MSDE does not come with Enterprise Manager. The MSDE license does not cover
> using Enterprise Manager.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "Ash Metry" <AshMetry@.discussions.microsoft.com> wrote in message
> news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...
>
>
I have a customer who uses SQL running on an SBS2000 server for several
applications. They have asked if
they can install SQL Enterprise manager on a workstation to manage an
Internet booking system they use.
Can anyone suggest any issues with this please? I'm assuming that there's a
licensing issue, but would there also be a network issue?
Regards
Nick
As long as the workstation has a licence to use the SQL Server it can also
use the managing tools.
There are no Networking issues as far as the EM is also only just a client
app with some more features than only quering or manipulating some data.
HTH, Jens Smeyer.
http://www.sqlserver2005.de
"Nick Hill" <please@.dont.use> schrieb im Newsbeitrag
news:d3jfu0$4ft$1$8302bc10@.news.demon.co.uk...
> Hi
> I have a customer who uses SQL running on an SBS2000 server for several
> applications. They have asked if
> they can install SQL Enterprise manager on a workstation to manage an
> Internet booking system they use.
> Can anyone suggest any issues with this please? I'm assuming that there's
> a licensing issue, but would there also be a network issue?
> Regards
> Nick
>
|||There is no problem in principle running Enterprise Manager or any of
the other client tools on a client PC - they are designed for that. You
need either a Client Access Licence or a Processor Licence for the
server.
If you are thinking about access over the Internet however, you won't
have the necessary ports open, except maybe via a secure VPN. You'll
most likely want some kind of remote access solution and then run EM
from there.
David Portas
SQL Server MVP
|||Doesn't MSDE come with the Enterprise Manager and as far as i know the MSDE
is free.
Does that mean that using the Enterprise Manager that MSDE comes with to
connect to another SQL server engine requires a licence?
-Ash
"David Portas" wrote:
> There is no problem in principle running Enterprise Manager or any of
> the other client tools on a client PC - they are designed for that. You
> need either a Client Access Licence or a Processor Licence for the
> server.
> If you are thinking about access over the Internet however, you won't
> have the necessary ports open, except maybe via a secure VPN. You'll
> most likely want some kind of remote access solution and then run EM
> from there.
> --
> David Portas
> SQL Server MVP
> --
>
|||> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
MSDE comes with OSQL , no EM :-)
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
But there is a webTool from MS to administer SQl Server Databases with basic
functionality:
http://www.microsoft.com/downloads/d...DisplayLang=en
HTH, Jens Smeyer
http://www.sqlserver2005.de
"Ash Metry" <AshMetry@.discussions.microsoft.com> schrieb im Newsbeitrag
news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...[vbcol=seagreen]
> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
> -Ash
> "David Portas" wrote:
|||MSDE does not come with Enterprise Manager. The MSDE license does not cover
using Enterprise Manager.
Geoff N. Hiten
Microsoft SQL Server MVP
"Ash Metry" <AshMetry@.discussions.microsoft.com> wrote in message
news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...[vbcol=seagreen]
> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
> -Ash
> "David Portas" wrote:
|||Ya i remember now.
Sorry about that, I posted without thinking.
"Geoff N. Hiten" wrote:
> MSDE does not come with Enterprise Manager. The MSDE license does not cover
> using Enterprise Manager.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "Ash Metry" <AshMetry@.discussions.microsoft.com> wrote in message
> news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...
>
>
Enterprise Manager on a workstation
Hi
I have a customer who uses SQL running on an SBS2000 server for several
applications. They have asked if
they can install SQL Enterprise manager on a workstation to manage an
Internet booking system they use.
Can anyone suggest any issues with this please? I'm assuming that there's a
licensing issue, but would there also be a network issue?
Regards
NickAs long as the workstation has a licence to use the SQL Server it can also
use the managing tools.
There are no Networking issues as far as the EM is also only just a client
app with some more features than only quering or manipulating some data.
HTH, Jens Smeyer.
http://www.sqlserver2005.de
--
"Nick Hill" <please@.dont.use> schrieb im Newsbeitrag
news:d3jfu0$4ft$1$8302bc10@.news.demon.co.uk...
> Hi
> I have a customer who uses SQL running on an SBS2000 server for several
> applications. They have asked if
> they can install SQL Enterprise manager on a workstation to manage an
> Internet booking system they use.
> Can anyone suggest any issues with this please? I'm assuming that there's
> a licensing issue, but would there also be a network issue?
> Regards
> Nick
>|||There is no problem in principle running Enterprise Manager or any of
the other client tools on a client PC - they are designed for that. You
need either a Client Access Licence or a Processor Licence for the
server.
If you are thinking about access over the Internet however, you won't
have the necessary ports open, except maybe via a secure VPN. You'll
most likely want some kind of remote access solution and then run EM
from there.
David Portas
SQL Server MVP
--|||Doesn't MSDE come with the Enterprise Manager and as far as i know the MSDE
is free.
Does that mean that using the Enterprise Manager that MSDE comes with to
connect to another SQL server engine requires a licence?
-Ash
"David Portas" wrote:
> There is no problem in principle running Enterprise Manager or any of
> the other client tools on a client PC - they are designed for that. You
> need either a Client Access Licence or a Processor Licence for the
> server.
> If you are thinking about access over the Internet however, you won't
> have the necessary ports open, except maybe via a secure VPN. You'll
> most likely want some kind of remote access solution and then run EM
> from there.
> --
> David Portas
> SQL Server MVP
> --
>|||> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
MSDE comes with OSQL , no EM :-)
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
But there is a webTool from MS to administer SQl Server Databases with basic
functionality:
http://www.microsoft.com/downloads/...&DisplayLang=en
HTH, Jens Smeyer
http://www.sqlserver2005.de
--
"Ash Metry" <AshMetry@.discussions.microsoft.com> schrieb im Newsbeitrag
news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...[vbcol=seagreen]
> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
> -Ash
> "David Portas" wrote:
>|||MSDE does not come with Enterprise Manager. The MSDE license does not cover
using Enterprise Manager.
Geoff N. Hiten
Microsoft SQL Server MVP
"Ash Metry" <AshMetry@.discussions.microsoft.com> wrote in message
news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...[vbcol=seagreen]
> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
> -Ash
> "David Portas" wrote:
>|||Ya i remember now.
Sorry about that, I posted without thinking.
"Geoff N. Hiten" wrote:
> MSDE does not come with Enterprise Manager. The MSDE license does not cov
er
> using Enterprise Manager.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "Ash Metry" <AshMetry@.discussions.microsoft.com> wrote in message
> news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...
>
>
I have a customer who uses SQL running on an SBS2000 server for several
applications. They have asked if
they can install SQL Enterprise manager on a workstation to manage an
Internet booking system they use.
Can anyone suggest any issues with this please? I'm assuming that there's a
licensing issue, but would there also be a network issue?
Regards
NickAs long as the workstation has a licence to use the SQL Server it can also
use the managing tools.
There are no Networking issues as far as the EM is also only just a client
app with some more features than only quering or manipulating some data.
HTH, Jens Smeyer.
http://www.sqlserver2005.de
--
"Nick Hill" <please@.dont.use> schrieb im Newsbeitrag
news:d3jfu0$4ft$1$8302bc10@.news.demon.co.uk...
> Hi
> I have a customer who uses SQL running on an SBS2000 server for several
> applications. They have asked if
> they can install SQL Enterprise manager on a workstation to manage an
> Internet booking system they use.
> Can anyone suggest any issues with this please? I'm assuming that there's
> a licensing issue, but would there also be a network issue?
> Regards
> Nick
>|||There is no problem in principle running Enterprise Manager or any of
the other client tools on a client PC - they are designed for that. You
need either a Client Access Licence or a Processor Licence for the
server.
If you are thinking about access over the Internet however, you won't
have the necessary ports open, except maybe via a secure VPN. You'll
most likely want some kind of remote access solution and then run EM
from there.
David Portas
SQL Server MVP
--|||Doesn't MSDE come with the Enterprise Manager and as far as i know the MSDE
is free.
Does that mean that using the Enterprise Manager that MSDE comes with to
connect to another SQL server engine requires a licence?
-Ash
"David Portas" wrote:
> There is no problem in principle running Enterprise Manager or any of
> the other client tools on a client PC - they are designed for that. You
> need either a Client Access Licence or a Processor Licence for the
> server.
> If you are thinking about access over the Internet however, you won't
> have the necessary ports open, except maybe via a secure VPN. You'll
> most likely want some kind of remote access solution and then run EM
> from there.
> --
> David Portas
> SQL Server MVP
> --
>|||> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
MSDE comes with OSQL , no EM :-)
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
But there is a webTool from MS to administer SQl Server Databases with basic
functionality:
http://www.microsoft.com/downloads/...&DisplayLang=en
HTH, Jens Smeyer
http://www.sqlserver2005.de
--
"Ash Metry" <AshMetry@.discussions.microsoft.com> schrieb im Newsbeitrag
news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...[vbcol=seagreen]
> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
> -Ash
> "David Portas" wrote:
>|||MSDE does not come with Enterprise Manager. The MSDE license does not cover
using Enterprise Manager.
Geoff N. Hiten
Microsoft SQL Server MVP
"Ash Metry" <AshMetry@.discussions.microsoft.com> wrote in message
news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...[vbcol=seagreen]
> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
> -Ash
> "David Portas" wrote:
>|||Ya i remember now.
Sorry about that, I posted without thinking.
"Geoff N. Hiten" wrote:
> MSDE does not come with Enterprise Manager. The MSDE license does not cov
er
> using Enterprise Manager.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "Ash Metry" <AshMetry@.discussions.microsoft.com> wrote in message
> news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...
>
>
Enterprise Manager on a workstation
Hi
I have a customer who uses SQL running on an SBS2000 server for several
applications. They have asked if
they can install SQL Enterprise manager on a workstation to manage an
Internet booking system they use.
Can anyone suggest any issues with this please? I'm assuming that there's a
licensing issue, but would there also be a network issue?
Regards
NickAs long as the workstation has a licence to use the SQL Server it can also
use the managing tools.
There are no Networking issues as far as the EM is also only just a client
app with some more features than only quering or manipulating some data.
HTH, Jens Süßmeyer.
--
http://www.sqlserver2005.de
--
"Nick Hill" <please@.dont.use> schrieb im Newsbeitrag
news:d3jfu0$4ft$1$8302bc10@.news.demon.co.uk...
> Hi
> I have a customer who uses SQL running on an SBS2000 server for several
> applications. They have asked if
> they can install SQL Enterprise manager on a workstation to manage an
> Internet booking system they use.
> Can anyone suggest any issues with this please? I'm assuming that there's
> a licensing issue, but would there also be a network issue?
> Regards
> Nick
>|||There is no problem in principle running Enterprise Manager or any of
the other client tools on a client PC - they are designed for that. You
need either a Client Access Licence or a Processor Licence for the
server.
If you are thinking about access over the Internet however, you won't
have the necessary ports open, except maybe via a secure VPN. You'll
most likely want some kind of remote access solution and then run EM
from there.
--
David Portas
SQL Server MVP
--|||> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
MSDE comes with OSQL , no EM :-)
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
But there is a webTool from MS to administer SQl Server Databases with basic
functionality:
http://www.microsoft.com/downloads/details.aspx?FamilyID=c039a798-c57a-419e-acbc-2a332cb7f959&DisplayLang=en
HTH, Jens Süßmeyer
--
http://www.sqlserver2005.de
--
"Ash Metry" <AshMetry@.discussions.microsoft.com> schrieb im Newsbeitrag
news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...
> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
> -Ash
> "David Portas" wrote:
>> There is no problem in principle running Enterprise Manager or any of
>> the other client tools on a client PC - they are designed for that. You
>> need either a Client Access Licence or a Processor Licence for the
>> server.
>> If you are thinking about access over the Internet however, you won't
>> have the necessary ports open, except maybe via a secure VPN. You'll
>> most likely want some kind of remote access solution and then run EM
>> from there.
>> --
>> David Portas
>> SQL Server MVP
>> --
>>|||MSDE does not come with Enterprise Manager. The MSDE license does not cover
using Enterprise Manager.
Geoff N. Hiten
Microsoft SQL Server MVP
"Ash Metry" <AshMetry@.discussions.microsoft.com> wrote in message
news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...
> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
> -Ash
> "David Portas" wrote:
>> There is no problem in principle running Enterprise Manager or any of
>> the other client tools on a client PC - they are designed for that. You
>> need either a Client Access Licence or a Processor Licence for the
>> server.
>> If you are thinking about access over the Internet however, you won't
>> have the necessary ports open, except maybe via a secure VPN. You'll
>> most likely want some kind of remote access solution and then run EM
>> from there.
>> --
>> David Portas
>> SQL Server MVP
>> --
>>
I have a customer who uses SQL running on an SBS2000 server for several
applications. They have asked if
they can install SQL Enterprise manager on a workstation to manage an
Internet booking system they use.
Can anyone suggest any issues with this please? I'm assuming that there's a
licensing issue, but would there also be a network issue?
Regards
NickAs long as the workstation has a licence to use the SQL Server it can also
use the managing tools.
There are no Networking issues as far as the EM is also only just a client
app with some more features than only quering or manipulating some data.
HTH, Jens Süßmeyer.
--
http://www.sqlserver2005.de
--
"Nick Hill" <please@.dont.use> schrieb im Newsbeitrag
news:d3jfu0$4ft$1$8302bc10@.news.demon.co.uk...
> Hi
> I have a customer who uses SQL running on an SBS2000 server for several
> applications. They have asked if
> they can install SQL Enterprise manager on a workstation to manage an
> Internet booking system they use.
> Can anyone suggest any issues with this please? I'm assuming that there's
> a licensing issue, but would there also be a network issue?
> Regards
> Nick
>|||There is no problem in principle running Enterprise Manager or any of
the other client tools on a client PC - they are designed for that. You
need either a Client Access Licence or a Processor Licence for the
server.
If you are thinking about access over the Internet however, you won't
have the necessary ports open, except maybe via a secure VPN. You'll
most likely want some kind of remote access solution and then run EM
from there.
--
David Portas
SQL Server MVP
--|||> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
MSDE comes with OSQL , no EM :-)
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
But there is a webTool from MS to administer SQl Server Databases with basic
functionality:
http://www.microsoft.com/downloads/details.aspx?FamilyID=c039a798-c57a-419e-acbc-2a332cb7f959&DisplayLang=en
HTH, Jens Süßmeyer
--
http://www.sqlserver2005.de
--
"Ash Metry" <AshMetry@.discussions.microsoft.com> schrieb im Newsbeitrag
news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...
> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
> -Ash
> "David Portas" wrote:
>> There is no problem in principle running Enterprise Manager or any of
>> the other client tools on a client PC - they are designed for that. You
>> need either a Client Access Licence or a Processor Licence for the
>> server.
>> If you are thinking about access over the Internet however, you won't
>> have the necessary ports open, except maybe via a secure VPN. You'll
>> most likely want some kind of remote access solution and then run EM
>> from there.
>> --
>> David Portas
>> SQL Server MVP
>> --
>>|||MSDE does not come with Enterprise Manager. The MSDE license does not cover
using Enterprise Manager.
Geoff N. Hiten
Microsoft SQL Server MVP
"Ash Metry" <AshMetry@.discussions.microsoft.com> wrote in message
news:033E925D-FB59-4211-BC67-7904A8686A89@.microsoft.com...
> Doesn't MSDE come with the Enterprise Manager and as far as i know the
> MSDE
> is free.
> Does that mean that using the Enterprise Manager that MSDE comes with to
> connect to another SQL server engine requires a licence?
> -Ash
> "David Portas" wrote:
>> There is no problem in principle running Enterprise Manager or any of
>> the other client tools on a client PC - they are designed for that. You
>> need either a Client Access Licence or a Processor Licence for the
>> server.
>> If you are thinking about access over the Internet however, you won't
>> have the necessary ports open, except maybe via a secure VPN. You'll
>> most likely want some kind of remote access solution and then run EM
>> from there.
>> --
>> David Portas
>> SQL Server MVP
>> --
>>
Wednesday, March 7, 2012
Enterprise Manager from desktop
Is there a way to install just the Enterprise Manager on my workstation so I
can access databases on our servers without having to install the whole SQL
Server 2000 program? Thanks.
David
Yes, install just the client tools. This can be done by only selecting the
"Client Tools Only" radio button on the "Installation Definition"
installation window.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"David" <dlchase@.lifetimeinc.com> wrote in message
news:ew0zW4hUEHA.3988@.tk2msftngp13.phx.gbl...
> Is there a way to install just the Enterprise Manager on my workstation so
I
> can access databases on our servers without having to install the whole
SQL
> Server 2000 program? Thanks.
> David
>
can access databases on our servers without having to install the whole SQL
Server 2000 program? Thanks.
David
Yes, install just the client tools. This can be done by only selecting the
"Client Tools Only" radio button on the "Installation Definition"
installation window.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"David" <dlchase@.lifetimeinc.com> wrote in message
news:ew0zW4hUEHA.3988@.tk2msftngp13.phx.gbl...
> Is there a way to install just the Enterprise Manager on my workstation so
I
> can access databases on our servers without having to install the whole
SQL
> Server 2000 program? Thanks.
> David
>
Enterprise Manager from desktop
Is there a way to install just the Enterprise Manager on my workstation so I
can access databases on our servers without having to install the whole SQL
Server 2000 program? Thanks.
DavidYes, install just the client tools. This can be done by only selecting the
"Client Tools Only" radio button on the "Installation Definition"
installation window.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"David" <dlchase@.lifetimeinc.com> wrote in message
news:ew0zW4hUEHA.3988@.tk2msftngp13.phx.gbl...
> Is there a way to install just the Enterprise Manager on my workstation so
I
> can access databases on our servers without having to install the whole
SQL
> Server 2000 program? Thanks.
> David
>
can access databases on our servers without having to install the whole SQL
Server 2000 program? Thanks.
DavidYes, install just the client tools. This can be done by only selecting the
"Client Tools Only" radio button on the "Installation Definition"
installation window.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"David" <dlchase@.lifetimeinc.com> wrote in message
news:ew0zW4hUEHA.3988@.tk2msftngp13.phx.gbl...
> Is there a way to install just the Enterprise Manager on my workstation so
I
> can access databases on our servers without having to install the whole
SQL
> Server 2000 program? Thanks.
> David
>
Enterprise Manager from desktop
Is there a way to install just the Enterprise Manager on my workstation so I
can access databases on our servers without having to install the whole SQL
Server 2000 program? Thanks.
DavidYes, install just the client tools. This can be done by only selecting the
"Client Tools Only" radio button on the "Installation Definition"
installation window.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"David" <dlchase@.lifetimeinc.com> wrote in message
news:ew0zW4hUEHA.3988@.tk2msftngp13.phx.gbl...
> Is there a way to install just the Enterprise Manager on my workstation so
I
> can access databases on our servers without having to install the whole
SQL
> Server 2000 program? Thanks.
> David
>
can access databases on our servers without having to install the whole SQL
Server 2000 program? Thanks.
DavidYes, install just the client tools. This can be done by only selecting the
"Client Tools Only" radio button on the "Installation Definition"
installation window.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"David" <dlchase@.lifetimeinc.com> wrote in message
news:ew0zW4hUEHA.3988@.tk2msftngp13.phx.gbl...
> Is there a way to install just the Enterprise Manager on my workstation so
I
> can access databases on our servers without having to install the whole
SQL
> Server 2000 program? Thanks.
> David
>
Sunday, February 19, 2012
Enterprise Manager and its particularities
Dear all,
I'm fed up with this problem. I hate that behaviour.
When I create objects from a query analyser session in my own workstation,
then these objects doesn't visible from my MMC. A lot of times I am obligate
d
to close and open again.
I've got a MMC with 13 Sql Server and some of them are remote but I don't
think that that aspect could to interfere in the response for do a refresh.
In a fact I do highest level refresh but nothing happens, objects such as
views, sp or tables are missing.
It's a waste time. Why on earth is happening this?
Thanks a lot and regards,Enric wrote:
> Dear all,
> I'm fed up with this problem. I hate that behaviour.
> When I create objects from a query analyser session in my own
> workstation, then these objects doesn't visible from my MMC. A lot of
> times I am obligated to close and open again.
> I've got a MMC with 13 Sql Server and some of them are remote but I
> don't think that that aspect could to interfere in the response for
> do a refresh. In a fact I do highest level refresh but nothing
> happens, objects such as views, sp or tables are missing.
> It's a waste time. Why on earth is happening this?
> Thanks a lot and regards,
I've seen a few others post this issue on SQL EM, but most of us here
have not experienced the problem. With me, anyway, a selecting the
Refresh context menu option performs the necessary refresh and the new
objects appear.
Can you document the steps to consistently reproduce the refresh issue
or is this something that does not occur with any consistency?
Also, what version of SQL EM are you using? Check Help | About and post
the full version.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Enric wrote:
> Dear all,
> I'm fed up with this problem. I hate that behaviour.
> When I create objects from a query analyser session in my own
> workstation, then these objects doesn't visible from my MMC. A lot of
> times I am obligated to close and open again.
> I've got a MMC with 13 Sql Server and some of them are remote but I
> don't think that that aspect could to interfere in the response for
> do a refresh. In a fact I do highest level refresh but nothing
> happens, objects such as views, sp or tables are missing.
> It's a waste time. Why on earth is happening this?
> Thanks a lot and regards,
Clarification: For the version, just let us know what SQL Server service
pack you've installed on your client. The version appears to only show
the major version, not the SP level.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||What happend if instead closing, you just disconnect and connect agaiin to
the server?
AMB
"Enric" wrote:
> Dear all,
> I'm fed up with this problem. I hate that behaviour.
> When I create objects from a query analyser session in my own workstation,
> then these objects doesn't visible from my MMC. A lot of times I am obliga
ted
> to close and open again.
> I've got a MMC with 13 Sql Server and some of them are remote but I don't
> think that that aspect could to interfere in the response for do a refresh
.
> In a fact I do highest level refresh but nothing happens, objects such as
> views, sp or tables are missing.
> It's a waste time. Why on earth is happening this?
> Thanks a lot and regards,|||You need to refresh at the right level. Don't do the highest level. Refresh
doesn't work "all the
way down". Do refresh on the right container.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:259BA9D3-01BE-4962-8F1F-86EB413D4C32@.microsoft.com...
> Dear all,
> I'm fed up with this problem. I hate that behaviour.
> When I create objects from a query analyser session in my own workstation,
> then these objects doesn't visible from my MMC. A lot of times I am obliga
ted
> to close and open again.
> I've got a MMC with 13 Sql Server and some of them are remote but I don't
> think that that aspect could to interfere in the response for do a refresh
.
> In a fact I do highest level refresh but nothing happens, objects such as
> views, sp or tables are missing.
> It's a waste time. Why on earth is happening this?
> Thanks a lot and regards,|||EM is not "active" in the sense that it does not sense changes it does not
make. It is an application that initializes iteslf with data, and knows wha
t
IT does, but not what others (Query Analyzer) do until it re-selects data.
If you want to see new tables, right-click on the "tables" tree in the left
pane and select "refresh". Your new tables will now appear. You can refres
h
at various levels, but the higher-up you go, the longer it will take.
"David Gugick" wrote:
> Enric wrote:
> Clarification: For the version, just let us know what SQL Server service
> pack you've installed on your client. The version appears to only show
> the major version, not the SP level.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||Thanks to all for response.
Tibor,
Your fix not always works.
David,
All the SQL SERVERS (2000) own sp3 and sp3a for olap services.
I think that it could be a network problem between domains or something like
that. There are two sql server which are living in an AD environment, the
rest one running under NT Domains.
Well, I also want understand that maybe to have so many servers at the same
time...
"Tibor Karaszi" wrote:
> You need to refresh at the right level. Don't do the highest level. Refres
h doesn't work "all the
> way down". Do refresh on the right container.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Enric" <Enric@.discussions.microsoft.com> wrote in message
> news:259BA9D3-01BE-4962-8F1F-86EB413D4C32@.microsoft.com...
>|||Enric wrote:
> Thanks to all for response.
> Tibor,
> Your fix not always works.
> David,
> All the SQL SERVERS (2000) own sp3 and sp3a for olap services.
> I think that it could be a network problem between domains or
> something like that. There are two sql server which are living in an
> AD environment, the rest one running under NT Domains.
>
Service Packs should be applied to the client as well as the server.
That's why I asked what version you have on the client. You can check
this from Query Analyzer on the client. You should be running 8.00.760
for SP3/SP3a.
It's possible the RTM release of SQL EM had refresh problems.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Hi
We have in excess of 95 servers in our EM at work, across multiple domains.
The SP is applied to both the servers and client workstations with EM
installed.
Right clicking as described by other posts in this thread works for us 100%
If you have networking problems between domains, you would get errors as the
objects are refreshed out of sysobjects in each database. It either works or
it gives you an error.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:CFD1B642-341C-4A97-8D0B-DFDBF16C15FF@.microsoft.com...
> Thanks to all for response.
> Tibor,
> Your fix not always works.
> David,
> All the SQL SERVERS (2000) own sp3 and sp3a for olap services.
> I think that it could be a network problem between domains or something
> like
> that. There are two sql server which are living in an AD environment, the
> rest one running under NT Domains.
> Well, I also want understand that maybe to have so many servers at the
> same
> time...
> "Tibor Karaszi" wrote:
>
I'm fed up with this problem. I hate that behaviour.
When I create objects from a query analyser session in my own workstation,
then these objects doesn't visible from my MMC. A lot of times I am obligate
d
to close and open again.
I've got a MMC with 13 Sql Server and some of them are remote but I don't
think that that aspect could to interfere in the response for do a refresh.
In a fact I do highest level refresh but nothing happens, objects such as
views, sp or tables are missing.
It's a waste time. Why on earth is happening this?
Thanks a lot and regards,Enric wrote:
> Dear all,
> I'm fed up with this problem. I hate that behaviour.
> When I create objects from a query analyser session in my own
> workstation, then these objects doesn't visible from my MMC. A lot of
> times I am obligated to close and open again.
> I've got a MMC with 13 Sql Server and some of them are remote but I
> don't think that that aspect could to interfere in the response for
> do a refresh. In a fact I do highest level refresh but nothing
> happens, objects such as views, sp or tables are missing.
> It's a waste time. Why on earth is happening this?
> Thanks a lot and regards,
I've seen a few others post this issue on SQL EM, but most of us here
have not experienced the problem. With me, anyway, a selecting the
Refresh context menu option performs the necessary refresh and the new
objects appear.
Can you document the steps to consistently reproduce the refresh issue
or is this something that does not occur with any consistency?
Also, what version of SQL EM are you using? Check Help | About and post
the full version.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Enric wrote:
> Dear all,
> I'm fed up with this problem. I hate that behaviour.
> When I create objects from a query analyser session in my own
> workstation, then these objects doesn't visible from my MMC. A lot of
> times I am obligated to close and open again.
> I've got a MMC with 13 Sql Server and some of them are remote but I
> don't think that that aspect could to interfere in the response for
> do a refresh. In a fact I do highest level refresh but nothing
> happens, objects such as views, sp or tables are missing.
> It's a waste time. Why on earth is happening this?
> Thanks a lot and regards,
Clarification: For the version, just let us know what SQL Server service
pack you've installed on your client. The version appears to only show
the major version, not the SP level.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||What happend if instead closing, you just disconnect and connect agaiin to
the server?
AMB
"Enric" wrote:
> Dear all,
> I'm fed up with this problem. I hate that behaviour.
> When I create objects from a query analyser session in my own workstation,
> then these objects doesn't visible from my MMC. A lot of times I am obliga
ted
> to close and open again.
> I've got a MMC with 13 Sql Server and some of them are remote but I don't
> think that that aspect could to interfere in the response for do a refresh
.
> In a fact I do highest level refresh but nothing happens, objects such as
> views, sp or tables are missing.
> It's a waste time. Why on earth is happening this?
> Thanks a lot and regards,|||You need to refresh at the right level. Don't do the highest level. Refresh
doesn't work "all the
way down". Do refresh on the right container.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:259BA9D3-01BE-4962-8F1F-86EB413D4C32@.microsoft.com...
> Dear all,
> I'm fed up with this problem. I hate that behaviour.
> When I create objects from a query analyser session in my own workstation,
> then these objects doesn't visible from my MMC. A lot of times I am obliga
ted
> to close and open again.
> I've got a MMC with 13 Sql Server and some of them are remote but I don't
> think that that aspect could to interfere in the response for do a refresh
.
> In a fact I do highest level refresh but nothing happens, objects such as
> views, sp or tables are missing.
> It's a waste time. Why on earth is happening this?
> Thanks a lot and regards,|||EM is not "active" in the sense that it does not sense changes it does not
make. It is an application that initializes iteslf with data, and knows wha
t
IT does, but not what others (Query Analyzer) do until it re-selects data.
If you want to see new tables, right-click on the "tables" tree in the left
pane and select "refresh". Your new tables will now appear. You can refres
h
at various levels, but the higher-up you go, the longer it will take.
"David Gugick" wrote:
> Enric wrote:
> Clarification: For the version, just let us know what SQL Server service
> pack you've installed on your client. The version appears to only show
> the major version, not the SP level.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||Thanks to all for response.
Tibor,
Your fix not always works.
David,
All the SQL SERVERS (2000) own sp3 and sp3a for olap services.
I think that it could be a network problem between domains or something like
that. There are two sql server which are living in an AD environment, the
rest one running under NT Domains.
Well, I also want understand that maybe to have so many servers at the same
time...
"Tibor Karaszi" wrote:
> You need to refresh at the right level. Don't do the highest level. Refres
h doesn't work "all the
> way down". Do refresh on the right container.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Enric" <Enric@.discussions.microsoft.com> wrote in message
> news:259BA9D3-01BE-4962-8F1F-86EB413D4C32@.microsoft.com...
>|||Enric wrote:
> Thanks to all for response.
> Tibor,
> Your fix not always works.
> David,
> All the SQL SERVERS (2000) own sp3 and sp3a for olap services.
> I think that it could be a network problem between domains or
> something like that. There are two sql server which are living in an
> AD environment, the rest one running under NT Domains.
>
Service Packs should be applied to the client as well as the server.
That's why I asked what version you have on the client. You can check
this from Query Analyzer on the client. You should be running 8.00.760
for SP3/SP3a.
It's possible the RTM release of SQL EM had refresh problems.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Hi
We have in excess of 95 servers in our EM at work, across multiple domains.
The SP is applied to both the servers and client workstations with EM
installed.
Right clicking as described by other posts in this thread works for us 100%
If you have networking problems between domains, you would get errors as the
objects are refreshed out of sysobjects in each database. It either works or
it gives you an error.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:CFD1B642-341C-4A97-8D0B-DFDBF16C15FF@.microsoft.com...
> Thanks to all for response.
> Tibor,
> Your fix not always works.
> David,
> All the SQL SERVERS (2000) own sp3 and sp3a for olap services.
> I think that it could be a network problem between domains or something
> like
> that. There are two sql server which are living in an AD environment, the
> rest one running under NT Domains.
> Well, I also want understand that maybe to have so many servers at the
> same
> time...
> "Tibor Karaszi" wrote:
>
Subscribe to:
Posts (Atom)