Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Micros Reports and procedures RES 5.0

Status
Not open for further replies.

POSINSAM

Technical User
Mar 3, 2013
268
US
After loading version 5 micros my reports & procedures always have to b messed around with before I can get them to work. (res 5.0 RC1 Win7 64)
1- Has anyone had issues getting IIS configured correctly for the web viewer to work in 5.0?
2- Does anyone have micros docs for this?

Im not sure what is different, but I cant seem to get this install to work. Any insight would be GREATLY APPRECIATED! ty
 
5.2 and 5.4 are a little more stable than 5.0 base, so you may want to consider upgrading if you can. I haven't had any issues, but Micros notes that a tweak may be needed if reports hang for 45-60 seconds before running. It's modifying a value in one of the web.config files, but I can't recall which off the top of my head.

Here is a copy of the 5.0 installation guide with IIS requirements: Res 5.0 Install RMF
 
Thank you for the reply. I have the install notes and followed the IIS setup tho the letter. It still hangs indefinitely. Do you happen to remember what the document was called, where Micros refers to the tweaks needed to the web.config?

Thanks again!
 
Here's the bit on the fix/tweak from the 5.0 RMF, not the install RMF:

"Occasionally, report requests from AutoSequence & Reports and Report Viewer
may be slow to display a report (i.e.- between 40 to 90 seconds). This does not
occur on all systems. If this problem is encountered, refer to Clarify Change
Request number 31114 for a solution. This solution will provide instructions on
how to load a configuration file, that works in conjunction with
'ReportExporter.exe', to address this report speed issue."

For an indefinite hang or blank screen when running autosequences, clearing the contents of the LocalDB folder in the micros\res\pos\etc folder on the PC and rebooting helps with that in our environment.
 
Thank you DJ! I will try that. I appreciate your time.
 
Do you possibly have the RMF handy? I can only seem to find the install RMF
 
Does anybody have the contents of that Clarify case for those of us who don't have access to the Micros website?

I really, truly, hate the reporter that Res 5 uses. I don't think I've ever had it work right off the bat and it's always a struggle to get it to work. At the moment I'm working on a very simple, fresh installation; one Windows user, no custom work, just basic Micros and a startup database. Loaded Windows 7 onto a newly formatted drive from a CD, followed the Res 5 installation instructions to the letter all the way up to v5.4, and still get "Navigation to the webpage was cancelled" on a simple, non-modified, menu item report. Does anybody have suggestions on getting the reporter to actually work?
 
Sadly I can't see this case :( The permission tiers are really screwed up in eSolutions, so more often than not when they tell you to look at a case you have to bounce it right back at them.
 
Thanks Moregelen. Any idea how to get past the "Navigation to the webpage was cancelled" error?
 
That Clarify case number above... I had a tech rattle off the fix to me once over the phone quickly during another autosequence issue. From memory : edit C:\micros\common\ReportViewer\web.config on the server itself. Find a value marked "timeout" and change it from 20 to 90 seconds. Save the file, restart the server.

On the "navigation cancelled" message, I have only seen that a handful of times; if the LocalDB clear and reboot and the Clarify fix don't get it, the only suggestion I have is to check the IIS logs on the server (c:\inetpub\logs\logfiles\w3svc1 on my test server). The first number after the closing parenthesis on each line is what you're looking for. A report I ran earlier in the lab today showed 304 for each response code.

Also - there is now a full base install version of 5.4 MR1 and the prerequisites out there now. It looks like a full recompile as opposed to a typical incremental patch release, as it kicks all the DLL and EXE versions up to the same major and minor numbers. Might be easier for future builds.



 
Thanks DJ. I tried the web.config fix and it didn't help. This is on the server, so there's no tempdb files to delete. I took a look at the IIS logs and there's nothing there. Just a couple of lines from when I browsed to to make sure that IIS is working. It's like the reporter isn't even attempting to connect.
 
I wouldn't be surprised. Browsing to that page gave me a generic error, so I set the CustomError mode to RemoteOnly to get a more helpful error message. It is a bit more verbose, but I'm not an IIS guy so don't really know where to start with it.

Server Error in '/ReportViewer' Application.

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.100.250:50705

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.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.100.250:50705

Source Error:

[highlight #EDD400]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.[/highlight]

Stack Trace:

[highlight #EDD400][SocketException (0x274c): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.100.250:50705]
System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) +239
System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP) +35
System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) +224

[WebException: Unable to connect to the remote server]
System.Net.HttpWebRequest.GetRequestStream(TransportContext& context) +1878753
System.Net.HttpWebRequest.GetRequestStream() +13
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) +103
ResReportViewer.RemotingServiceRoutines.RemotingServiceRoutinesService.BeginSession(String& strSession) +51
ResReportViewer.Login.GetServiceLogon() +147
ResReportViewer.Login.get_IsComplexSecurityEnabled() +36
ResReportViewer.Viewer.DoRedirect(Page page) +11
ResReportViewer.Viewer.CheckEmpSeq(Page page) +987
ResReportViewer._Default.Page_Load(Object sender, EventArgs e) +127
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +50
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
[/highlight]
Version Information: Microsoft .NET Framework Version:2.0.50727.5485; ASP.NET Version:2.0.50727.5483
 
This one might be a little over my head, without access to the machine... My lab system Default.aspx redirects to Login2.aspx within a second or two.

You say you're using a "startup" database - is that the shell database?
 
If I go to Login2.aspx it displays the page and a title bar, but that's about it. That kind of sounds like the default.aspx page has some kind of problem.

The startup database isn't a true shell, it's more the starting point for all the 3700's that are installed in my area. It has common classes of all kinds, sample menu items & employees and a full set of touchscreens programmed in already.
 
Ahhhh, gotcha. Our original system was boot-strapped off of a similar database. I've had problems with portions of Res functionality being disabled using the shell database until certain options are enabled (such as enhanced security), which is why I asked.

From the debug log you posted above and some tinkering on the lab system, it's now looking like a database connectivity issue to me. My lab system stopped redirecting Default.aspx to Login2.aspx as soon as it couldn't talk to the database anymore. Wish I had more suggestions...
 
Ok, so here it is. The server I was working on has two NICs. Micros, in their infinite wisdom, has the Report Viewer/IIS set up in such a way that if the primary NIC has no network connection, you can't run reports. That NIC on my test server had an IP conflict, (one of our admins connected an uplink to our domain switch), didn't have a network connection and therefore couldn't run any reports. This is what caused that complete mess of an error message I posted above.
 
pmegan it ends up that we had very similar problems. I only had one one network card loaded on the server and 5.0 did not seem to like that. As soon as I installed the second network card, BAM! Report city. Thanks a lot for your help with this. I appreciate it. Have a great day!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top