Error starting Azure SSIS integration runtime. Unexpected character encountered while parsing value: C. Path

Question

Error starting Azure SSIS integration runtime. Unexpected character encountered while parsing value: C. Path

David B SQL 1

I am getting an error when my SSIS Integration Runtime tries to start up. I have triggers everyday that start the IR run a few packages, and then stops itself. This has been working fine for months. Last night I started getting errors when it tried to start. I have tried to manually start 10+ times today and I keep getting the same error. We have not published any new packages recently and we have not changed any configurations. I contacted support on twitter and they recommended I post here.

This is the error message I am seeing below. I have removed my specific resource information.

Operation on target startMyIR failed:
{"code":"ErrorMessageNotFound","message":"Error message not found.
Parameters: [{"Code":"ExpressCustomSetupFailure","NodeNumber":1,
"Message":"{"dateTime":"06/02/2021 07:20:58",
"setupType":null,"componentName":null,"version":null,"errorCode":-1,
"errorMessage":"Unexpected character encountered while parsing value: C. Path '', line 0, position 0."}rn"}]
[activityId : a7fa9997-a7d1-4d72-b61e-69ca33a96690]",
"target":"{hidden}","details":null}

HimanshuSinha-msft 19,486 Reputation points Microsoft Employee Moderator

2021-06-09T18:31:08.94+00:00

Hello @David B SQL ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet .In case if you have any resolution please do share that same with the community as it can be helpful to others . Otherwise, will respond back with the more details and we will try to help .
Thanks
Himanshu
David B SQL 1 Reputation point

2021-06-09T19:45:16.63+00:00

Hello. Thanks for the response and research. I dont know how to relate that quite yet with what I am seeing. The error I was getting came when I was simply trying to start up my SSIS Integration Runtime in Azure Data Factory. I started an Azure Support ticket to see if support was able to see any logs on the backend that could point to what was happening. Curiously enough, the service started working again on Monday morning without any changes on my end, so I feel quite certain it has something to do with the PaaS infrastructure, but I still do not know what is happening. It happened one more time this week, but has not happened in my most recent attempts to start the runtime. If I am able to fine out more info from the support ticket, I will pass along!
David B SQL 1 Reputation point

2021-06-09T21:14:05.587+00:00

I received a call from Microsoft and they said it was definitely an issue on their end, and that it has been resolved now, although I do not quite yet have details as to what the ACTUAL problem was.

1 answer

Your answer

HimanshuSinha-msft 19,486 Reputation points Microsoft Employee Moderator

2021-06-09T18:31:08.94+00:00

Hello @David B SQL ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet .In case if you have any resolution please do share that same with the community as it can be helpful to others . Otherwise, will respond back with the more details and we will try to help .
Thanks
Himanshu
David B SQL 1 Reputation point

2021-06-09T19:45:16.63+00:00

Hello. Thanks for the response and research. I dont know how to relate that quite yet with what I am seeing. The error I was getting came when I was simply trying to start up my SSIS Integration Runtime in Azure Data Factory. I started an Azure Support ticket to see if support was able to see any logs on the backend that could point to what was happening. Curiously enough, the service started working again on Monday morning without any changes on my end, so I feel quite certain it has something to do with the PaaS infrastructure, but I still do not know what is happening. It happened one more time this week, but has not happened in my most recent attempts to start the runtime. If I am able to fine out more info from the support ticket, I will pass along!
David B SQL 1 Reputation point

2021-06-09T21:14:05.587+00:00

I received a call from Microsoft and they said it was definitely an issue on their end, and that it has been resolved now, although I do not quite yet have details as to what the ACTUAL problem was.

Answer 1

Hi @David B SQL ,

This error message is not common so that I did some online research.

The issue seems more related with C#.

You may have a refer to see if it is helpful.

https://stackoverflow.com/questions/23259173/unexpected-character-encountered-while-parsing-value

Regards，

Zoe

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hot issues October

Share via

Error starting Azure SSIS integration runtime. Unexpected character encountered while parsing value: C. Path

1 answer

Your answer