MSBI

When you install pymssql module using pip in python and then try to import pymssql, you may end up with “ PyMSSql - import _mssql - ImportError: DLL load failed: The specific module could not be found ” error, if you are using pymssql version 2.1 or greater. This is due to security reason, pymssql now is not linked with SSL and FreeTDS, unlike previous version where SSL and FreeTDS were jointly linked with pymssql during installation. This information can be found on pymssql site found http://pymssql.org/en/latest/freetds.html#windows In order to overcome, we need to install supporting components FreeTDS and OpenSSL independently and then pymssql will work without any issue. Below are the steps to download and configure FreeTDS and OpenSSL. FreeTDS can be downloaded https://github.com/ramiro/freetds/releases And extract the file which is download. Now place the extract folder where your python module is installed.  (Can be kept anywhere but to avoid accide...

The node /hbase is not in ZooKeeper. It should have been written by the master. Check the value configured in 'zookeeper.znode.parent'. There could be a mismatch with the one configured in the master. If you come across this error, while starting Hbase, then, check Hbase-Site.XML file (For me it was in /usr/lib/hbase-0.96.2-hadoop2/conf folder). Check if Znode is present else add this property to existing XML node. <configuration>         <property>                 <name>zookeeper.znode.parent</name>                 <value>/hbase-unsecure</value>         </property> </configuration> This is done for Stand-Alone mode. I am not sure how it is done for clusters.

Recently I had copied a excel file for analysis from SFTP site to development server from my account and asked my team mate to analyze it, by loading it into table. He logged in to the server and used a simple data flow task in SSIS with source as Excel to load the data. When he was connecting excel using excel connection manager, he had a weird error. Unexpected error from external database driver ()  He was unsure of why he was getting the error when selecting the sheet names. Then when reported, we quickly got into the possible reason of security. As I copied the file from SFTP to Development machine using my account, it had limited the access to other users. When he was trying to load, he was facing the error because it was a read-only file for him. Soon I granted full permission to him on excel security and it worked for him. There are various different solution on internet but initially none worked for us when we were trying to resolve. Hope this so...

SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Transaction (Process ID 68) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction." When you receive this error, Please verify if TABLE LOCK option is ticked in OLEDB Destination table. By Checking the TABLE LOCK option, this error will be resolved.

Recently, when one of my team mate created a package in the system dedicated to him and later, deployed it into Server. When we tried to run the package from Server, we got this error. All these days, we never had a problem but suddenly we had this issue as Server was recently updated. "Error 2  System.UnauthorizedAccessException:  Access to the path '*:\*******\******\****** .dtsx' is denied.      at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.SetAttributes(String path, FileAttributes fileAttributes) at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.BuildIncremental(IOutputWindow outputWindow)  0 0 " I did a quick research and found out error is due to security limit given to User accessing the server. Solution: Right Click on the Package and Go to Properties. In Properties, Go to Security Tab and Check if the user is given Full Permission....

[OLE DB Source] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "\foo\c$\bar" failed with error code 0xC0209303. There may be error messages posted before this with more information on why the AcquireConnection method call failed. If you face this error, then, go to project properties and select Debugging option from Configuration Properties and set Run64Bit mode to “False”.  

If you get “ SSIS: OleDB Data source: cannot retrieve the column code page info from the OLE DB provider “ error, then follow these steps to resolve. Go to the SSIS project properties page Ø   Then Click Debugging under configuration properties Ø   Select “Run64BitRuntime” property to false Ø   Save the project Ø   RUN Build againThen check the package runs to a successful completion.

Hi All, When you are using Varchar (MAX) in declaring a Variable, Always remember, that VARCHAR(MAX) can hold only 8000 characters. When we try to print Variables, PRINT Command display only 4000 character max. When we try to execute, Variable (MAX) which is more than 8000 Character, we may not get exact Error to solve. The problems seems to be with SET Statement which accepts only 4000 Characters. In Order to Execute a Variable which is having VARCHAR (MAX) and the length of the strings are more than 8000 Character, Then best way to work is Splitting the Queries with Multiple Variable. Example, If you have Dynamic Query which is 10000 characters, and is used as a string in a variable, Then, we need to Split the Queries. Find a Logical Break Point and Then concatenate remaining variables. DECLARE @Query VARCHAR ( MAX )       DECLARE @Query1 VARCHAR ( MAX )       DECLARE @Query2 VARCHAR ( MAX )   ...

Error: SSIS Error Code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: The Excel Connection Manager is not supported in the 64-bit version of SSIS, as no OLE DB provider is available. To solve this error, go to Project >> Properties >> select Debugging option and select FALSE in Run64BitRunTime .

This error message is due to the server setting of Remote Connection Query Timeout. The default is 600 seconds, or 10 minutes. We can change the Default value from 600 to any value as we wish, either by using SQL Server Management Studio GUI or by querying system Stored Procedure. By Query: EXEC   sp_configure   'show advanced options' ,  1 ; GO RECONFIGURE ; GO EXEC   sp_configure   'Remote Query Timeout' ,  1200 ; GO RECONFIGURE ; By SSMS GUI: We can Achieve this by using SSMS GUI. Follow these steps in SQL Server 2012. Step 1) On Server, Right Click and Go for properties. Step 2) Click in Connections as Shown here and C hange the  Remote Query Timeout value as required.

OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "(null)" returned message "The Microsoft Access database engine cannot open or write to the file ''. It is already opened exclusively by another user, or you need permission to view and write its data.". Msg 7303, Level 16, State 1, Line 1 Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "(null)". If you get this error while Loading Data From Excel to SQL Server, then, close the Excel sheet opened and try to run queries again.

To overcome this issue, There are two methods, One is by using SQL Server Management Studio GUI interface and Other is by running Stored Procedures to enable program. Method 1 Run Following Stored Procedures: EXEC   sp_configure   'show advanced options' ,  1 ; GO RECONFIGURE ; GO EXEC   sp_configure   'Ad Hoc Distributed Queries' ,  1 ; GO RECONFIGURE ; Explanation: Here  sp_configure   displays or changes global configuration settings for the current server.   By setting  Show Advanced options  to 1, we  can list the advanced options by using  sp_configure . The default is 0. By Enabling  Show Advanced options , we can Enable  Ad Hoc Distributed Queries  options. Ad Hoc Distributed Queries:   By default, SQL Server does not allow ad hoc distributed queries using OPENROWSET and OPENDATASOURCE. When this option is set to 1, SQL Server allows ad hoc access. ...

[OLE DB Destination [730]] Error: There was an error with input column "Email" (689) on input "OLE DB Destination Input" (362). The column status returned was: "The value violated the integrity constraints for the column.". We have created table initially with EMAIL Column as "NOT NULL". While loading Data from Flat File to SQL Server Table, We got this above mentioned error. We looked into few data from Source where we found we had Some "NULL" Values and this is reason we got this Error. We fixed it by changing EMAIL Column at Destination Table like to allow "Null" Values and then populated the records and it worked like charm!!!