Unable to Execute Query - Access Database 2016

activities
studio
access
connection

#1

Hi There,
I am trying to execute an access query and when I configure the connection with connection wizard, it says that the connect is successful but while executing query, it gives me an exception. And in the output, it says " : ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"

I have already installed the Access Database Engine and tried both 32bit and 64bit but no help !

Below is the log :

"An error has occured

Source: Newtonsoft.Json

Message: Cannot create and populate list type System.Data.Odbc.OdbcErrorCollection. Path ‘$values’, line 1, position 175.

Exception Type: JsonSerializationException

Newtonsoft.Json.JsonSerializationException: Cannot create and populate list type System.Data.Odbc.OdbcErrorCollection. Path ‘$values’, line 1, position 175.
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateNewList(JsonReader reader, JsonArrayContract contract, Boolean& createdFromNonDefaultCreator)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateList(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, Object existingValue, String id)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.ReadMetadataProperties(JsonReader reader, Type& objectType, JsonContract& contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue, Object& newValue, String& id)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateISerializableItem(JToken token, Type type, JsonISerializableContract contract, JsonProperty member)
at Newtonsoft.Json.Serialization.JsonFormatterConverter.Convert(Object value, Type type)
at System.Runtime.Serialization.SerializationInfo.GetValue(String name, Type type)
at System.Data.Odbc.OdbcException…ctor(SerializationInfo si, StreamingContext sc)
at Void .ctor(System.Runtime.Serialization.SerializationInfo, System.Runtime.Serialization.StreamingContext)(Object[] )
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateISerializable(JsonReader reader, JsonISerializableContract contract, JsonProperty member, String id)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue(JsonProperty property, JsonConverter propertyConverter, JsonContainerContract containerContract, JsonProperty containerProperty, JsonReader reader, Object target)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
at UiPath.Shared.JsonParser.DeserializeObject[T](String jsonValue)
at UiPath.Models.UiPathDuplexProxy.<>c__DisplayClass21_0.b__0()
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()"


#2

Hello,

I’ve been there, can you double check the data base you are querying has the same columns?
you know like a double check of everything, also are you running on admin mode?

here it´s a workflow with the insert query and all the files. :slight_smile:

1_Insert_fuelUsageDT - Copy.zip (836.2 KB)


#3

Thanks for quick response @beesheep.

I am trying to fetch data from Access 2016 and when I configure connection, it says “Test Succeeded” but gives the above mentioned error while executing query.


#4

Hello

Do you have the MS access database ?

image

And also the file was empy hahahah now this is the correct one… Fuel Usage Report 26062017_173357.xlsx (1.8 MB)

change the file for this one and change the excel scope activity. :slight_smile:

image

Please reply with your results.


#5

Just doing a followup since this question its being asked over and over again. can you let me know if the answer given helped you in any way. many many thanks.


#6

@beesheep, I’m waiting to see if @AryanPrakash had any luck with that too :slight_smile:

I’m using OleDb instead of ODBC, maybe that would work?
See richard.denton’s post for a connection string.
It works fine for me with Access 2016. My first thought was like yours, I think, that it was a column name spelled wrong - that’s the same type of error I get when I name the column incorrectly in the query.

Regards,
burque505


#7

I am wondering if the type of installation of the oledb is not the one causing the problem.


#8

@beesheep, I’m not having any trouble with the connector, just having trouble remembering to type in my column names correctly from time to time :slight_smile:
My thought was that OleDB might work instead of ODBC for @AryanPrakash.
Regards,
burque505