Test Run deployment issue: 'Oracle.ManagedDataAccessDTC' - oracle

I just configured the code on my machine. (VS2013 Premium) and I am not able to run any of the test case because of one following error :
"Warning: Test Run deployment issue: The assembly or module
'Oracle.ManagedDataAccessDTC' directly or indirectly referenced by the
test container
'e:\cs\qa_automation\all_team_current_automation\international\lda_automation\bin\debug\lda_automation.dll' was not found."
It is an Oracle version issue or what ? Can anybody guide me?

Mentioned dll is part of Oracle Data Access Components (ODAC). You need to install Oracle client software called 32-bit Oracle Data Access Components (ODAC)
with Oracle Developer Tools for Visual Studio
This should add Oracle support components for Visual Studio and solve your issue.

Related

How to configure SSRS report to access Oracle database on SQL Server machine where Report Server is installed?

I am sure that someone was successful to deployed SSRS report on the server where
SSRS is configured to access Oracle database.
I developed report on my machine where I have Visual Studio 2017,
ODTwithODAC122011 64-bit; 32-bit ODT withODAC122011. I connect to Oracle database and can run report.
After i deployed this report on Windows Server 2016. i got an error "An error has occurred during report processing. (rsProcessingAborted)
An attempt has been made to use a data extension 'ORACLE' that is either not registered for this report server or is not supported in this edition of Reporting Services. (rsDataExtensionNotFound".
I tried to complete the same ODAC install as on my machine.
1)Installed ODTwithODAC122011 64-bit - configured TNS name.
but with step
2) i tried to install 32-bit ODT - I received error that i need to install Visual studio to proceed with installation.
Do i really need VS on the server? What is the possible solution you can share?
thank you --Angelika--
with only the Oracla.DataAccess library should be enough, on the root of the service. Be aware the versions be the same as indicated in the project references

Importing Azure SQL database into Visual Studio 2013

I am setting up VS 2013 for development with Azure SQL Database (I am new to Azure). I have set up a database on Azure and a Solution on VS 2013. The local machine is Windows 8.1 Pro, with SQL server 2014 Express. I am trying to import the database on Azure into the VS solution. I have changed the Target platform on VS to “Microsoft Azure SQL Database”. I have checked that VS can see the Azure database by using “Test Connection” – all appears well.
When I start the Import Database, I get the following error:
You cannot import a 1025 database because you project’s target platform is set to 130. To learn more about changing your target platform and/or source database, or the supported database editions for specific target platforms, please refer to Import Schema help page.
I cannot find the help referred to in the error message. I have tried changing the target to SQL server 2014, no joy. Can anyone give me some pointers?
This issue could be SSDT version issue. Can you download and install the latest RTM or Preview version of SSDT from https://msdn.microsoft.com/en-us/library/mt204009.aspx
If you need to try out all GA and Preview features of Azure SQL DB, SSDT Preview would cover it. Otherwise SSDT RTM version will provide the stability.
For this:
Created the SQL project
Set target to Azure SQL
Instead of "Import" did "Synchronize"
The numbers refer to they type of sql installation, with 130 being 2014, and 1025 being the azure cloud. Exporting data from azure is a little more complicated than you would expect with a VM, because of the way SQL Azure works behind the scenes. First to literally answer your question here is the link to how to use the import export services so you can get the DB on your local 2014 install. However I imagine what you want to do is actually develop for that server without some painful import export process, which is why I think this link that talks about what tools to use might be more helpful.
Anyway, good luck, SQL azure is very much a product in it's infancy.
I was able to work around the problem by working from VS 2013 and creating the Db in VS and publishing to Azure following the tutorial:
https://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-get-started/
I hope I will not need to import a Db in the future!
Thank you to all those that edited & answered. I hope to be able to return the favour.
Importing from Azure into a Sql Server Project works in Visual Studio 2015 with no issues.

Connecting to db2 from Visual Studio 2010

I know that while connecting .net to oracle, you can attach dll's and run the program, can we do the same with db2? if so, then what are the dlls and where can i find them? i've tried connecting ibm.data.db2.dll (downloaded from net) but vs is giving a error saying it may not be valid build for vs.
any idea?
You need to install at least the IBM Data Server Runtime client appropriate for your DB2 version and, optionally, Visual Studio plug-ins from http://www-01.ibm.com/support/docview.wss?uid=swg27016878

