Hi everyone,
Primary platform is Framework 2.0 and Sql25k 64-bit
When I try to save my DTSX package from my client to the production server I get this error:
"No Description found"
Either Windows or Sql authentication.
Does anyone have ever faced this drawback?
Thanks in advance,
Any idea?
Is something related to Visio 2003? http://support.microsoft.com/kb/922546
Thanks again,
I have a small .net application that uses RMO to synchronize a merge subscription. Everything works fine when I build with platform target = "Any CPU" on both x86 and x64 systems, but I get a "Class not registered" error on my x64 system when the application is built with platform target = "x86". Incase you are wondering I have to run this code under x86 because it is actually going to distributed in a dll and called from an x86 application.
x64 System:
Microsoft Windows Server 2003 R2
Enterprise x64 Edition
Service Pack 1
Here is my code:
{
ServerConnection dbconn = new ServerConnection(publication_server);
dbconn.LoginSecure = true;
dbconn.Connect();
MergeSubscription subscription = new MergeSubscription();
subscription.ConnectionContext = dbconn;
subscription.DatabaseName = publication_db;
subscription.PublicationName = publication_name;
subscription.SubscriberName = subscription_server;
subscription.SubscriptionDBName = subscription_db;
if (!subscription.LoadProperties() || subscription.SubscriberSecurity == null)
throw new Exception("Unable to initialize the Synchronization");
MergeSynchronizationAgent agent = subscription.SynchronizationAgent;
agent.Synchronize();
}
The MergeSynchronizationAgent class is platform specific (it is just a thin wrapper around a pile of native code), so you would need to make sure that you have the x86 version of SQL Server installed on your x64 server if you compile your exe as x86.
-Raymond
|||I would hate to install an x86 instance of SQL Server to solve this issue. Is there anything short of that I can do to get the appropriate files and registry keys on to an x64 system?
Thanks for your help.
|||Sorry to disappoint you, but there really isn't a supported way to allow you to just pick the dependencies for running the MergeSynchronizationAgent class although we have plans to come up with a merge module for replication components in the future. Realistically, it would be rather difficult to just pick out the dependencies for the MergeSynchronizationAgent class as it depends on things that folks normally don't suspect such as:
sqlncli.dll\rll
msvc80*.dll
The 2.0 .NET Framework
instapi.dll under 90\Share and corresponding registry key for locating it.
-Raymond
Hi all of you,
Primary platform is Framework 2.0 running over XP.
I've got an issue with a SSIS package which uses Oracle Provider for OleDB:
Test connection failed because of an error in initializing provider 'OraOLEDB.Oracle.1' is not registered on local machine
Nevertheless, MS Ole DB Provider for Oracle works fine. Let me know where am I failing.
Thanks in advance,
Try reinstalling the Oracle client.|||Thanks for your answer Phil.
I've got a question.. If I do such thing, my tnsnames.ora will be destroyed? 'suppose so
Anyway, I think that my problem is other one..
|||Copy your tnsnames.ora file to another name and then restore it when done. Which is something you should be doing anyway -- backing it up.You can try just reinstalling the OLE provider: http://www.oracle.com/technology/software/tech/windows/ole_db/index.html|||
Hi Phil,
Thanks indeed. It works fine. I'm sorry for my scepticism.
|||Hi Phil.
I am also having this problem, made sure that the ACL are read and execute for ASPNET, IUSR, IWAM users on the server. The app is .NET 2.0 by a vendor that is using the following connection string. names change to protect the innocent.
Provider=OraOLEDB.Oracle;Password=pass;User ID=user; Data Source=ds'/>
Unfortunately the vendor has no answers...
My question is that I have been told by my DBA that reinstalling doesn't always reinstall correctly as the registry entries still exists. Am I being told correctly? Also, If I reinstall, am I creating a new Oracle_Home that I would have set up in the OBDC administrator.
|||
n2magick wrote:
Hi Phil.
I am also having this problem, made sure that the ACL are read and execute for ASPNET, IUSR, IWAM users on the server. The app is .NET 2.0 by a vendor that is using the following connection string. names change to protect the innocent.
Provider=OraOLEDB.Oracle;Password=pass;User ID=user; Data Source=ds'/>
Unfortunately the vendor has no answers...
My question is that I have been told by my DBA that reinstalling doesn't always reinstall correctly as the registry entries still exists. Am I being told correctly? Also, If I reinstall, am I creating a new Oracle_Home that I would have set up in the OBDC administrator.
Right, but are you using SSIS? If not, I'm afraid I cannot help you... It seems that you have several layers that could be causing you issues.|||
Thanks Phil for answering my question. No I am not using SSIS. Just happen on the post doing a search trying to find the answer to my problem.
Thanks again for your prompt answer.
LuAnn
