This was the mid-tier not liking the ODBC name on the report creator's machine (so the ODBC connection name in the report). Changing this to the same ODBC name used in the mid-tier fixes up this issue.
Anne Ramey *********************************** E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Ramey, Anne Sent: Friday, July 09, 2010 10:05 AM To: arslist@ARSLIST.ORG Subject: all custom reports error in midtier ** For my custom reports, with and without subreports, I get errors like Error Failed to open the connection. Failed to open the connection. C:\WINDOWS\TEMP\{E239F6DA-2BE3-40B1-9AAD-9F898E882E66}.rpt In the midtier. Of course the hex string is different each time. I checked and that file does exist on the report server. I googled, but couldn't find anything on this error anywhere. Even the midtier on the reporting server sees this message, even though it's local to that directory and would have full permissions. I'm sure it's something we did creating the reports, but I can't see what. We didn't save the data with the report and they work fine in the WUT. Can someone point me in the right direction? Anne Ramey *********************************** E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties only by an authorized State Official. _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
