question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

format exception causing scripthost to continually restart

See original GitHub issue

Hi,

A bunch of my jobs are causing the following error to occur, which is sending the scripthost into a cycle of constantly restarting:

[07/08/2016 19:26:28 > cfb1f8: ERR ] Unhandled Exception: System.FormatException: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters. 
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at System.Convert.FromBase64_Decode(Char* startInputPtr, Int32 inputLength, Byte* startDestPtr, Int32 destLength)
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at System.Convert.FromBase64CharPtr(Char* inputPtr, Int32 inputLength)
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at System.Convert.FromBase64String(String s)
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at Microsoft.WindowsAzure.Storage.Queue.CloudQueueMessage.get_AsString()
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at Microsoft.Azure.WebJobs.Host.Queues.StorageQueueMessageExtensions.TryGetAsString(IStorageQueueMessage message)
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at Microsoft.Azure.WebJobs.Host.Queues.QueueCausalityManager.GetOwner(IStorageQueueMessage msg)
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at Microsoft.Azure.WebJobs.Host.Queues.Listeners.QueueTriggerExecutor.<ExecuteAsync>d__1.MoveNext()
[07/08/2016 19:26:28 > cfb1f8: ERR ] --- End of stack trace from previous location where exception was thrown ---
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at Microsoft.Azure.WebJobs.Host.Queues.Listeners.QueueListener.<ProcessMessageAsync>d__11.MoveNext()
[07/08/2016 19:26:28 > cfb1f8: ERR ] --- End of stack trace from previous location where exception was thrown ---
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at Microsoft.Azure.WebJobs.Host.Timers.BackgroundExceptionDispatcher.<>c__DisplayClass1.<Throw>b__0()
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
[07/08/2016 19:26:28 > cfb1f8: ERR ]    at System.Threading.ThreadHelper.ThreadStart()
[07/08/2016 19:26:28 > cfb1f8: SYS ERR ] Job failed due to exit code -532462766

Unfortunately, I haven’t been able to narrow it down to a specific job and the error isn’t super helpful. Any idea what might be triggering this?

Thanks, James

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:6 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
jamesdixoncommented, Jul 11, 2016

@mathewc in case you’re interested, here was the response to the issue I posted:

@jamesdixon , refer to the breaking change log, originally the SDK only support a flag which indicates if the queue message should be encoded/decoded (base64 encoding). But we found that’s not enough and not extensible. So we decided to introduce the encoding/decoding interface and provided some built-in encoders. For why we change the default encoding behavior from base64 encoding to XML encoding, it’s because XML encoding will have smaller payload size for most scenarios. Please let me know if this makes sense.

1reaction
jamesdixoncommented, Jul 9, 2016

Closing since this appears to be a Azure Node SDK issue

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to correct the error of Windows Script Host
Here is a solution to it. Boot in safe mode tapping F8. Run registry Editor by ctrl+r and typing regedit; Now go to...
Read more >
Solved – Windows Script Host Error On Windows 10
The Windows Script Host error could occur for several reasons on Windows 10, but you can find handy fix methods in this article....
Read more >
6 Ways to Fix Windows Script Host Errors
3. Fix Corrupted System Files With SFC and DISM. If Windows Script Host errors are caused by corrupted system files, then the SFC...
Read more >
Windows Script Host Error on Startup
Windows Script Host error at startup: Hi guys and gals, Please kindly assist with the following error message: "Can not find script file...
Read more >
How to Fix Windows Script Host Errors on Windows 10 ...
Once you tap Y, restart your computer to complete the check, then check for the error. 3. Run a Full Malware Scan. One...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found