DANGEROUS BUG WIN XP PRO/Oracle 9.2

  • Thread starter Thread starter Nick
  • Start date Start date
N

Nick

RE: Installation of Oracle 9.2 database on a Win XP Pro
PC that has Visual Studio.Net 2003 already installed

I am looking for the solution to a problem that I have
been facing for the past 30 days, and have not been able
to find any solution on the internet so far. So, I don't
know, if I have 'DISCOVERED' a new bug or what.

Anyways, here it goes:

I have a Win XP Pro PC and have installed Visual Studio
Enterprise Architect.NET 2003 on that. After that, I
tried to install Oracle 9.2 (the latest release of
Oracle) database, but without success. The TNSLSNR.EXE
has been giving me a hell of a problems, and the error
that I get from Microsoft (during installation of Oracle
9.2 and thereafter forever) is: "TNSLSNR.EXE has
encountered an error and needs to close. Report this
problem to Microsoft ...". When I try to connect to the
Oracle 9.2 database through SQL/PLUS, the error that I
get is: "ORA-12154: TNS:could not resolve service name".

Could someone please explain what is going on here?
Trusting my Win XP Pro installation to be impeccable
(because everything including .NET 2003 just works fine
even now, minus the Oracle part) I have installed-
uninstalled-reinstalled Oracle 9.2 probably 20 times in
the last 30 days, but continue to get these errors. Have
I 'DISCOVERED' that .NET and Oracle 9.2 database on Win
XP Pro are born incompatibles, or am I just one of the
suffering but not so vociferous many? Is there a cure?
What is it please ...

Please do oblige with your help if you could in any way.
I am already sick with this and am technically dying
because I can't cure this.

Thanks,
Nick.

BTW: I work with the Bay.NET forum in Silicon Valley CA
as a volunteer/marketing events producer, and no-one
there has been able to answer my request so far either.
That hurts.
 
-----Original Message-----
RE: Installation of Oracle 9.2 database on a Win XP Pro
PC that has Visual Studio.Net 2003 already installed

I am looking for the solution to a problem that I have
been facing for the past 30 days, and have not been able
to find any solution on the internet so far. So, I don't
know, if I have 'DISCOVERED' a new bug or what.

Anyways, here it goes:

I have a Win XP Pro PC and have installed Visual Studio
Enterprise Architect.NET 2003 on that. After that, I
tried to install Oracle 9.2 (the latest release of
Oracle) database, but without success. The TNSLSNR.EXE
has been giving me a hell of a problems, and the error
that I get from Microsoft (during installation of Oracle
9.2 and thereafter forever) is: "TNSLSNR.EXE has
encountered an error and needs to close. Report this
problem to Microsoft ...". When I try to connect to the
Oracle 9.2 database through SQL/PLUS, the error that I
get is: "ORA-12154: TNS:could not resolve service name".

Could someone please explain what is going on here?
Trusting my Win XP Pro installation to be impeccable
(because everything including .NET 2003 just works fine
even now, minus the Oracle part) I have installed-
uninstalled-reinstalled Oracle 9.2 probably 20 times in
the last 30 days, but continue to get these errors. Have
I 'DISCOVERED' that .NET and Oracle 9.2 database on Win
XP Pro are born incompatibles, or am I just one of the
suffering but not so vociferous many? Is there a cure?
What is it please ...

Please do oblige with your help if you could in any way.
I am already sick with this and am technically dying
because I can't cure this.

Thanks,
Nick.

BTW: I work with the Bay.NET forum in Silicon Valley CA
as a volunteer/marketing events producer, and no-one
there has been able to answer my request so far either.
That hurts.

.
Click to expand...
Google: TNSLSNR.EXE
I did a quick scan but unfortunately didn't see anyone who
was reporting a solution. However, knowing that you are
not alone is a bit of help - you now know that the problem
isn't specific to your computer(s).

Bill
 
Actually, the error is coming from Oracle. (The error reporting dialog
simply sends the error report to Microsoft, but this doesn't mean the error
is with Windows.) Check with Oracle to see if they have a fix for this.
 
Back
Top