From: c-eric.geil on 5 Oct 2007 09:51 I'm getting the following error when attempting to deploy any report in RS (2000): An unexpected error occurred while compiling expressions. Native compiler return value: '128'. I've tried deploying reports that worked fine in the past, and have not changed since they were last deployed. I get this error for every report I try. I've also tried deploying from 3 different machines (including from the server itself) and get the same error. The reports work fine in "Preview". When I reboot the server, it works fine for a few deploys, then the error returns. Any idea what could be causing this? For that matter, any idea what return value 128 means? Thanks in advance. Eric
From: c-eric.geil on 5 Oct 2007 11:36 I'm not sure if it's related or not, but I'm having a different problem with RS as well. When I try to use Report Manager, I get an error message. It references a peculiar looking DLL name which actually changes each time I try to access Report Manager: Server Error in '/ReportManager' Application. -------------------------------------------------------------------------------- Could not find file "C:\WINDOWS\TEMP\nwo4n7np.dll". Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.IO.FileNotFoundException: Could not find file "C:\WINDOWS\TEMP\nwo4n7np.dll". Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [FileNotFoundException: Could not find file "C:\WINDOWS\TEMP \nwo4n7np.dll".] System.IO.__Error.WinIOError(Int32 errorCode, String str) +170 System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean useAsync, String msgPath, Boolean bFromProxy) +852 System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) +44 System.CodeDom.Compiler.CodeCompiler.FromFileBatch(CompilerParameters options, String[] fileNames) +882 System.CodeDom.Compiler.CodeCompiler.FromSourceBatch(CompilerParameters options, String[] sources) +433 System.CodeDom.Compiler.CodeCompiler.FromSource(CompilerParameters options, String source) +90 System.CodeDom.Compiler.CodeCompiler.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSource(CompilerParameters options, String source) +37 System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, CompilerParameters parameters, Evidence evidence) +479 System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, CompilerParameters parameters, Assembly assembly, Hashtable assemblies) +2143 System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence) +137 System.Xml.Serialization.XmlSerializer.FromMappings(XmlMapping[] mappings, Type type) +193 System.Web.Services.Protocols.SoapClientType..ctor(Type type) +309 System.Web.Services.Protocols.SoapHttpClientProtocol..ctor() +151 Microsoft.SqlServer.ReportingServices.ReportingService..ctor() Microsoft.SqlServer.ReportingServices.RSConnection..ctor(String reportServerLocation) Microsoft.ReportingServices.UI.RSWebServiceWrapper..ctor() Microsoft.ReportingServices.UI.Global.get_ReportServer() Microsoft.ReportingServices.UI.Global.SecureAllAPI() Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level) Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args) System.EventHandler.Invoke(Object sender, EventArgs e) +0 System.Web.UI.Control.OnInit(EventArgs e) +67 System.Web.UI.Control.InitRecursive(Control namingContainer) +241 System.Web.UI.Page.ProcessRequestMain() +197 Once again, a reboot clears this up for a short time, then it breaks again.
From: c-eric.geil on 5 Oct 2007 12:00 After further investigation, restarting the ReportServer and MSSQLSERVER services had no effect, but restarting IIS cleared up both problems temporarily. Once again, it stopped working after a few deploys.
|
Pages: 1 Prev: Large images causing LocalReport to throw an exception Next: Web Service render Timeout |