Oracle.DataAccess.dll not in Visual Studio 2008 ".NET" reference list

I've got two Windows XP machines with both Visual Studio 2008 and Oracle Client 10.0.2.0.1 installed. One is a development machine and the other one a dedicated build machine. The machines were probably not set up the same way.
On my development machine, I've included Oracle.DataAccess.dll (version 10.2.0.1.100, not the asp.net v 2.x one) in a C# project. Note that the System.Data.OracleClient dll is insufficient (I don't properly remember why, I think it had something to do with bulk insertion/selection).
I was able to select that DLL from the Project->Add Reference dialog in the .NET tab.
Now on the build machine, I cannot build the project as it cannot find the .dll. The .dll is located in the same folder as on the development machine, (<installdir>\10.2.0\client_1\bin\Oracle.DataAccess.dll) in the same version.
The .dll is however not displayed in the .NET tab.
I tried (re)installing ODAC with ODP.Net for VS 2008 but it didn't change anything. When looking at the registry, I realized that my Development machine had a registry folder
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\AssemblyFolders\ODP.Net]
which points to the bin directory of my oracle installation. This entry does not exist on the build machine. Unfortunately, manually adding the key did not make Visual Studio find it (I've tried rebooting).
My main question is:
What do I have to do so the Build Machine automatically finds the Oracle.DataAccess.dll? (Note: manually adding the .dll each time the solution is changed would work, but that is not an option).
You can maybe help me out already by answering one of the following subquestions:
Which installer sets that registry entry?
Do I maybe have to reinstall the whole Oracle Client in a different configuration? (e.g. ADMIN)
Do I need more than just the Oracle Client, ODAC and .NET installed?
I managed to resolve the issue by completely uninstalling the Oracle Client on the build machine, then doing a fresh installation using the Administrator configuration rather than the Developer configuration.
Note that installing the Administrator configuration on top of the existing oracle installation did not work.

SSIS packages failing to load in VS 2008

I have a problem when trying to load an SSIS package in VS 2008. In the about it says it has "SQL Server Integration Services" installed but on loading a package I get a message that says:
Microsoft Vistual Studio is unable to load this document:
To design
Integration Services packages in Business Intelligence Development
Studio, Integration Services has to be installed by one of these
editions of SQL Server 2008: Standard, Enterprise, Developer or
Evaluation. To install Integration Services, run SQL Server Setup and
select Integration Services.
I thought maybe it was a version problem so I thought I'd look at a new Intergation Services project to play spot the difference. However when I told visual studio to create a new IS project (which was in the list quite happily) it created it and then gave me the above error message again.
To give some idea about my environment I have several version of Visual Studio (2k5, 2k8, 2k10) and several version of SQL server (2k5, 2k8) so I don't know if there is some confusion between versions...
The other thing that I am wondering is if there is a problem with what order things got installed in (ie my VS2008 wasn't installed when SSIS stuff was installed).
I am hoping there is a simple approach to this that won't mean reinstalling things. I can go to our IT to ask them to try to get it working but that would take some time. If it does come to that though I'd like to have some idea of what I should ask them to install since it does seem to be all installed currently...
So if anybody can either a) help me work out precisely what components are installed and what is missing that would be great. Bonus points for helping fix it without needing the install media...
Edit: A thought occurs to me. Coudl it be that I only have 2005 Integration Services installed? If so how can I determine that? And I still am not sure why VS is behaving as it is and letting me create a project but no SSIS in it, even if they were older versions...
Edit: Also it seems that if I load up VS 2005 I can create IS projects but of course can't load up the newer SSIS packages, I assume because they are from a newer version maybe...
Edit: Version information for SSIS in VS 2008:
Microsoft SQL Server Integration Services Designer
Version 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
The following line can tell you the version of the package:
<DTS:Property DTS:Name="PackageFormatVersion">3</DTS:Property>
3 is for 2008, 2 is 2005 and 6 is 2012.
By the way, how patched is your system? The 10.0.1600.22 does sound like the original installation of 2008. Try to install SP3 and the latest cumulative update - this will bring your installation to 10.00.5788 and the issue might go away.
If you previously had the components from a Express 2008 installation, and then you install an Standard, Enterprise, Developer or Evaluation, instead of actually installing a new instance/components (probably you see Integration Services grayed out) use the Upgrade option of the SQL Server 2008 setup, and then VS will load perfectly the DTSX file.

Resources