I'm working on my buildfire app locally. Last night I closed my laptop without any errors. Today, I hit the refresh button and got this error:
Not sure what's wrong. My other apps that I haven't touched in a while are also not working / getting the same error screen. Also, the admin panels still work fine, just not the widget itself. No errors when I go to app.buildfire.com. I even tried pulling the latest sdk but still getting an error.
Nothing in the widget is responsive when I click on it except the "cancel" text. When I click the cancel text another error will appear in the console.
Doing another pull of the SDK fixed the issue.
I am working with LUIS NLP service provided through website www.luis.ai. I am not able to open this website for few days, it hangs right on the account login page with message - "Please wait a few moments... Initializing". Is there some issue in LUIS or I am missing something? I have attached the image where this site hangs.
Any help will be appreciable. Thanks.
We're also seeing this issue, quite a lot. There site is quite buggy on the front-end.
What has worked for us was to use IE, it seems to run a bit better there. Also, if it gets stuck on 'initializing' for like 3 or 4 seconds, a refresh usually does the trick
I am getting the error Could not load 'extlib.dijit.Mobile in IE 8. Using FF 17.0.7, I don't see such an error but the form does not display either.
I found this post
Getting error when using Extension library and dojo in xpages says at least 8.5.3 is needed. The server is running 8.5.3.
Edit: Opps wrong link corrected above
Any idea what is wrong?
I should be able to display a mobile app on my PC's browser correct?
Sorry but this is my first mobile app.
This is working locally on the browser but not on the server. Are we missing something on the server that should have been installed?
I am working on an application which has got light box on the Home page, I need to close the light box and navigate to the Home Page, I am closing the Light box with the script and navigating to the Home page.
I am trying to bring the application to front and maximize the window.
I am using commands "ie.bring_to_front" and "ie.maximize".
These commands work for an application which has not got light box on the Home page.
Is it due to the Light box which is present on the home or is it due to java script the page has got.
Please suggest
Thanks and Regards,
Ajazz.
It is not possible to assist you.
Without seeing the code that is actually running on that page, and with no indication of the failure mode beyond 'not working' (e.g. what actually happens, do you get an error message of any sort?) no description of the 'light box' application, not even a screenshot, it's nearly impossible to know what is causing the code to fail. ESPECIALLY since we know the code is not at fault since it works on other sites.
Please find a psychic who can read your mind and get the information needed to help you, since you seem to be incapable of providing it when requested
I have recently inherited a website written in Classic ASP, and am currently trying to get a sense of the state of things. The website is working in production, however the development environment (hosting on a Windows Server 2003 box) produces an HTTP 500 error when you try to navigate to it.
I realize that HTTP 500 errors just mean that an unexpected server error occurred, and that this also is more than likely the ASP code crashing for one reason or another. I have tried numerous browsers (IE, Firefox, and Chrome) but they all have the same amount of information.
Being primiarly an ASP.NET developer I am use to the yellow screen of death which can be configured to show a stack trace.
So my question is, how do I convince IIS and/or Classic ASP to give me a better hint about what is causing the error?
Update:
I should have gone into more detail originally, but here are some of the things I've looked at.
I've looked at the event logs
(Application, Security, System, etc)
and there is nothing relevent there.
I have looked at the IIS access logs
and I see the access attempts, and
just 500 errors. It is even
producing 500 errors on favicon.ico
If you can't find the offending line by turning off "Show friendly HTTP error messages" as Wayne suggested, then try adding "On Error Resume Next" to the code along with response.write statements. I've found with problems like these, you just have to start going line by line through the code until you find the offensive code.
Just out of curiosity, is Active Server Pages set to allowed in the Web Server extensions in IIS on the dev servers?
Have you checked the Application portion of the web server's Event Viewer for error entries?
What alex said, also make sure that you turn off "Show friendly HTTP error messages" in Internet Explorer and then browse to the site; that tends to give you a more specific error message (although still generic compared to ASP.NET's stack trace) along with the line number.
If you have a global.asa file in your web directory, you could rename the file and try loading the favicon.ico file again. If it loads, the problem lies within the global.asa
Clearly an old question, but for what it's worth, if you have access to the development server (direct or remote desktop), you can access the site from there. Localhost requests reveal more debugging information about classic ASP including line numbers.