Error connecting to Oracle via linked server after SP2 installatio

We have a test SQL Server box configured with the following:
Windows 2000, SP4
SQL Server: 8.00.944
Oracle Client Tools: 9.2.0.1
Microsoft ODBC for Oracle: 2.573.9030.00
We built a linked server to a 3rd party Oracle application. We used the
standard "Microsoft OLE DB Provider for Oracle" drvier from the drop down
list. We created views using this linked server and they worked fine.
However, after installing SP2 of Reporting Services, we now receive the
following error when we attempt to use the views:
[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB provider returned
error message: Oracle client and networking components not found. These
components are supplied by Oracle Corporation and are part of the Oracle
Version 7.3.3 or later client software installation.
Provider is unable to function until these components are installed.]
We use a free SQL Tool called "Toad" to access the Oracle environment. This
tool uses the same Oracle Client Tools referred to in the error message.
This tool continues to function normally.
We really want to take advantage of some of the new features in SP2, but we
can't deploy this on our production SQL Reporting box until we get this issue
resolved. Any help in this matter would be greatly appreciated. Thanks!
--
Grande ApplicationsHello,
Microsoft OLE DB Provider for Oracle and Microsoft ODBC Driver for Oracle
are not supported with any Oracle versions later than 8i. For more
information, click the following article number to view the article in the
Microsoft Knowledge Base:
244661 Limitations of Microsoft Oracle ODBC Driver and OLE DB Provider
http://support.microsoft.com/default.aspx?scid=KB;EN-US;244661
Therefore, the cause of the issue is not related to the reporting service.
If you want to use Oracle version 9i, you can use the following settings in
step 3 of this procedure in the article 280106:
280106 How to set up and troubleshoot a linked server to Oracle in SQL
Server
http://support.microsoft.com/?id=280106
However, this configuration is not supported and is discouraged.
Oracle Client Microsoft Windows 2000
9.x
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI]
"OracleXaLib"="oraclient9.dll"
"OracleSqlLib"="orasql9.dll"
"OracleOciLib"="oci.dll"
You can refer to the article 280106 to set up and troubleshoot a linked
server. I hope the information is helpful.
Sophie Guo
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 Sophie,
Thanks much for your response. We were able to resolve the problem by
restarting the SQL server (SQL Server service); however, we have discovered
from others that this resolution has been known to provide only a temporary
fix.
Do you know where I can find a list of all of the files (and file versions)
installed and updated by Reporting Services SP 2? This would be very helpful
to us.
Thank you.
Grande Applications
Thank you
"Sophie Guo [MSFT]" wrote:
> Hello,
> Microsoft OLE DB Provider for Oracle and Microsoft ODBC Driver for Oracle
> are not supported with any Oracle versions later than 8i. For more
> information, click the following article number to view the article in the
> Microsoft Knowledge Base:
> 244661 Limitations of Microsoft Oracle ODBC Driver and OLE DB Provider
> http://support.microsoft.com/default.aspx?scid=KB;EN-US;244661
> Therefore, the cause of the issue is not related to the reporting service.
> If you want to use Oracle version 9i, you can use the following settings in
> step 3 of this procedure in the article 280106:
> 280106 How to set up and troubleshoot a linked server to Oracle in SQL
> Server
> http://support.microsoft.com/?id=280106
> However, this configuration is not supported and is discouraged.
> Oracle Client Microsoft Windows 2000
> 9.x
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI]
> "OracleXaLib"="oraclient9.dll"
> "OracleSqlLib"="orasql9.dll"
> "OracleOciLib"="oci.dll"
>
> You can refer to the article 280106 to set up and troubleshoot a linked
> server. I hope the information is helpful.
> Sophie Guo
> 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.
>
>

Error connecting Database Server

Hi,

I am getting the following error when i am trying to connect to the database server installed on different box.

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"

When i searched google, some postings suggested to enable the TCP/IP and Named Pipes Protocols from SQL Server configuration Manager. I did so and also ran mofcomp command. But even after doing this i am not able to connect to the server. Following is my connection string.

<add key="conn2" value="Data Source=xxx\xxxxx;Initial Catalog=xxxxxx_xxxxxx;User ID=xx;Password=xxxxxx;"/>

Could any one please tell me what else the configuration settings i need to do in order to connect to the database from my application.

There are a couple of things to look at

1/. ensure your SQL Server 2005 instance allows remote connections

2/. make sure your firewall is not blocking any incoming connections

Error at statup

Hello all,
I'm getting an error when starting SQL2K SP3 running on
Windows 2K Server.
The error message is in a message box called "Queue
Manager" with an ! in a triangle and the following text:
Run-time error '-2147467259 (80004005)':
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
does not exist or access denied.
Has anyone else come across this error and what did you do
to correct it?
At this point the server will not start up, I get this
message when i'm trying to manually start the SQL Server
as it will not start up with the OS as it is supposed to
do.
Background: No changes have been made too the server
configuration. Database structure's have been changed.
I've looked through all the Microsoft KB's but other
problems with this error message dont seem to relate to
this particular scenario. I'm afraid I might have to
reinstall SQL2K. This could be a problem, might not get
all the data back. However, I do have the MDF and LDF.
Any help is appreciated.
Thanks
Isaiah* What account are you using to startup?
* Is SQL SErver set for mixed mode authentication?
* Have you tried running it as an application using the '-c' switch from
command prompt?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Error Adding SQL Server Login Properties

Hello,
I have SQL 200 SP3 box that has a web app with a hard coded user; I
tried to re-add the user after it was deleted.
I now get the following error when trying to add the database access:
"Error 21002 [SQL-DMO] user 'unsername' already exists."
Any help would be greatly appreciated.
I fixed my issue by running the following:
use my_db;
go
sp_change_users_login AUTO_FIX, 'my_user'
go
Hulicat wrote:
> Hello,
> I have SQL 200 SP3 box that has a web app with a hard coded user; I
> tried to re-add the user after it was deleted.
> I now get the following error when trying to add the database access:
> "Error 21002 [SQL-DMO] user 'unsername' already exists."
>
> Any help would be greatly appreciated.

Error Adding SQL Server Login Properties

Hello,
I have SQL 200 SP3 box that has a web app with a hard coded user; I
tried to re-add the user after it was deleted.
I now get the following error when trying to add the database access:
"Error 21002 [SQL-DMO] user 'unsername' already exists."
Any help would be greatly appreciated.I fixed my issue by running the following:
use my_db;
go
sp_change_users_login AUTO_FIX, 'my_user'
go
Hulicat wrote:
> Hello,
> I have SQL 200 SP3 box that has a web app with a hard coded user; I
> tried to re-add the user after it was deleted.
> I now get the following error when trying to add the database access:
> "Error 21002 [SQL-DMO] user 'unsername' already exists."
>
> Any help would be greatly appreciated.