Sql Enterprise Edition: error

Showing posts with label error. Show all posts

Thursday, March 29, 2012

EnumErrorlogs using SQLDMO

I am wanting to use the EnumErrorlogs method of the SQLServer object to
identify which of the error logs have been written to in a specified period.
I also need to be able to deploy this to any of our SQL Servers which could
all be running with different locales.
The Date column in the QueryResults output shows this but not in the date
format that I expected. My server is set to English(Australian), my default
language for my login in SQL Server is British English ... i.e. everything is
configured to return dates in the D/M/Y format. However, the date string
returned from EnumErrorlogs is in a M/D/Y format which then messes up the
remainder of my processing.
Is the result ALWAYS returned in M/D/Y ? If so then I could at least code
for that, but if it is possible for it to be in the D/M/Y format then I need
to know where this is set so that I can test for it before continuing to
process the logs.
Can anyone direct me to information about this?
I was hoping it was something to do with the current holder of the ashes (ie
you could have waited about a year for it to fix itself),
but I'm seeing the same here in the UK on totally UK Server. The description
is a bit vague in BOL , going to try a few things.
cheers,
Andy.
"MartinC" <MartinC@.discussions.microsoft.com> wrote in message
news:79DF19A6-89D7-4464-92BF-EC7F6E6B78BB@.microsoft.com...
>I am wanting to use the EnumErrorlogs method of the SQLServer object to
> identify which of the error logs have been written to in a specified
> period.
> I also need to be able to deploy this to any of our SQL Servers which
> could
> all be running with different locales.
> The Date column in the QueryResults output shows this but not in the date
> format that I expected. My server is set to English(Australian), my
> default
> language for my login in SQL Server is British English ... i.e. everything
> is
> configured to return dates in the D/M/Y format. However, the date
> string
> returned from EnumErrorlogs is in a M/D/Y format which then messes up the
> remainder of my processing.
> Is the result ALWAYS returned in M/D/Y ? If so then I could at least
> code
> for that, but if it is possible for it to be in the D/M/Y format then I
> need
> to know where this is set so that I can test for it before continuing to
> process the logs.
> Can anyone direct me to information about this?
|||tried
- Service Account as interactive user with Brit English / UK locale
- changing / reapplying default to UK DD/MM/YY and reboot
giving up, attached is a noddy func to fix
bloody septics :-)
cheers,
Andy.
"Andy Ball" <ng@.spamno77greenfell.com> wrote in message
news:ua3F10v%23FHA.1028@.TK2MSFTNGP11.phx.gbl...
>I was hoping it was something to do with the current holder of the ashes
>(ie
> you could have waited about a year for it to fix itself),
> but I'm seeing the same here in the UK on totally UK Server. The
> description
> is a bit vague in BOL , going to try a few things.
> cheers,
> Andy.
>
> "MartinC" <MartinC@.discussions.microsoft.com> wrote in message
> news:79DF19A6-89D7-4464-92BF-EC7F6E6B78BB@.microsoft.com...
>
begin 666 ConvertErrorlogDate.txt
M( T*)R!A<R!E<G)O<FQO9R!I;B!M+V0O>2!F;W)M870@.:6X@.16YU ;45R<F]R
M3&]G<PT*1G5N8W1I;VX@.0V]N=F5R=$5R<F]R3&]G1&%T92A%<G)O<DQO9T1A
M=&4I#0H)0V]N=F5R=$5R<F]R3&]G1&%T92 ](&-3='(H36ED*$5R<F]R3&]G
M1&%T92PT+#(I("L@.(B\B("L@.;6ED*$5R<F]R3&]G1&%T92P@.,2PR*2 K("(O
J(B K(&UI9"A%<G)O<DQO9T1A=&4L(#<L,C I*0T*16YD($9U;F-T:6]N
`
end

Tuesday, March 27, 2012

Entry point not found with MS SQL Server

Hi All!

Has anyone has seen this error before?

Event Type:Information
Event Source:Application Popup
Event Category:None
Event ID:26
Date:5/14/2004
Time:10:06:45 AM
User:N/A
Description:
Application popup: sqlmangr.exe - Entry Point Not Found : The
procedure entry point TraceMessage could not be located in the dynamic
link library ADVAPI32.dll.

This computer is running MS SQL Server STD Edition 2000 W/ Service
Pack 1.

Thanks!Eric wrote:

> Hi All!
> Has anyone has seen this error before?
> Event Type:Information
> Event Source:Application Popup
> Event Category:None
> Event ID:26
> Date:5/14/2004
> Time:10:06:45 AM
> User:N/A
> Description:
> Application popup: sqlmangr.exe - Entry Point Not Found : The
> procedure entry point TraceMessage could not be located in the dynamic
> link library ADVAPI32.dll.
>
> This computer is running MS SQL Server STD Edition 2000 W/ Service
> Pack 1.
> Thanks!

Usually that means some DLL was updated or not updated while others were
(or were not)...if you can makes sense of that. ;) Basicaly, you likely
have an outdated DLL. That's just a guess.

Zach

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
>

Enterprise Manger Error

I am getting an error:
MMC cannot open the file C:\program files\Miscorosft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an MMC console, or was
creted by a later version of MMC. This may also by because you do not have
sufficient access rights to the file.
I've tried uninstalling/reinstalling reapplying SP3a etc. with no luck.
I did find that renaming the file to anything else will allow it to work.
Which makes for an easy enough work around but was wondering if anybody knew
what is going on?
TIA
Hi
Have you tried running MMC and opening the file from there?
Check the file permissions.
If you have EM on another machine you may want to try copying the file.
Alternatively may want to extract the MSC file from the original CD.
John
"Ken Rinaman" <go@.away.net> wrote in message
news:%23sPCyhiUEHA.2972@.TK2MSFTNGP12.phx.gbl...
> I am getting an error:
> MMC cannot open the file C:\program files\Miscorosft SQL
> Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
> This may be because the file does not exist, is not an MMC console, or was
> creted by a later version of MMC. This may also by because you do not have
> sufficient access rights to the file.
> I've tried uninstalling/reinstalling reapplying SP3a etc. with no luck.
> I did find that renaming the file to anything else will allow it to work.
> Which makes for an easy enough work around but was wondering if anybody
knew
> what is going on?
> TIA
>
|||
> Have you tried running MMC and opening the file from there?
Yes, same error.

> Check the file permissions.
I have the ability to rename, delete, etc.

> If you have EM on another machine you may want to try copying the file.
> Alternatively may want to extract the MSC file from the original CD.
I did pull the file from the CD which is how I discovered changing the name
fixes the problem. On the CD the file is called SQLEM.msc if I copy that
file to my computer it runs fine. However if I rename it to SQL Server
Enterprise Manger.msc it no longer runs.
sql

Wednesday, March 21, 2012

Enterprise Manager won't Start

Why would SQL Enterprise Manager fail to start, and yet
all other applications in the SQL Server program group
start run ok? This is the error message greeting us you
when we click on Enterprise Manager - 'SQLDMO has not
been registered, please re-run SQL Server setup and
contact your system administrator'.
Well, reinstallation didn't help. Users whose
applications are backended by an SQL database are running
ok. I am suspecting a application for remote application
control called Royal TS. Terminal Services are installed
on this server but I doubt this could be the reason, or
could it?
Thanks in advanceThis error normally can be rectified by registering SQLDMO using "regsvr32".
Not sure if your remote server application may be the problem.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"T" <anonymous@.discussions.microsoft.com> wrote in message
news:0a6001c3af5d$b91200d0$a401280a@.phx.gbl...
> Why would SQL Enterprise Manager fail to start, and yet
> all other applications in the SQL Server program group
> start run ok? This is the error message greeting us you
> when we click on Enterprise Manager - 'SQLDMO has not
> been registered, please re-run SQL Server setup and
> contact your system administrator'.
> Well, reinstallation didn't help. Users whose
> applications are backended by an SQL database are running
> ok. I am suspecting a application for remote application
> control called Royal TS. Terminal Services are installed
> on this server but I doubt this could be the reason, or
> could it?
> Thanks in advance

Enterprise Manager Won't Start

All of a sudden, whenever I try to start the SQL Server
Enterprise Manager, I get the following error:
MMC cannot open the file C:\Program File\...\SQL Server
Enterprise Manager.MSC.
This may be because the file does not exist, is not an
MMC console, or was created by a later version of MMC.
This may also be because you do not have sufficient
access rights to the file.
I've uninstalled and re-installed SQL Server at least
four times now. I still get the same error. What is
going on? The file exists. I can see it. Please, I
need some insight on this. Help!Does the account SQL Server is using have rights to the
directory? that would be my first guess
>--Original Message--
>All of a sudden, whenever I try to start the SQL Server
>Enterprise Manager, I get the following error:
>MMC cannot open the file C:\Program File\...\SQL Server
>Enterprise Manager.MSC.
>This may be because the file does not exist, is not an
>MMC console, or was created by a later version of MMC.
>This may also be because you do not have sufficient
>access rights to the file.
>I've uninstalled and re-installed SQL Server at least
>four times now. I still get the same error. What is
>going on? The file exists. I can see it. Please, I
>need some insight on this. Help!
>.
>|||Glenn,
Try reapplying the latest SQL Server 2000 service pack. If that doesn't
work try copying SQLEM.MSC from the SQL Server CD (remember to rename it
to Enterprise Manager.msc on your machine).
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:
> All of a sudden, whenever I try to start the SQL Server
> Enterprise Manager, I get the following error:
> MMC cannot open the file C:\Program File\...\SQL Server
> Enterprise Manager.MSC.
> This may be because the file does not exist, is not an
> MMC console, or was created by a later version of MMC.
> This may also be because you do not have sufficient
> access rights to the file.
> I've uninstalled and re-installed SQL Server at least
> four times now. I still get the same error. What is
> going on? The file exists. I can see it. Please, I
> need some insight on this. Help!|||Still no success. I have:
1. Verified all of the file permissions.
2. Installed SP3a.
3. Copied the SQLEM.MSC file, renamed it.
I still get the same error.
Any other possibilities?
Glenn Cadoret
>--Original Message--
>Glenn,
>Try reapplying the latest SQL Server 2000 service pack.
If that doesn't
>work try copying SQLEM.MSC from the SQL Server CD
(remember to rename it
>to Enterprise Manager.msc on your machine).
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Glenn Cadoret wrote:
>> All of a sudden, whenever I try to start the SQL
Server
>> Enterprise Manager, I get the following error:
>> MMC cannot open the file C:\Program File\...\SQL
Server
>> Enterprise Manager.MSC.
>> This may be because the file does not exist, is not an
>> MMC console, or was created by a later version of
MMC.
>> This may also be because you do not have sufficient
>> access rights to the file.
>> I've uninstalled and re-installed SQL Server at least
>> four times now. I still get the same error. What is
>> going on? The file exists. I can see it. Please, I
>> need some insight on this. Help!
>.
>|||Glenn,
Well, it sounds like a permissions issue to me. What did you change? ;-)
Can you log on as local administrator and open EM?
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Glenn Cadoret wrote:
> Still no success. I have:
> 1. Verified all of the file permissions.
> 2. Installed SP3a.
> 3. Copied the SQLEM.MSC file, renamed it.
> I still get the same error.
> Any other possibilities?
> Glenn Cadoret
>
>>--Original Message--
>>Glenn,
>>Try reapplying the latest SQL Server 2000 service pack.
> If that doesn't
>>work try copying SQLEM.MSC from the SQL Server CD
> (remember to rename it
>>to Enterprise Manager.msc on your machine).
>>--
>>Mark Allison, SQL Server MVP
>>http://www.markallison.co.uk
>>Looking for a SQL Server replication book?
>>http://www.nwsu.com/0974973602.html
>>
>>Glenn Cadoret wrote:
>>All of a sudden, whenever I try to start the SQL
> Server
>>Enterprise Manager, I get the following error:
>>MMC cannot open the file C:\Program File\...\SQL
> Server
>>Enterprise Manager.MSC.
>>This may be because the file does not exist, is not an
>>MMC console, or was created by a later version of
> MMC.
>>This may also be because you do not have sufficient
>>access rights to the file.
>>I've uninstalled and re-installed SQL Server at least
>>four times now. I still get the same error. What is
>>going on? The file exists. I can see it. Please, I
>>need some insight on this. Help!
>>.sql

Enterprise Manager Won't Run

I am unable to start my Enterprise Manager. I get the following error message:
"Microsoft Management Console has encountered a problem and needs to close".
This is a SQL 2000 system.
This happened one day for no apparent reason. I use SQL Enterprise Manager
everyday. I have uninstalled and reinstalled the product and have the same
problem.
Help is appreciated. Thanks.
Hi
Have you tried to run MMC on it's own and then open up the SQL Server
Enterprise Manager MMC?
John
"john" <john@.discussions.microsoft.com> wrote in message
news:4AA5174A-D9C1-4FA1-979C-3DAC67521A14@.microsoft.com...
>I am unable to start my Enterprise Manager. I get the following error
>message:
> "Microsoft Management Console has encountered a problem and needs to
> close".
> This is a SQL 2000 system.
> This happened one day for no apparent reason. I use SQL Enterprise Manager
> everyday. I have uninstalled and reinstalled the product and have the same
> problem.
> Help is appreciated. Thanks.
|||Yes, I can start say Computer Management which uses the MMC and it opens just
fine. I can leave it open and then try to start the Enterprise Manaer and i
get the same problem. I am not sure if they use the same version of the MMC
or not.
"John Bell" wrote:

> Hi
> Have you tried to run MMC on it's own and then open up the SQL Server
> Enterprise Manager MMC?
> John
> "john" <john@.discussions.microsoft.com> wrote in message
> news:4AA5174A-D9C1-4FA1-979C-3DAC67521A14@.microsoft.com...
>
>
|||Hi
You can therefore try and open the SQL Server Enterprise Manager.mmc from
the tools (or the tools/html) directory.
You could try copying the file from another machine and possibly renaming
it, if it continues to cause an issue.
John
"john" <john@.discussions.microsoft.com> wrote in message
news:C9132729-931C-488D-9F96-63AB177CA33D@.microsoft.com...[vbcol=seagreen]
> Yes, I can start say Computer Management which uses the MMC and it opens
> just
> fine. I can leave it open and then try to start the Enterprise Manaer and
> i
> get the same problem. I am not sure if they use the same version of the
> MMC
> or not.
>
> "John Bell" wrote:
|||I tried copying the MMC from another computer that can run enterprise Manager
and i had the same problem. Then I renamed it as you siuggested and now it
will run. That seems so strange. Any ideas why this works?
thanks for your help
john
"John Bell" wrote:

> Hi
> You can therefore try and open the SQL Server Enterprise Manager.mmc from
> the tools (or the tools/html) directory.
> You could try copying the file from another machine and possibly renaming
> it, if it continues to cause an issue.
> John
> "john" <john@.discussions.microsoft.com> wrote in message
> news:C9132729-931C-488D-9F96-63AB177CA33D@.microsoft.com...
>
>
|||Did you try to register a custom MMC ? Open Managment Console, File
Add/Remove Snappin, Add , SQL Server Enterprise Manager
Save the Console under a known destination path, try to open it from
this msc file.
Would be interesting if the problems occurs after creating this custom
console.
HTH, jens Suessmeyer.

Enterprise Manager Unknown Error

I am running SQL2000 sp3 with 819 hotfix on a 2003
Cluster. When I am on one of the database servers in the
cluster I can select from a table and get data returned.
When I am on the webserver and use EnterPrise I can see
the tables but when I try to select I get 'Unknown Error'.
The same select works from ISQL/W GUI and isql at the
command line while on the webserver.
Any ideas on what to look for would be helpful, nothing is
being logged in the eventlog or the sql log.
Thanks
Check the following;
- The MDAC version on the good and the bad machine. If possible upgrade to
the latest version of MDAC
- Capture the T-SQL command from profiler while you are try to retrieve the
data and see if you can identify the issue.
- Permissions
- The client configuration options by comparing them to the good machine.
HTH
SQL Server Support
Agnes Panosian

Monday, March 19, 2012

Enterprise manager SQLServer2000

When I click on Enterprise manager->Database this is the error I am getting:
A runtime error has occurred. Do you wish to debug. Line 306 Error: unspecified error. Yes/No

This is happening on user databases only not the SQL standard dbs; pubs,master,northwind.

How can I fix this?

Thanks for any help.
VinnieAre you clicking from a client workstation, server console, server console through Terminal Services client, etc.? More details needed.|||I am clicking (Left click)
SQLServer Enterprise Manager
Microsoft SQLserver
SQLServer Group
Myhost
Databases
MYDATABASE

it displays the error:
Runtime Error occurred. Line 306
when I say debug/yes it displays a program code.|||Through My PC Desktop.|||Do you have the latest service pack installed? If you do, I would just reinstall the Client Tools. It will be a lot quicker than trying to figure this out.

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...
>
>

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...
>
>

Sunday, March 11, 2012

Enterprise Manager Problem

Suddenly one of my user started seeing one problem.. Whenever he tries
to connect to database and see tables through enterprise manager. Gets
error as shown below.
"An unexpected error happened during this operation.
[MS Design Tools] - You might not have permission to perform this
operation, or the object Administrator might no longer exist in
database."
Though previously there wasn't any problem.. I just droped and
recreated this login with same permission as previously. Even tried
assigning system administrator role to the login but no success.
Please help
Thanks
NJTry reinstall the client.
Quentin
"neeju" <njvds.o11@.gmail.com> wrote in message
news:1138897109.940035.202020@.z14g2000cwz.googlegroups.com...
> Suddenly one of my user started seeing one problem.. Whenever he tries
> to connect to database and see tables through enterprise manager. Gets
> error as shown below.
> "An unexpected error happened during this operation.
> [MS Design Tools] - You might not have permission to perform this
> operation, or the object Administrator might no longer exist in
> database."
>
> Though previously there wasn't any problem.. I just droped and
> recreated this login with same permission as previously. Even tried
> assigning system administrator role to the login but no success.
> Please help
> Thanks
> NJ
>

Enterprise Manager Open Table/Return All Rows

After upgrading Windows 2000 server to Windows Server 2003 Standard Edition
I'm receiving a '8007007F Unknown Error' when I use the 'Open Table/Return
All Rows' right click option in Enterprise Manager (SQL 2000 sp3a).
Although not exactly my issue KnowledgeBase Article 817301 suggested
re-registering query.dll and tquery.dll. I've tried this and I'm still
having the same issue. If anyone is knows of this issue please respond.
Thank-you,
EWDI'd try re-installing the tools...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Ernest Dungy" <ewdungy@.msn-DONTSENDSPAM.com> wrote in message
news:Ormc6wexEHA.1988@.TK2MSFTNGP12.phx.gbl...
> After upgrading Windows 2000 server to Windows Server 2003 Standard
Edition
> I'm receiving a '8007007F Unknown Error' when I use the 'Open Table/Return
> All Rows' right click option in Enterprise Manager (SQL 2000 sp3a).
> Although not exactly my issue KnowledgeBase Article 817301 suggested
> re-registering query.dll and tquery.dll. I've tried this and I'm still
> having the same issue. If anyone is knows of this issue please respond.
> Thank-you,
> EWD
>|||Thanks Wayne, I tried re-installing the tools and uninstall/re-install of
the SQL Server but I received the same error.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:uwOsI0lxEHA.1196@.TK2MSFTNGP15.phx.gbl...
> I'd try re-installing the tools...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Ernest Dungy" <ewdungy@.msn-DONTSENDSPAM.com> wrote in message
> news:Ormc6wexEHA.1988@.TK2MSFTNGP12.phx.gbl...
> > After upgrading Windows 2000 server to Windows Server 2003 Standard
> Edition
> > I'm receiving a '8007007F Unknown Error' when I use the 'Open
Table/Return
> > All Rows' right click option in Enterprise Manager (SQL 2000 sp3a).
> > Although not exactly my issue KnowledgeBase Article 817301 suggested
> > re-registering query.dll and tquery.dll. I've tried this and I'm still
> > having the same issue. If anyone is knows of this issue please respond.
> >
> > Thank-you,
> > EWD
> >
> >
>|||Ernest, I am receiving the same error. Can you tell me if you were able to
fix your issue?
Thanks
Derek
"Ernest" wrote:
> Thanks Wayne, I tried re-installing the tools and uninstall/re-install of
> the SQL Server but I received the same error.
> "Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
> news:uwOsI0lxEHA.1196@.TK2MSFTNGP15.phx.gbl...
> > I'd try re-installing the tools...
> >
> > --
> > Wayne Snyder, MCDBA, SQL Server MVP
> > Mariner, Charlotte, NC
> > www.mariner-usa.com
> > (Please respond only to the newsgroups.)
> >
> > I support the Professional Association of SQL Server (PASS) and it's
> > community of SQL Server professionals.
> > www.sqlpass.org
> >
> > "Ernest Dungy" <ewdungy@.msn-DONTSENDSPAM.com> wrote in message
> > news:Ormc6wexEHA.1988@.TK2MSFTNGP12.phx.gbl...
> > > After upgrading Windows 2000 server to Windows Server 2003 Standard
> > Edition
> > > I'm receiving a '8007007F Unknown Error' when I use the 'Open
> Table/Return
> > > All Rows' right click option in Enterprise Manager (SQL 2000 sp3a).
> > > Although not exactly my issue KnowledgeBase Article 817301 suggested
> > > re-registering query.dll and tquery.dll. I've tried this and I'm still
> > > having the same issue. If anyone is knows of this issue please respond.
> > >
> > > Thank-you,
> > > EWD
> > >
> > >
> >
> >
>
>

Friday, March 9, 2012

enterprise manager loading DB

Hello
I have a problem with a loading DB in Enterprise Manager.
I had restored a DB from another Sql Server and something seems wrong. Ive
got no error message but I have a grey DB Icon with my DB Name and a loading
behind the name. I cant delete the DB with Enterprise manager, cant open
the properties nothing.
I have tried in Sql Query analyzer to drop the database, but Ive got an
error that the db cant be deleted because an use for replication exist.
On the Sql Server where I have restored the DB is no replication configured
only on the sql server where the backup was made.
Any idea how to remove the DB?
(Sql Server 2000 sp3)
Thx
BjrnPerhaps the restore was done using NORECOVERY option? Try:
RESTORE DATABASE dbname WITH RECOVERY
That would make the database accessible. Then drop the database, possibly re
moving replication
config first if needed (Google for details...).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bjrn" <prodevelop@.gmx.net> wrote in message news:O0SgxiqyGHA.3568@.TK2MSFTNGP03.phx.gbl...[
vbcol=seagreen]
> Hello
> I have a problem with a loading DB in Enterprise Manager.
> I had restored a DB from another Sql Server and something seems wrong. Iv
e
> got no error message but I have a grey DB Icon with my DB Name and a loadi
ng
> behind the name. I cant delete the DB with Enterprise manager, cant open
> the properties nothing.
> I have tried in Sql Query analyzer to drop the database, but Ive got an
> error that the db cant be deleted because an use for replication exist.
> On the Sql Server where I have restored the DB is no replication configure
d
> only on the sql server where the backup was made.
> Any idea how to remove the DB?
> (Sql Server 2000 sp3)
> Thx
> Bjrn
>[/vbcol]|||Hi,
Add on to Tibor; You could also try
RESTORE LOG dbname WITH RECOVERY
Thanks
Hari
SQL Server MVP
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ehrzeNsyGHA.4976@.TK2MSFTNGP04.phx.gbl...
> Perhaps the restore was done using NORECOVERY option? Try:
> RESTORE DATABASE dbname WITH RECOVERY
> That would make the database accessible. Then drop the database, possibly
> removing replication config first if needed (Google for details...).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Bjrn" <prodevelop@.gmx.net> wrote in message
> news:O0SgxiqyGHA.3568@.TK2MSFTNGP03.phx.gbl...
>|||Hi
Thx for your answer
Now the DB is deleted

regards
Bjrn
"Hari Prasad" <hari_prasad_k@.hotmail.com> schrieb im Newsbeitrag
news:#tECW2wyGHA.3568@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Add on to Tibor; You could also try
> RESTORE LOG dbname WITH RECOVERY
> Thanks
> Hari
> SQL Server MVP
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in
> message news:ehrzeNsyGHA.4976@.TK2MSFTNGP04.phx.gbl...
possibly[vbcol=seagreen]
an[vbcol=seagreen]
exist.[vbcol=seagreen]
>

Enterprise Manager launch error

Not sure what has caused this to suddenly happen, but each time I attempt to launch Enterprise Manager I get the error:

"MMC cannot open the file C:\MSSQL\BINN\SQL Server Enterprises Manager.MSC
This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient access rights to the file."

Now, I've already attempted to reinstall the client tools with no luck. The file does exist, and I have not changed my security settings -- at least that I'm aware of.

I use EM daily, so I'm perplexed as to why over night it stopped working. Is it possible a Windows Update could have caused this?

If you have any insight I'd appreciate it. Thanks.

PS. I'm using SQL 7.0 on a WinXP Pro laptop.

DavidI feel there could be some issue with h/w on the box and may refer to this KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;315341 to fix it.

Ensure to obtain latest service pack for XP also, if nothing works reinstall from scratch.

Enterprise Manager html error

Normally in Enterprise Manager the right hand pane displays icoms for
Diagrams, Tables, Views, etc. when a particulat database is clicked on in the
left hand pane.
For one particulat database, and only one, Enterprise Manager attempts to
display an html page with various tabs but this errors when loading and
displays wthout any information on it.
Why is this database differnet - I can't find any setting wich controls this
display or indeed any reference in BOL, and can I change it?
The error pops up an alert box as follows:
A Runtime Error has occurred.
Do you wish to Debug?
Line: 306
Error: Unspecified error.
unknown exeption
Break
Res://C:\...\sqlmmc.rll/Tabs.html
szDB =
parent.window.objSQLNSContext.GetDisplayName(strCo ntextCookie)
strContextCookie = GetParameterX("SQLNSCookie");
szDB = undefined
strContextCookie = "00FA25200000000000000001"
The line is called from JScript global code.
So, secondly, what is the error and can I fix it?
Thanks
Grant Ord
Grant,
You need to click on the database and then on the View tab change to
something other than Taskpad. Then change to Taskpad. The details should now
be fine. It is a known bug I think.
Chris Wood
Alberta Department of Energy
CANADA
"Grant Ord" <grant.ord@.nospam.nospam> wrote in message
news:1D78B191-9D4C-4834-957B-E07828400110@.microsoft.com...
> Normally in Enterprise Manager the right hand pane displays icoms for
> Diagrams, Tables, Views, etc. when a particulat database is clicked on in
the
> left hand pane.
> For one particulat database, and only one, Enterprise Manager attempts to
> display an html page with various tabs but this errors when loading and
> displays wthout any information on it.
> Why is this database differnet - I can't find any setting wich controls
this
> display or indeed any reference in BOL, and can I change it?
> The error pops up an alert box as follows:
> A Runtime Error has occurred.
> Do you wish to Debug?
> Line: 306
> Error: Unspecified error.
>
> unknown exeption
> Break
> Res://C:\...\sqlmmc.rll/Tabs.html
> szDB =
> parent.window.objSQLNSContext.GetDisplayName(strCo ntextCookie)
> strContextCookie = GetParameterX("SQLNSCookie");
> szDB = undefined
> strContextCookie = "00FA25200000000000000001"
> The line is called from JScript global code.
> So, secondly, what is the error and can I fix it?
> --
> Thanks
> Grant Ord
|||http://www.aspfaq.com/2293
http://www.aspfaq.com/
(Reverse address to reply.)
"Grant Ord" <grant.ord@.nospam.nospam> wrote in message
news:1D78B191-9D4C-4834-957B-E07828400110@.microsoft.com...
> Normally in Enterprise Manager the right hand pane displays icoms for
> Diagrams, Tables, Views, etc. when a particulat database is clicked on in
the
> left hand pane.
> For one particulat database, and only one, Enterprise Manager attempts to
> display an html page with various tabs but this errors when loading and
> displays wthout any information on it.
> Why is this database differnet - I can't find any setting wich controls
this
> display or indeed any reference in BOL, and can I change it?
> The error pops up an alert box as follows:
> A Runtime Error has occurred.
> Do you wish to Debug?
> Line: 306
> Error: Unspecified error.
>
> unknown exeption
> Break
> Res://C:\...\sqlmmc.rll/Tabs.html
> szDB =
> parent.window.objSQLNSContext.GetDisplayName(strCo ntextCookie)
> strContextCookie = GetParameterX("SQLNSCookie");
> szDB = undefined
> strContextCookie = "00FA25200000000000000001"
> The line is called from JScript global code.
> So, secondly, what is the error and can I fix it?
> --
> Thanks
> Grant Ord

Enterprise Manager html error

Normally in Enterprise Manager the right hand pane displays icoms for
Diagrams, Tables, Views, etc. when a particulat database is clicked on in the
left hand pane.
For one particulat database, and only one, Enterprise Manager attempts to
display an html page with various tabs but this errors when loading and
displays wthout any information on it.
Why is this database differnet - I can't find any setting wich controls this
display or indeed any reference in BOL, and can I change it?
The error pops up an alert box as follows:
A Runtime Error has occurred.
Do you wish to Debug?
Line: 306
Error: Unspecified error.
unknown exeption
Break
Res://C:\...\sqlmmc.rll/Tabs.html
szDB = parent.window.objSQLNSContext.GetDisplayName(strContextCookie)
strContextCookie = GetParameterX("SQLNSCookie");
szDB = undefined
strContextCookie = "00FA25200000000000000001"
The line is called from JScript global code.
So, secondly, what is the error and can I fix it?
--
Thanks
Grant OrdGrant,
You need to click on the database and then on the View tab change to
something other than Taskpad. Then change to Taskpad. The details should now
be fine. It is a known bug I think.
Chris Wood
Alberta Department of Energy
CANADA
"Grant Ord" <grant.ord@.nospam.nospam> wrote in message
news:1D78B191-9D4C-4834-957B-E07828400110@.microsoft.com...
> Normally in Enterprise Manager the right hand pane displays icoms for
> Diagrams, Tables, Views, etc. when a particulat database is clicked on in
the
> left hand pane.
> For one particulat database, and only one, Enterprise Manager attempts to
> display an html page with various tabs but this errors when loading and
> displays wthout any information on it.
> Why is this database differnet - I can't find any setting wich controls
this
> display or indeed any reference in BOL, and can I change it?
> The error pops up an alert box as follows:
> A Runtime Error has occurred.
> Do you wish to Debug?
> Line: 306
> Error: Unspecified error.
>
> unknown exeption
> Break
> Res://C:\...\sqlmmc.rll/Tabs.html
> szDB => parent.window.objSQLNSContext.GetDisplayName(strContextCookie)
> strContextCookie = GetParameterX("SQLNSCookie");
> szDB = undefined
> strContextCookie = "00FA25200000000000000001"
> The line is called from JScript global code.
> So, secondly, what is the error and can I fix it?
> --
> Thanks
> Grant Ord|||http://www.aspfaq.com/2293
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Grant Ord" <grant.ord@.nospam.nospam> wrote in message
news:1D78B191-9D4C-4834-957B-E07828400110@.microsoft.com...
> Normally in Enterprise Manager the right hand pane displays icoms for
> Diagrams, Tables, Views, etc. when a particulat database is clicked on in
the
> left hand pane.
> For one particulat database, and only one, Enterprise Manager attempts to
> display an html page with various tabs but this errors when loading and
> displays wthout any information on it.
> Why is this database differnet - I can't find any setting wich controls
this
> display or indeed any reference in BOL, and can I change it?
> The error pops up an alert box as follows:
> A Runtime Error has occurred.
> Do you wish to Debug?
> Line: 306
> Error: Unspecified error.
>
> unknown exeption
> Break
> Res://C:\...\sqlmmc.rll/Tabs.html
> szDB => parent.window.objSQLNSContext.GetDisplayName(strContextCookie)
> strContextCookie = GetParameterX("SQLNSCookie");
> szDB = undefined
> strContextCookie = "00FA25200000000000000001"
> The line is called from JScript global code.
> So, secondly, what is the error and can I fix it?
> --
> Thanks
> Grant Ord

Thursday, March 29, 2012

EnumErrorlogs using SQLDMO

Tuesday, March 27, 2012

Entry point not found with MS SQL Server

Thursday, March 22, 2012

Enterprise Mgr Error

Enterprise Mgr Error

Enterprise Manger Error

Wednesday, March 21, 2012

Enterprise Manager won't Start

Enterprise Manager Won't Start

Enterprise Manager Won't Run

Enterprise Manager Unknown Error

Monday, March 19, 2012

Enterprise manager SQLServer2000

Enterprise Manager Server Registration General Network Error

Enterprise Manager Server Registration General Network Error

Sunday, March 11, 2012

Enterprise Manager Problem

Enterprise Manager Open Table/Return All Rows

Enterprise Manager Open Table/Return All Rows

Enterprise Manager Open Table/Return All Rows

Friday, March 9, 2012

enterprise manager loading DB

Enterprise Manager launch error

Enterprise Manager html error

Enterprise Manager html error

Sql Enterprise Edition

Blog Archive

About Me