Cannot connect to Oracle after Office patches

BizTalk Utilities

Xselerator XSLT IDE

Forum main page

Most active member

Search page

Information Online

View our event calendar
Add general event such as an upcoming software release or conference
View all birthdays

Public image gallery
Upload your images in your profile

Profile editing page
Subscription list page
Address book page

Member list page
View the most active member
User groups listing
Private message page

TopXML Discussion Forum

Forums Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

Cannot connect to Oracle after Office patches

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [BizTalk Utilities] >> BizTalk 2004/2006 Utilities and Adapters >> Cannot connect to Oracle after Office patches

Page: [1]

Message

<< Older Topic Newer Topic >>

Cannot connect to Oracle after Office patches - 21 May 2008

Magnus

Posts: 2
Score: 0
Joined: 21 May 2008
Status: offline

Last thursday (may 15, 2008) we installed the latest patches from Microsoft, security update for Publisher 2003 (KB950213), security update for Word 2003 (KB950241) and junk e-mail filter for Outlook 2003 (KB950380) on our servers. After that the adapter for Oracle stopped working with the error "An Exception occurred attempting to start an EndPoint. The Uri is 'database://Microsoft .NET Data Provider for Oracle/Adresser/Adresse'". We have several receive ports with different URI's. None is working. We have uninstalled the patches on the BizTalk-server and updated BizTalk Utilities from 3.0.1 to 4.0.7, but to no avail. Nothing else has been changed. The test reports "Connection successful" when you click the button "Test connection" in Visual Studio for the particular receive ports and the connection to Oracle works fine in SQL Plus since I can run the same SQL-commands there as the receive port tries to do.

I have read that the error should appear if you have an invalid URI, but the URI has not been changed. The system has been running fine for almost two years straight...until last thursday. Any help is appreciated.