Liveware Publishing Support Forum

Hi,____I just migrate a web app. from w2k to w2k3 and I am getting "Invalid report file type". I check and recheck all the setup steps and I can not resolve the problem.____IUSR_XXX and EVERYONE has FULL CONTROL permission to C:WINDOWSTEMP__FULL CONTROL to the C:APPDIRECTORY____Could you help me with this____regards____Jorge

Here is the troubleshooting checklist from the Help File.____· Make sure that there is only one copy of R?WRUN.EXE and R?RRPT32.DLL on your server and that the installed version of these files come from the RattleRR installation. Having earlier versions of these files can cause a variety of unexpected conditions and can prevent successful DLL registration of the RattleRR components.__· Verify that the R?WATL.DLL files have been correctly installed and__registered. You can manually register these files by changing to the__directory where they reside and running:__REGSVR32 RRWATL.DLL__REGSVR32 RSWATL.DLL__for the Xbase and SQL versions respectively.____· Verify that the report can run via conventional runtime on the server.__· Verify that the ActiveX component can be successfully downloaded from the__server.__· If the problem occurs across all reports, start with a simple single file reports as the smallest test case.__· Setting a property to an invalid value can result in an _invalid report control object_ error.__· For SQL version, make sure that you are using a System data source and not a User data source.__· If a report is saved with the File->Print Print to file box checked the report may either not display in the browser or the browser may get the invalid report file type error show below.__Note that this error can be returned under other conditions as well so troubleshooting may take some careful investigation of the problematic report.

Hi,____I did every think but still does not work. ____I am using R&R v12 and the pdi file is generated calling dlls from an cgi xbase++ program.____In all cases in the new server the PDI file is generated ok, but the asp viewer show the error.____I took the PDI files generated in the new server and they can be viewed in the old server. So I believe the problem is the ASP viewer (I am using the same asp file in both servers) in w2k works fine in w2k3 dont.____I will appreciate all your help!!!!!!!!____Jorge____

Hi,____Just in case someelse have the same problem!!!!____What I discovered is that w2k3 by some reason blocks some file extensions for download (exe, pdi, etc.) that includes PDI extesion.____To solve the problem what I did was to generate a PDI file then rename it and change the extension to .txt and READY the report works again!!!!____Regards____Jorge

Thanks for the updated info. I would have never figured that out!____Kathleen__R&R Support