Monday, March 19, 2012
Error 7102
error in log-file:
Error 7102 Serverity 20 State 0
SQL Server Internal Error. Text manager cannot continue with current
statement.
OS: Windows 2000 Advanced Server SP4.Hi white,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You get the Error
7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
please feel free to point it out.
Error 7102 is a general error. Would you please provide some detail
information to narrow down the issue?
1. Using DBCC CHECKDB to see is there any error messages.
2. What do you get in the Application and System event log? Would your
please post it here?
3. Are you able to trace what the database is doing when you get this
error?
Please let us know the result. I look forward your reply.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Lu!
1. DBCC CHECKDB is executed every night. Error messages are absent.
2. There are no error and warning messages in the Application and System
event log. To post there is nothing.
3. 7102 error messages arises seldom. Trace is now turn on.
"Wei Lu" wrote:
> Hi white,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You get the Erro
r
> 7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern
,
> please feel free to point it out.
> Error 7102 is a general error. Would you please provide some detail
> information to narrow down the issue?
> 1. Using DBCC CHECKDB to see is there any error messages.
> 2. What do you get in the Application and System event log? Would you
r
> please post it here?
> 3. Are you able to trace what the database is doing when you get this
> error?
> Please let us know the result. I look forward your reply.
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi white,
Thanks for the update. Please gather the trace and to see what have you
done before these error arised.
Wei Lu
Microsoft Online Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Error 7102
error in log-file:
Error 7102 Serverity 20 State 0
SQL Server Internal Error. Text manager cannot continue with current
statement.
OS: Windows 2000 Advanced Server SP4.Hi white,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You get the Error
7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
please feel free to point it out.
Error 7102 is a general error. Would you please provide some detail
information to narrow down the issue?
1. Using DBCC CHECKDB to see is there any error messages.
2. What do you get in the Application and System event log? Would your
please post it here?
3. Are you able to trace what the database is doing when you get this
error?
Please let us know the result. I look forward your reply.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Lu!
1. DBCC CHECKDB is executed every night. Error messages are absent.
2. There are no error and warning messages in the Application and System
event log. To post there is nothing.
3. 7102 error messages arises seldom. Trace is now turn on.
"Wei Lu" wrote:
> Hi white,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You get the Error
> 7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
> please feel free to point it out.
> Error 7102 is a general error. Would you please provide some detail
> information to narrow down the issue?
> 1. Using DBCC CHECKDB to see is there any error messages.
> 2. What do you get in the Application and System event log? Would your
> please post it here?
> 3. Are you able to trace what the database is doing when you get this
> error?
> Please let us know the result. I look forward your reply.
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi white,
Thanks for the update. Please gather the trace and to see what have you
done before these error arised.
Wei Lu
Microsoft Online Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Error 7102
error in log-file:
Error 7102 Serverity 20 State 0
SQL Server Internal Error. Text manager cannot continue with current
statement.
OS: Windows 2000 Advanced Server SP4.
Hi white,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: You get the Error
7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
please feel free to point it out.
Error 7102 is a general error. Would you please provide some detail
information to narrow down the issue?
1. Using DBCC CHECKDB to see is there any error messages.
2. What do you get in the Application and System event log? Would your
please post it here?
3. Are you able to trace what the database is doing when you get this
error?
Please let us know the result. I look forward your reply.
Wei Lu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Lu!
1. DBCC CHECKDB is executed every night. Error messages are absent.
2. There are no error and warning messages in the Application and System
event log. To post there is nothing.
3. 7102 error messages arises seldom. Trace is now turn on.
"Wei Lu" wrote:
> Hi white,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: You get the Error
> 7102 in the SQL Server 2000 SP4 Error log. If I misunderstood your concern,
> please feel free to point it out.
> Error 7102 is a general error. Would you please provide some detail
> information to narrow down the issue?
> 1. Using DBCC CHECKDB to see is there any error messages.
> 2. What do you get in the Application and System event log? Would your
> please post it here?
> 3. Are you able to trace what the database is doing when you get this
> error?
> Please let us know the result. I look forward your reply.
> Wei Lu
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi white,
Thanks for the update. Please gather the trace and to see what have you
done before these error arised.
Wei Lu
Microsoft Online Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Sunday, March 11, 2012
Error 605
installation.
They've started to get this error in the log usually when the reindex-job is
running on the database but sometimes at other times too:
DBCC CHECKDB (ProductionDB) executed by DOMAIN\user01 found 0 errors and
repaired 0 errors.
Getpage: bstat=0x9, sstat=0, cache
pageno is/should be: objid is/should be:
Getpage: bstat=0x9, sstat=0, cache
Getpage: bstat=0x9, sstat=0, cache
pageno is/should be: objid is/should be:
Getpage: bstat=0x9, sstat=0, cache
(1:1772011)/(1:1772011) 0/930818378
pageno is/should be: objid is/should be:
pageno is/should be: objid is/should be:
(1:1772011)/(1:1772011) 0/930818378
(1:1772011)/(1:1772011) 0/930818378
(1:1772011)/(1:1772011) 0/930818378
... IAM indicates that page is allocated to this object
... IAM indicates that page is allocated to this object
... IAM indicates that page is allocated to this object
... IAM indicates that page is allocated to this object
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:1772011) in database 'ProductionDB' belongs
to object '0', not to object 'Table1'..
The server is a failover-clustered server with SQL 2000 and Windows 2000.
Before this problem they had a problematic HD that they replaced. The
problem seemed to be gone after the replacement but resurfaced a little
later.
I started to think that the problem was related to the write-cache, so I
checked the write-cache on raid-controller and it was turned off. Wanting to
know if there was a possibility that the write-cache on the HDs was the
problem I got the answer that there is no cache on the disks or at least no
possablity to turn of the disk cache on them?
I also get this message in the beginning of the sqliostress-testlog:
"*** WARNING: Write caching ALLOWED"
I still had a feeling that the problem was hardware related and ran
sqliostress.exe and it came through fine. Thinking that the problem just
appears under load I ran 5 simultanious instances of sqliostress and got a
problem in one of the logs:
Pattern for page 1 is A
ERROR: LSN not found for page 1. Currently at slot 1 page 1 in log
searching for LSN 3
---
ERROR: Did not find expected pattern in file for page 1.
Bytes read = 8192
Potential torn write
---
Sector: 0 LSN: 3 Page: 0
[AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA...[sic]
ERROR: Appears to be a premature truncation of file. Pages expected: 32000,
Pages Read: 1, Last Error: 0
Current LSN is 32001
Verifing complete.
Ok, what next? Is the problem the HD-cache or something else in the
raid-system that possibly could create this problem or should I look
somewhere else?Anyone?|||Hi John, your assumptions are the same as the ones I would have
probably jumped to. Lets assume that the DB is inconsistent (perhaps
down to that faulty drive) ....
You say you are running the DBCC checkdb command, however have you
tried actually repairing the db using on of the repair parameters. I
would probably start off with the REPAIR_FAST option (if it is a
production db), but you might have to bite the bullet and use
REPAIR_ALLOW_DATA_LOSS might be an idea to do it with WITH ALL_ERRORMSGS
Br,
Mark Broadbent
mcdba , mcse+i
=============|||Mark Broadbent wrote:
> Hi John, your assumptions are the same as the ones I would have
> probably jumped to. Lets assume that the DB is inconsistent (perhaps
> down to that faulty drive) ....
> You say you are running the DBCC checkdb command, however have you
> tried actually repairing the db using on of the repair parameters. I
> would probably start off with the REPAIR_FAST option (if it is a
> production db), but you might have to bite the bullet and use
> REPAIR_ALLOW_DATA_LOSS might be an idea to do it with WITH
> ALL_ERRORMSGS
and I should add.. make sure you have a current backup to rely upon
before you start this process.
--
Br,
Mark Broadbent
mcdba , mcse+i
=============|||Thanks for your answer Mark!
Yes, I've tried running dbcc repair and it showed no problems.
After these error is reported I always also run a dbcc checkdb which
doesen't indicate any problems.
The problem is that the nightly reindex job is failing about half the times
with this error (it runs 3 times a week).
I started to belive that there was an "erranous errormessage" and that the
data wasn't damaged becaus the checks and repairs never reported any
problems.
However two weeks ago the same problem appeared and this time there was some
damage to one of the tables...after a repair with dataloss the problem was
fixed though (luckily it wasn't any table that contained uniqe data this
time...).
I also have tried to create a new empty database and transfer the data
there, in the case that the disk problems that has been fixed had made some
sort of "invisible" damage to the database that the checks couldn't fix. It
didn't fix the problem however.
The breakthrough as I see it is that I think that I've managed to reproduced
the problem by running sqliostress in five parallel instances and got one a
possible torn page in one of the logs...that should indicate a problem in
the disk-subsystem...right?
"Mark Broadbent" <no-spam-please_mark.broadbent@.virgin.net> wrote in message
news:#kMJelDqDHA.644@.TK2MSFTNGP11.phx.gbl...
> Hi John, your assumptions are the same as the ones I would have
> probably jumped to. Lets assume that the DB is inconsistent (perhaps
> down to that faulty drive) ....
> You say you are running the DBCC checkdb command, however have you
> tried actually repairing the db using on of the repair parameters. I
> would probably start off with the REPAIR_FAST option (if it is a
> production db), but you might have to bite the bullet and use
> REPAIR_ALLOW_DATA_LOSS might be an idea to do it with WITH ALL_ERRORMSGS
>
> --
> Br,
> Mark Broadbent
> mcdba , mcse+i
> =============|||John Horn wrote:
> Thanks for your answer Mark!
> Yes, I've tried running dbcc repair and it showed no problems.
> After these error is reported I always also run a dbcc checkdb which
> doesen't indicate any problems.
> The problem is that the nightly reindex job is failing about half the
> times with this error (it runs 3 times a week).
> I started to belive that there was an "erranous errormessage" and
> that the data wasn't damaged becaus the checks and repairs never
> reported any problems.
> However two weeks ago the same problem appeared and this time there
> was some damage to one of the tables...after a repair with dataloss
> the problem was fixed though (luckily it wasn't any table that
> contained uniqe data this time...).
> I also have tried to create a new empty database and transfer the data
> there, in the case that the disk problems that has been fixed had
> made some sort of "invisible" damage to the database that the checks
> couldn't fix. It didn't fix the problem however.
> The breakthrough as I see it is that I think that I've managed to
> reproduced the problem by running sqliostress in five parallel
> instances and got one a possible torn page in one of the logs...that
> should indicate a problem in the disk-subsystem...right?
>
>
> "Mark Broadbent" <no-spam-please_mark.broadbent@.virgin.net> wrote in
> message news:#kMJelDqDHA.644@.TK2MSFTNGP11.phx.gbl...
> > Hi John, your assumptions are the same as the ones I would have
> > probably jumped to. Lets assume that the DB is inconsistent (perhaps
> > down to that faulty drive) ....
> > You say you are running the DBCC checkdb command, however have you
> > tried actually repairing the db using on of the repair parameters. I
> > would probably start off with the REPAIR_FAST option (if it is a
> > production db), but you might have to bite the bullet and use
> > REPAIR_ALLOW_DATA_LOSS might be an idea to do it with WITH
> > ALL_ERRORMSGS
> >
> >
> > --
> >
> > Br,
> > Mark Broadbent
> > mcdba , mcse+i
> > =============
Yes I certainly think you are looking in the right place. I would
expect it to be either the disks or controller -the former you would
expect to fail in array eventually if there was a problem.
I once had a problem with a server (non sql) where every now and again
a disk would fail OR the server would crash. Every time we would chkdsk
/f it and get the thing going. All hardware looked fine (compaq insight
didnt report problems). We software monitored it for yonks -fine...
again a crash would happen. Failed Disks were replaced left/right and
centre ....then eventually we replaced the external disk array and
the raid controller, and to be honest I cant remember which one
resolved the problem, -but the problem WAS resolved. Your best bet is
to swap out the controller first and then take it from there.
Good Luck with troubleshooting!
--
Br,
Mark Broadbent
mcdba , mcse+i
=============
Wednesday, March 7, 2012
Error 400 Bad Request in Reporting Services
Hi,
I get this strange error when I try to acess my SQL Reporting Services application.
I'm using SQL 2005 Beta 2. The installation was OK and the server is working fine. That is the only problem.
I checked the logs and a traced the database, but couldn't find someful usefull (at leat for me).
Here's the SQL2005 Report Server WebApp log:
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing MaxScheduleWait to default value of '1' second(s) because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing DatabaseQueryTimeout to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing InstanceName to default value of '' because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing ProcessRecycleOptions to default value of '0' because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing RunningRequestsScavengerCycle to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing RunningRequestsDbCycle to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing RunningRequestsAge to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing CleanupCycleMinutes to default value of '10' minute(s) because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing WatsonFlags to default value of '1064' because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing WatsonDumpOnExceptions to default value of 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException' because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to default value of 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing SecureConnectionLevel to default value of '1' because it was not specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
w3wp!library!1!25/08/2005-12:57:13:: i INFO: Initializing WebServiceUseFileShareStorage to default value of 'False' because it was not specified in Configuration file.
w3wp!ui!1!25/8/2005-12:57:15:: e ERROR: The request failed with HTTP status 400: Bad Request.
w3wp!ui!1!25/8/2005-12:57:15:: e ERROR: HTTP status code --> 500
---Details---
System.Net.WebException: The request failed with HTTP status 400: Bad Request.
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Page.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
w3wp!ui!1!25/8/2005-12:57:20:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)
w3wp!ui!5!25/8/2005-12:57:44:: e ERROR: The request failed with HTTP status 400: Bad Request.
w3wp!ui!5!25/8/2005-12:57:44:: e ERROR: HTTP status code --> 500
Thanks in advance,
Anderson
I had some "weird" problems immediately after I installed the SQL2005 JUNE CTP when initially launching RS. I do not know for cetain what your problems relates to above - but for some strange reason with my problem which I getting similar issues to your post was that the Virtual Directories (Reports and ReportServer) within IIS were somehow messed up!
So I deleted the two virtual directories and recreated and ensured I was not using 'Enable Anonymous Access' and I specified Integrated Windows Authentication.
Restarted IIS and everything was ok after that.
What version of Visual Studio are you using -? I had similar problems with bad requests without registering RS after install to .Net as well.
Best Regards,
Joe|||
Hi, Joe
Thanks for your interest.
I was having some trouble with the RS db. I've followed the steps below and now everything's ok:
1. Unistall RS;
2. Ensure RS database is deleted;
3. Reinstall RS;
4. Use RS Configuration Tool to setup everything.
Actually, I'm using SQL2K5April CTP and VS2K5 Beta 2.
Best regards,
Anderson
|||Hello Anderson!these little things you have to go through to make things work sometimes!
Did you know the August SQL 2005 CTP is now available as well?
Best regards,
joe
Friday, February 24, 2012
Error 27502
MSDE, then installs a client applicaton. Have used this installer dozens of
times with no problem. Now I have received the following error after MSDE
installs, but during the install of the client program: "Error 27502. Could
not connect to SQL Server (local)\MYINSTANCE". Then the client installation
rolls back.
Related info: this computer previously had MSDE and the client running, but
they were uninstalled. Tried to do a complete removal/uninstall of all
components through registry, etc. It is not practical for me to change
anything in the installer package, and besides it works fine on new
installations. Has something changed due to a previous installation that
would cause this error?
Any help is most appreciated! --RS
hi Rob,
Rob S wrote:
> Here is my situation... have an installation package that first
> installs MSDE, then installs a client applicaton. Have used this
> installer dozens of times with no problem. Now I have received the
> following error after MSDE installs, but during the install of the
> client program: "Error 27502. Could not connect to SQL Server
> (local)\MYINSTANCE". Then the client installation rolls back.
> Related info: this computer previously had MSDE and the client
> running, but they were uninstalled. Tried to do a complete
> removal/uninstall of all components through registry, etc. It is not
> practical for me to change anything in the installer package, and
> besides it works fine on new installations. Has something changed
> due to a previous installation that would cause this error?
> Any help is most appreciated! --RS
if you get an exception like "setup failed to configure the server" or the
like, you can only "change" the instance name or properly clean up the file
system and the registry...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Could you please help me identify all of the locations in the system and
registry files that could be affecting the MSDE installation.
As mentioned, the exact same installation routine normally detects and
connects to the server, but in this case there must be something left over
from a previous installation that is affecting the ability to detect the
server. I suspect it has something to do with translating the "(local)"
reference to the default server installation. Where, or how, does windows
translate the (local) reference into the actual host name?
Thanks again, RS
"Andrea Montanari" wrote:
> hi Rob,
> Rob S wrote:
> if you get an exception like "setup failed to configure the server" or the
> like, you can only "change" the instance name or properly clean up the file
> system and the registry...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Rob,
Rob S wrote:
> Could you please help me identify all of the locations in the system
> and registry files that could be affecting the MSDE installation.
there're 2 kb article that can help...
http://support.microsoft.com/default...b;en-us;320873 and
http://support.microsoft.com/default...;EN-US;Q290991
the first one requires the Msizap.exe, part of the Windows Installer SDK to
remove Windows Installer related entries, while the second skip this sort of
cleanup... file system and SQL Server related registry entries to clean are
listed...
personally I used the second one (and still have an entry in the add/remove
applet for an orphaned MSDE installation entry)...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
Thanks for all of your help. I ran both cleanup tools. Still did not solve
problem. I would not give up! After many hours of trial and error I
determine the problem was with a corrupted MDAC component. Reinstall MDAC on
XP sp2? Yes there is a way to do that (very simple). Once I reinstalled
MDAC the client application connected and installed just fine. --RS
"Andrea Montanari" wrote:
> hi Rob,
> Rob S wrote:
> there're 2 kb article that can help...
> http://support.microsoft.com/default...b;en-us;320873 and
> http://support.microsoft.com/default...;EN-US;Q290991
> the first one requires the Msizap.exe, part of the Windows Installer SDK to
> remove Windows Installer related entries, while the second skip this sort of
> cleanup... file system and SQL Server related registry entries to clean are
> listed...
> personally I used the second one (and still have an entry in the add/remove
> applet for an orphaned MSDE installation entry)...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>