none
Suddenly, U-SQL scripts that previously worked now fail with Internal error

    Question

  • ...and every table I've created today has disappeared. I had been experimenting with simple CREATE TABLE statements or CREATE TABLE...AS. The last operation that seemed to complete successfully was CREATE VIEW...AS EXTRACT. The internal error message is pasted below. Any thoughts on how to troubleshoot this vague error?

    ERRORID:  E_CSC_SYSTEM_INTERNAL

    SEVERITY:  Error

    SOURCE:  SYSTEM

    MESSAGE:  
    Internal error! The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.

    DETAILS:  N/A

    DESCRIPTION:  N/A

    RESOLUTION:  N/A

    INTERNALDIAGNOSTICS:  
    ScopeCompiler.CompilationException: E_CSC_SYSTEM_INTERNAL: Internal error! The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.
     ---> System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.

    Server stack trace: 
       at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Scope.MetadataService.Contract.IMetadataService.GetTableInfo(EntityName tableName, SecurityContext seContext)
       at Scope.MetadataService.Client.MetadataClient.GetEntityBase[T](EntityName name, Func`3 baseFunc)
       at Scope.MetadataService.Client.MetadataClient.GetTableInfo(DdlName tableName)
       at Scope.MetadataService.Client.WcfBasedMetadataClient.GetEntityExt[T](Func`2 baseGet, DdlName entityName)
       at ScopeCompiler.FrontEnd.Ddl.CatalogMetadataInfoProvider.GetEntityInfo(Type type, DdlName ddlName)
       at ScopeCompiler.FrontEnd.Ddl.CatalogMetadataInfoProvider.GetEntityInfo[T](DdlName name)
       at ScopeCompiler.FrontEnd.Ddl.RecordMetadataInfoProvider.GetEntityInfo[T](DdlName name)
       at ScopeCompiler.FrontEnd.Ddl.MetadataRegister.GetEntity[T](DdlName name)
       at ScopeCompiler.FrontEnd.Ddl.BaseDdlResolver.CheckExistenceForCreate[T](DdlName name, Token token, Boolean ifNotExists)
       at ScopeCompiler.FrontEnd.Ddl.DdlResolver.OnCreateTableStatement(TVoid input, CreateTableStatement e)
       at ScopeCompiler.VisitorContext`1.Visit(T node, Action accept)
       at ScopeCompiler.TreeVisitor`2.Visit(P input, IEnumerable`1 nodes)
       at ScopeCompiler.VisitorContext`1.Visit(T node, Action accept)
       at ScopeCompiler.FrontEnd.CompilePassHelper.Run(Action pass, Compiler compiler, CompilerTimer timer, Boolean throwOnErrors)
       at ScopeCompiler.FrontEnd.CompileStrategy.ExecuteCompilePass(Action pass, CompilerPhase phase, Boolean throwOnErrors)
       at ScopeCompiler.FrontEnd.SqlAstBuilder.BuildAst(Compiler compiler, FunctionCall parentCall, NameContext nameContext, SubroutineType subroutineType, Script parent, Boolean isCodeObjectUsed, DiagnosticCollection diagnostics)
       at ScopeCompiler.FrontEnd.SqlAstBuilder.BuildAst()
       at ScopeCompiler.FrontEnd.SqlCompileStrategy.<>c__DisplayClass1.<AstBuildingPass>b__0()
       at ScopeCompiler.FrontEnd.CompilePassHelper.Run(Action pass, Compiler compiler, CompilerTimer timer, Boolean throwOnErrors)
       at ScopeCompiler.FrontEnd.CompileStrategy.ExecuteCompilePass(Action pass, CompilerPhase phase, Boolean throwOnErrors)
       at ScopeCompiler.FrontEnd.SqlCompileStrategy.AstBuildingPass(Script mainScript, String scriptText)
       at ScopeCompiler.FrontEnd.FrontEndRunner.Execute()
       at ScopeCompiler.FrontEnd.CompilePipeline.DoExecutePipeline()
       at ScopeCompiler.FrontEnd.CompilePipeline.DoCompile()
       --- End of inner exception stack trace ---

    HELPLINK:  N/A

    FILEPATH:  N/A

    LINENUMBER:  -1

    STARTOFFSET:  -1

    ENDOFFSET:  -1


    Jason

    Wednesday, November 18, 2015 8:49 PM

Answers

  • Apologies for the inconvenience. We are actively investigating this issue now.

    Wednesday, November 18, 2015 10:15 PM
    Moderator
  • As a work around, please try to submit the job with a different priority level (1) and/or parallelism level (e.g., 5 instead of 1). Some of these changes seem to unblock submitting jobs.

    Michael Rys

    Wednesday, November 18, 2015 11:16 PM
    Moderator

All replies

  • Apologies for the inconvenience. We are actively investigating this issue now.

    Wednesday, November 18, 2015 10:15 PM
    Moderator
  • As a work around, please try to submit the job with a different priority level (1) and/or parallelism level (e.g., 5 instead of 1). Some of these changes seem to unblock submitting jobs.

    Michael Rys

    Wednesday, November 18, 2015 11:16 PM
    Moderator
  • Thank you. Seems to be working now.

    Jason

    Thursday, November 19, 2015 1:42 PM
  • Thank you. If I see this again I'll try these workarounds.

    Jason

    Thursday, November 19, 2015 1:42 PM
  • Following up on this, there were some intermittent issues with jobs last night and we've since mitigated and resolved that so you should not be seeing any additional issues.  If you are, please feel free to reach back out.

    Thanks,

    matt


    Program Manager -- hadoop -- http://blogs.msdn.com/mwinkle

    Thursday, November 19, 2015 4:58 PM