I am deploying a SSAS Tabular project that uses a ODBC datasource.
This datasource is a DSN created for Hive (cloudera).
I am using SSDT for developing the datasource. I had to install ODBC Driver for 64 and 34 bits with the same name (here the explanation https://ayadshammout.com/2013/07/13/ssas-tabular-using-hiveodbc-connection/)
I am trying to deploy this proyect in a remote server, but I get this error:
"The modifications to the server could not be saved. Error returned: 'Error de OLE DB u ODBC.
Could not connect to the data source named 'Hive_DES'"
Is it necessary that the ODBCs be created on the server with the same name?
Thanks
I resolved the issue. It is necessary configurate an user with permissions to get data. The ODBC should be well configured.
Related
I am working on an ASP.NET project which accessing a remote SQL Server database. My objective is to set up this remote database on my local system.
I have tried 2 ways, but I'm facing problems both ways:
(1) Using SQL Server import and export wizard.
I get an error saying that the connection state is closed, but I am able to fetch all database tables of remote database:
(2) Schema and Data comparison from SQL Server object explorer inside of Visual Studio.
Here I get an error in that database user-related issues are showing. User or group not found:
I have tried other things in the last 4 days also but not found any clue to solve it. I am new to ASP.NET and SQL. Please help. Any helpful answer will always be appreciated. Thanks.
I have tried the Dennis1679's answer, but the following issues are coming.
One or more unsupported elements were found in the schema used as of
a data package. Error SQL71564:Error validating element[username]:
The element[username] has been orphaned from its login and cannot be
deployed.
Install SQL Server Management Studio, connect to the remote database, right-click on the database, choose export data-tier application. Then connect to your local instance and import data-tier application.
Connect to the remote database:
Right-click on the database choose export data-tier application:
Follow the wizard and save the .bacpac somewhere
Connect to your local SQL Server (localdb)\MSSQLLocalDB
Choose Import data-tier application
Select the previously saved .bacpac and import it. Now your local instance should have the same database
I've had a frustrating time attempting to connect to an Oracle DB as a destination via SSIS so I can export some data into it.
I have Oracle ODAC components installed, tnsnames.ora set up properly, TNSNAMES in the NAMES.DIRECTORY_PATH attribute in sqlnet.ora, Attunity installed on my computer etc. I have even managed to connect to the database in question in the SSIS server explorer, and am able to access all its tables etc.
However I can't seem to find out how to actually connect to that Oracle DB as a destination in an SSIS Project. I started a new package, switched to data flow, selected 'OLE DB Destination' and attempted to create a new connection with either 'Oracle Provider for OLE DB' or 'Microsoft OLE DB Provider for Oracle'. Both only let me cite the server name and user name + password, and when I enter the same ones I used to establish the SSIS server explorer connection I get an 'ORA-12154: TNS: could not resolve the connect identifier specified' error.
I have spent a lot of time trying to fix this but keep running into a brick wall. Any idea what I'm doing wrong or what I could do to establish a connection?
Are you using 32 or 64 bit Windows? I've struggled with some Oracle connections in the past and I made the mistake with mixing up 32 and 64 bit Oracle drivers and settings. Visual Studio is 32 bit and uses those drivers by default, you can go to project properties and change the VS to use 64 bit runtime if necessary.
This could be helpful also: https://stackoverflow.com/a/18098573/5605866
We are experiencing issues when executing an SSIS package from a SQL Server job. However, when we execute the package locally, it is successful. The package connects to an external SSAS cube using MDX. I have attached the error message below. The connection manager is OLE DB Provider for Analysis Services 11.0. We can successfully ping the external site where the cube is located from the server
with the job.
Unfortunately, at this point, it appears that the issue is related to the windows server core install. I found this link which outlines the issues related to core - http://technet.microsoft.com/en-us/library/ee441257(v=ws.10).aspx. We can get the job to execute from a Windows Server with a full version install, but not on the core install.
I need to create a linked server from SQL Server 2012 to a IBM DB2 (9.x) on AIX. It is a mandatory requirement to create the connection with SSL.
I was trying to use "Microsoft® OLEDB Provider for DB2 v4.0 for Microsoft® SQL Server® 2012" but I was not able to connect to DB2 by the Data Access Tool from MS OLEDB.
Later I installed the IBM DB2 client tools and GSKIT and with this I can connect to DB2 via SSL. With the installation also came the connection provider "IBM OLE DB Provider for DB2". The problem is that I can't create the linked server.
I always get the error message
Cannot create an instance of OLEDB Provider "IBMDADB2.DB2COPY1" for linked Sever "mydb2" (Microsoft SQL Server , Error 7302)
In some discussions was mentioned to use a specific provider string, but in this case the field of the provider string is greyed out.
I just have the options for Product name and Data Source. Is the Data Source == the DB Name of the Connection form the IBM BD2 Client tools? What should I use as Data Source?
Okay i could solve the problem and want to share the solution.
The mentioned provider IBMDADB2.DB2COPY1 comes from the installation of the IBM DB2 Client tools.
In Server Objects --> Linked Servers --> right click new server you can choose the provider. Using the "IBM OLE DB Provider for DB2 - DB2COPY1" which has access to the configured connection including the SSL Keys, the field Data Source is greyed out.
The key to successfully create a linked server to a DB2 is not the guy but the script. There you can use also provider string information even it is greyed out in the GUI.
EXEC master.dbo.sp_addlinkedserver #server = N'MyLinkedServer', #srvproduct=N'IBMDADB2',
#provider=N'IBMDADB2', #provstr= N'HOSTNAME=hosturl;Port=12345;
DATABASE=DBinDB2Client;UID=ItsMe;Pwd=secret;Security=SSL;', #datasrc=N'DBinDB2Client'
Et voila, as you can see the linked server will be created successfully and can acceess the DB2 Database. The issue is solved.
__
edit:
the linked server can only! used by it's creator. if other users want to access the server, they'll get this error:
Cannot create an instance of OLE DB provider "MSDADASQL" for linked server "MyDB2"
there is a tutorial how to give the permission to other users:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2011/09/28/troubleshooting-cannot-create-an-instance-of-ole-db-provider.aspx
after you walk through the tutorial, you also need to reboot.
I have a problem when I try to process a SSAS project in Visual studio 2013 (sql server 2012) using Pubs data sample of Microsoft. Could anyone tell me how to resolv it? Thanks in advance!
OLE DB error: OLE DB or ODBC error: A network-related or
instance-specific error has occurred while establishing a connection
to SQL Server. Server is not found or not accessible. Check if
instance name is correct and if SQL Server is configured to allow
remote connections. For more information see SQL Server Books Online.;
08001; Client unable to establish connection; 08001; Encryption not
supported on the client.; 08001.
Change the Provider in the connection manager to OLE DB.
If that doesn't work, try restarting the SSAS service.
This happened to me today. It took 3 hours of trying everything I could to fix it and I wanted to share it so maybe someone else can be saved those hours. My solution is particular to my problem whereby I'm using impersonation to log into the server with a specific username and password.
In my case I had an SSAS tabular model with a connection to a remote Azure server. I am using Git on Azure DevOps for my source control and I had just moved over to a new development machine on our local network so I updated the remote repo with the latest version of the model, connected to the new dev machine and cloned the repo there. Then I tried to resume my work, but I was getting the same error you were: "OLE DB error: OLE DB or ODBC error: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible..." blah.
Anyway, I tried resetting the SSAS services, changing the connection provider, rolling back to a previous commit that I knew worked, etc. Nothing worked.
The problem was my impersonation settings!!! I have SSAS_Data_Model credentials created for this project so when I cloned the repo, for some reason the impersonation must not have come through with the password.
So, in Visual Studio, go to Tabular Model Explorer, click on Model -> Data Sources, Edit Connection -> Impersonation... -> and under 'Specific Windows user name and password', you need to re-enter the password for your username. This finally got it working again and I can import tables into my model once more.
Try to test the connection when you provide appropriate server , database , provider. So you will be able to get the connection related problems there itself.
(data source designer -> connection string edit)