Oracle SQL Developer 4.2 windows authentication for SQL Server - oracle-sqldeveloper

I have SQL developer 4.2 and jtds-1.3.1. I am unable to connect to MS SQL Server
through Windows Authentication.
I have placed the "ntlmauth.dll" and "JtdsXA.dll" in jdk/jre/bin. it's not
working.
Placing file under jdk/bin is not working.
Placing file under Windows/System32 is not working.
I restarted the machine every time, while trying above 3 options.

Related

ORA-12154: TNS: could not resolve the connect identifier specified (but Net Manager tests fine!)

I am running Lyris ListManager on a Win 2008 server. It connects to Oracle 12c on another machine.
I have successfully configured and tested the connection using the Net Manger (or Net Configuration Assistant). However, when I run ListManger, I receive this Oracle error (TNS: could not resolve the connect identifier specified).
I checked the configuration file for the ListManager (lmcfg.txt), which correctly specifies everything.
Previously, we had Oracle 11g database, and 11g client on this server, which worked fine. DB upgrade to 12c was successful (other applications, on other servers, work fine), and I removed 11g client and installed 12c. It successfully connects to the Oracle server with the correct service ID, but Lyris ListManger application can't connect.
What am I missing here?
The root of the problem was in multiple client installations. At some point during the troubleshooting, I installed, and then uninstalled 64-bit client. After that, I installed 32-bit client and got it to connect through the Net Manager. However, that 64-bit client wasn't correctly and completely removed, and the ODBC driver was still looking at its original path for DLL libraries (which weren't there anymore).
I had to add a new ODBC driver entry for the 32-bit Oracle client. Once this was properly configured, the ListManager application was able to connect to Oracle server.

Windows authentication or SQL authentication not working after PC upgrading windows 8 to 8.1?

I have upgraded my pc Windows 8.0 to Windows 8.1, I am using Microsoft SQL Server R2, and this was working fine with my windows authentication/ SQL authentication when I am using Windows 8.0, but after upgrading my PC windows 8.0 to 8.1 the SQL server was not able to connect using windows authentication or SQL authentication. This problem occurring in only with my credentials, but It is able connect when use other credentials to connect to other database.
Please help me some one regarding this problem.!
I have figured out a work around for this issue.
First create a local account that will work with your sql server. Then switch to your Windows Live account (a seperate user) and modify the shortcut's target.
C:\Windows\System32\runas.exe /user:domainName\localAccountName /savecred “pathToExecutable”
This should work for any program that needs to use Windows Authentication.

Sql Server 2008 R2 Web setup throws application error when starting FixSqlRegistryKey_x86.exe

I have Windows 7 64bit. I had Sql Server 2008 R2 Express installed. I unistalled it and then I tried to install Sql Server 2008 R2 Web. Unfortunatelly on the Setup Support Rules page for 'Consistency validation for SQL Server registry keys' I got 'Failed'. I spent half of a day trying to solve it, but then I assumed that there must be realy something wrong with registry keys and it will be faster just to reinstall Windows.
After formatting the disk and reinstalling Windows 7, rebooting dozen of times I installed all Windows upadtes as well. I also did install some programs like Skype, Thundirbird etc. which has no influence on Sql Server setup.
And then I tried again to install Sql Server 2008 R2 Web. And again an error. A bit different one. Now when the setup is on the Setup Support Rules page I get an error message box with the title "FixSqlRegistryKey_x86 - Application Error" and content: The application was unable to start correctly (0xc000007b). Click OK to close the application. 'Consistency validation for SQL Server registry keys' gets 'Failed' status as well.
My team mate has exactly the same machine as mine. He had no problem with installation (he didnt even need to reinstall Windows).
I run the setup as administrator, from a local folder. I even tried to use the setup files copied from my team mate, for a case if my copy is corrupted. In the setup options I have chosen the 'x64' version.
Any ideas what can be the reason of the problem?
Problem solved.
Someone suggested to me that Web edition should not be installed on Win 7 (just on Windows Server). So perhaps installing a different version would work. My team mate perhaps succeeded acidentially - due to having sql server installed already in express edition... but it is just a guess.
Before I tried to install another edition of SqlServer, I downloaded 2008 Express version and I started the install. From the temporary folder created by the express edition I copied FixSqlRegistryKey_x86.exe file and I had overwritten the problematic file in the Web setup with this file.
I started the setup again. It passed the verification this time. But has crashed on a later point - setup unpacks the installation files to C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2 and runs from it. So I needed to again overwrite the problematic file in this location. Now the installation succeeded.

allround automations pl/sql developer on windows 7 - TNS over IP connect to remote db

I am really having very hard time making PL/SQL developer PL/SQL Developer work on my windows 7 64-bit OS. I have Oracle 10g standard edition installed already. I tried with PL/SQL developer version 7 and 8 with no luck. Do anyone tried doing it?. Main objective is to just establish a TCP over IP connection to a remote Oracle 10g database from PL/SQL developer. The PL/SQL developer website states it supports windows 7 though but it's making me crazy.
I finally got PL/SQL Developer working on my Windows 7 OS. Here goes the step by step instructions on how I did it.
First installed Oracle 10g 32-bit client runtime environment which is sufficient enough for opening a TCP over IP connection to a remote Oracle 10g database from PL/SQL Developer. It is also possible to connect using Oracle InstantClient (which is more light only 300 Kb) InstantClient_PL/SQL.
Than installed PL/SQL Developer version 8.0.4 (latest as of now) and copied over tnsnames.ora file into C:\oracle\product\10.2.0\client_1\NETWORK\ADMIN.
Now I can open a vpn connection for a remote database and connect directly to the remote db from PL/SQL developer using a TNS over IP connection.
The only caveat here is to open PL/SQL Developer as an administrator. This is where I went wrong and PL/SQL developer crapped out with a blank window.

DB2 Transport Component is not registered correctly

I'm trying to test the DB2 adapter for BizTalk 2006 (not R2).
While trying to configure an instance in an application, I get an error stating:
DB2 Transport Component is not registered correctly
The enivronment is 2 BizTalk servers sharing a messagebox.
The DB2 adapter works fine on the first server. It is the second server I am having problems with.
I've exported the .msi files from the first server, then installed them onto the second server and imported them into BizTalk. All of the other adapters that I'm using work fine on both servers.
Google searches don't bring up a whole lot regarding troubleshooting the BizTalk DB2 adapter.
Further troubleshooting has shown that MS BizTalk Adapters for Host Systems is installed on both machines. However, it was only configured on the machine that is giving me the issue.
I've unconfigured it, but that still has not helped.
I've double checked tht version numbers of the .dll's for the DB2 adapter are the same on both servers, and made sure that they are installed in the GAC.
None of this has helped.
Has anyone run into an issue like this before, or point me in the direction of where to look for BizTalk DB2 adapter troubleshooting guidence?
When the "registered" word appears, I think about the registration of COM components, not the installation of .NET assemblies. The underlying driver the DB2 adapter uses is the Microsoft ODBC Driver for DB2. You may want to check if your ODBC DSN control panel shows up that particular driver for you to configure a DSN.
I'd recommend a reinstallation for the Adapter pack for Host Systems.