What program are you running? What version? When does the error occur? Give us a hint or two. Terry Broadbent
Please review faq183-874.
"The greatest obstacle to discovery is not ignorance -- it is the illusion of knowledge." - Daniel J Boorstin
Where did you get that information? How do you know that is the problem if you don't know the application being run? If you have a source for your info would you mind sharing it? Terry Broadbent
Please review faq183-874.
"The greatest obstacle to discovery is not ignorance -- it is the illusion of knowledge." - Daniel J Boorstin
I had this when I had installed the SQL 2000 Beta on my local machine some time ago. I had SQL 2000 available on my local machine but the server was still on SQL 7. When I finally upgraded to full release SQL 2000 the problem went away. You may want to check MS TechNet also as they might have a article about it.
That's exactly the behaviour I was seeing. Again upgrading to SQL 2000 cured it, but if that is not in your immediate plans, maybe try applying the latest SQL 7 Service Pack on the machine you are using EM on. MS may have addressed it. Good Luck!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.