Hye, I have a problem with Orion NMS. Whenever I try to created availability report for next month there is an error came out from my browser. Kindly refer below.
Orion Website Error
An error has occurred with the Orion website.
Additional Information
System.Web.HttpException: Request timed out.
I try to add increase timeout at "Report Cache Timeout" from Orion Website setting. But whenever I click submit the valued not change, value remain same.
Appreciate if someone have any idea or solution for this kind of problem.
Related
The cash summary by branch report is customized report and we can run earlier and the issue is currently happened.
Faced that the issue that is the 500 Internal Server Error when we run the report.
But We have no this server error when run for each month period (Eg- From Date to(11/1/2022), To Date(11/16/2022)) and can't run by year(Eg- From Date(1/1/2018), To Date(11/16/20220). Why is this the case and how to solve it?
enter image description here
enter image description here
enter image description here
We have no this server error when run for each month period (Eg- From Date to(11/1/2022), To Date(11/16/2022)) and can't run by year(Eg- From Date(1/1/2018), To Date(11/16/20220).
Please help to check and let me know any concern
When building the new report, I would set a default values that work, and then be able to use the Preview function. It will execute the report using the default values only during preview.
You can then use that to troubleshoot - start with the base report that works with that range that crashes on the custom report, and then slowly add your changes. You would then find out what change causes the 500 internal server error.
If you have access to the server, you can try using failed request tracing to get additional information on the errors that are not being sent to the web client. Here is a link on how to troubleshoot failed requests: https://learn.microsoft.com/en-us/iis/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis?source=recommendations
When I excute my code many time I get
server error 500 in the console
and no data has charged when I check the error I get cache error and then I have to refresh the page to get data. I don't know why I get this exception!!!
can someone help me and tell me how can I avoid this exception in symfony :
class: "Symfony\Component\Debug\Exception\ContextErrorException"
message: "Warning: rename(C:\wamp\www\myproject\app\cache\dev/doctrine/orm/Proxies\__CG__DefaultAppBundleEntityService.php.568513d40be3a3.02053948,C:\wamp\www\myproject\app\cache\dev/doctrine/orm/Proxies\__CG__DefaultAppBundleEntityService.php): "
Help!
unfortunatly I can't resolve this problem can someone help me please ????!!!
Sometimes all queries run without problem or errors but if I refresh the page it may that I get this error for one or more requests
Please check the user and owner of the file. assign them the same user and owner which are running php apache on your system. This worked for me.
From my application, the user clicks a button that launches a new window that contains the Report Viewer control and from there the user chooses the parameters from dynamically generated dropdown lists. When they click the View Report button it will occasionally throw the following error:
"The report execution {random ID code that changed with each error} has expired or cannot be found. (rsExecutionNotFound)"
After doing some Google research, I've tried:
Trimming all white space from the report path.
Extending the session time out on the server.
Making sure the time zones were the same on both the SSRS server and the SQL server.
Remove the session variable that equals "Microsoft.Reporting.WebForms.ReportHierarchy".
None of these solutions have fixed the problem. I have not been able to figure out what causes the error to show up. It seems to get thrown at random times.
Has anyone run into this error and figured out what causes it/how to fix it?
Thanks
You should look into the log file on the reporting server to obtain more detailed info. The log file is created in [PROGRAM_FILES]\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\LogFiles. If you can isolate the conditions and reproduce the problem then you can more than likely find more info on what is causing the issue. I would bet this is an issue when a report is requested and your application's session has not expired but the session between you app, the reportviewer, and ssrs has expired. You can increase that value.
I am currently trying to get search working in my Tridion 2011 installation. I read in another article that I should run the TcmReIndex.exe tool in the Tridion/bin folder to re-index all my sites. So I tried this and it failed with a message box giving the following details
Unable to get list of Publication items.
Unable to Intialize TDSE object.
The wait operation timed out
Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=21054; handshake=35;
The wait operation timed out
A database error occurred while executing Stored Procedure "EDA_TRUSTEES_GETTRUSTEEETOKEN"
I have four fairly large publications (100 000+ items in total) which I am trying to index.
Any ideas?
Whenever I get "Unable to Intialize TDSE object." errors, I typically write a small test script using VBScript, and try running it on the CMS server. Whilst this does not directly solve the problem, it often gives some insight into the issue by logging information in the event viewer. Try creating a test.vbs file as follows and running it:
Set tdse = CreateObject("TDS.TDSE")
tdse.initialize()
msgbox(tdse.User.Description)
Set tdse = Nothing
If it throws any errors, please let me know, and it may help us solve the problem. If it gives you a popup with your user description, then I am completely barking up the wrong tree.
I haven't come to anything conclusive but it seems like my issue may have been a temporary one as it just started working. I did increase all timeouts in Tridion MMC > Timeout Settings by 100 times their amounts but I suspect that this wasn't the issue, when it works the connection is almost instant.
If anyone else has this issue
Restart the computer the content manager is installed on, try again.
Wait an hour or two, try again.
Increase timeouts, try again.
I've run the process a few more times and it seems to be working correctly.
I don't have any errors with my smart target application, but I do see in the event log, the following error messages:
ERROR 2012-09-19 14:30:09
com.tridion.smarttarget.utils.AmbientDataHelper - can't find defined
trigger-types in claim store (check if your smarttarget cartridge is
up and running)
and:
ERROR 2012-09-19 14:30:11
com.tridion.smarttarget.tags.TimeoutQueryRunner - The fredhopper query
timed out java.util.concurrent.TimeoutException at
java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source) at
java.util.concurrent.FutureTask.get(Unknown Source) at
com.tridion.smarttarget.tags.TimeoutQueryRunner.executeQuery(TimeoutQueryRunner.java:64)
ERROR 2012-09-19 14:30:11
com.tridion.smarttarget.tags.TimeoutQueryRunner - The fredhopper query
timed out
I would really like to understand what is causing these and how I can remove them. Or some suggested steps to help me debug this would be great :)
As I say, everything is working perfectly, later on in the logs I see the query to ST is correct and the results being generated.
In the event that is helps, I'm running on a 2009 implementation with Smart Target 2010, java 1.5.
thanks
John
Sounds like you might have a trigger configured in ST that does not actually exist in the ADF (or is mismatched). Have you looked through your trigger-types.xml file for anything obvious? Have you disabled an ADF cartridge but not removed the corresponding trigger in the XML perhaps? See the documentation for Defining trigger types.
I think your timeout is coming from the SmartTarget region rather than FredHopper. Sometimes a query that isn't already cached in FredHopper can take a while to return, even though it's ultimately successful. The ST query tag has a timeout (defined in the smarttarget_conf.xml file, or over-ridden with a tag attribute) that it will wait for a response from Fredhopper for before resorting to using the fallback content. This might explain why you see later in the logs that the query is correct and that results are returned. See the documentation for <tcdl:query>.
No conclusive answer for you I'm afraid, but I hope that helps.
The first error is logged if your SmartTarget cartridge is not running -- or if the data that it puts into ADF is lost somehow (e.g. you have disabled sessions in your web server).
In that case, SmartTarget will still do a query but it won't include anything from the Ambient Data Framework in it. If you don't have any triggers based on ambient data, the end result is the same for you.
To get rid of the error, make sure that smarttarget_cartridge is configured correctly.
As for the timeout error, it simply means that the query sent to Fredhopper took longer than the configured time. In that case it will show the fallback content instead. If this is happening a lot, you might want to increase the timeout within smarttarget_conf.xml.
I hope you found the issue, but for future reference, the first error message is raised when the claim "taf:claim:ambientdata:definedtriggertypes" is not set by the SmartTarget cartridge. This can be caused by:
SmartTarget cartridge could not load the the trigger types from the SmartTarget server. The log will show an error "can't retrieve list of defined trigger types from FH".
The HTTP session on your web server is expired during an active visit (the HTTP session expired but the browser is still open) and the claim is "lost".
The server does not support sessions like Peter mentioned.