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.
Related
We've one IIS application server on which we have deployed ASP.NET application.
Now the issue is Server is hanging very frequently and every time we are recycling or restarting application pool. Could you please help me to fix it.
What I've tried:
1) Looked into IIS log and found that there are few requests throwing 500 error some time. All the time except few instances same requests are working fine and getting 200 status.
2) Few resources are taking longer time like
a) "Report.aspx" - State- SendResponse - Time Elapsed- 2-3 minutes
I checked the query and found that sp is returning data in 00:00:02.
b) "NewReport.aspx" - State- ExecuteRequestHandler- Time Elapsed- 1 minutes
I checked the query and found that sp is returning data too quickly.
3) Default recycle time is 29 hrs, and each application is using individual pool.
4) In code application connection has been opened and not closed at very few places.
5) We are using connection pooling, having 2 different connection string with Max Pool=500 and min Pool=50 each.
6) Most of the time there is no error in Event Viewer, some time have received TCP/IP error.
What I am looking for:
1) Do I need to make any changes in IIS to track down or please help if any changes required in IIS?
2) Is there any setting in SQL Server which can help me to find out or fix it?
3) Please help if anything else I've to do to fix this issue from your previous experiences.
I think you should capture a hang dump for W3WP.exe with Procdump or debug diagnostic tool first. We need to check all managed stack trace via WINDBG, sos.dll and mex extension. So that we can figure out worker thread is pending on which method and which module. Then might tell us about how to fix this hang issue. If you could find a way to always reproduce this problem. The problem would become much easier.
This link is about how to capture hang dump.
https://blogs.msdn.microsoft.com/asiatech/2014/01/09/debug-diagnostic-2-0-generate-a-manual-hang-dump-for-all-processes-owned-by-iis/
If you don't know how to analyze dump file manually, debug diagnostic analysis tool could help you achieve this.
I have the following code that is crashing:
Try
Logger.Warn("do_databind entered.")
Session("AgentId") = AgentId
Session("section") = Section
SectionId.Value = Section.ToString()
Session("dtresponses") = dtresponses
Session("dtlv") = dtlv
lvQuestions.DataSource = dtlv
Logger.Warn("just before databind.")
lvQuestions.DataBind()
Logger.Warn("databind successful. ")
Catch ex As Exception
Logger.Error(ex)
If Not IsNothing(ex.InnerException) Then
Logger.Error(ex.InnerException)
End If
End Try
The coding reaches the "just before databind" message, and then the application aborts. The "databind successful" message is never reached.
The catch loop is never reached because the error message in it is not recorded.
This has been working for months, and just quit working today. I would think it is a server problem.
The listview size at the point of the databind command is only 8 records, and I know the page it generates takes less than 10k total with a number of other blocks it generates.
In the old days, we would say this is probably a heap-stack collision, but I am not sure that terminology applies as well to managed memory in VB.Net. The code that traps the error is probably being overwritten. Other than that, I have no clue as to why it would stop working on our servers overnight.
Has anyone encountered this particular problem before?
UPDATE: The server indicates that it is a stack overflow error in w3wp.exe with error code 0xc00000fd (i.e., stack overflow)
I don't use the databinding or databound events for anything, but it would be an additional diagnostic to see where the memory crash may be occurring.
This app is in testing, so I have extensive error-trapping and comment logging at this point to make sure that the functions are working correctly.
The error does not leave a trace in the program. It is being caught by the server. This makes sense if the error is caused by a stack overflow. It is overwriting the catch code.
UPDATE:
Found the problem.
The program depends on a database, and a change was made to the database that resulted in a recursive procedure that called itself with the same information.
It ran until all the system memory on the server was consumed, and then aborted with a stack overflow error.
I put in diagnostic messages until I finally found it.
The trick here is it was on the staging server, and the database on the development server was not identical, so it worked on the development server the correct way but bombed on the staging server because the database contents were different.
I thought my coding had accounted for the condition that led to the error, but it had not.
Now I know to look for recursive problems if I get an abort in an application that is loaded with try-catch loops and results in no error logging where error logging should exist.
I am facing this error since some time, it is very intermittent in nature so, unable to understand why this error and what needs t be done t fix this.
Issue:
We have a workflow 4.5 WCF service. Everything goes well, but intermittently we see suddenly that a workflow instance gets suspended with an error in the table "DurableInstancing.InstancesTable"
The error is "Keyword Not supported: 'DB Name,1433';Initial Catalog'.
Since most times this ust workd fine without any error, I do not think this problem is related to web.config entry for connectionstring. Most times the workflow completes without any error. We have verified multiple times that the connection string is proper and there is no issue with parsing the connection string.
I suspect this issue is happening while Workflow instance is being recreated from persistence storage, and because some reason it is unable to recreate , the workflow is getting suspended with this error in DB.
I really appreciate any help in getting us through this error.
Thanks,
GD
What we found was it was an issue with permission in Database. We gave "dbo" user permission to the workflow database, and after that we have not seen this problem occur again. Has the error or exception that gets logged in the table is mre informative then it would have been better.
Thanks,
GD
I'm refactoring a very old reports generating function in an ORACLE web application. It used JavaScript to construct a URL, sending to the reports server to run a reports. What I want to do is processing it in the database, in PL/SQL procedures(invoked through mod_pl/SQL). I tried to use utl_http.begin_request to do that, but sometimes when the output file is large(PDF format, about 20 pages, 1.5M), I received an error:
ORA-29259: end-of-input reached.
The test codes for sending requests are quite simple:
--------upgraded 2013/08/27----------------------------------------------------------
UTL_HTTP.set_transfer_timeout(1000);
--some params setting....
myIdent := SRW.RUN_REPORT(myPlist); --here raise the exception(ORA-29273:request_failed; ORA-29259: end-of-input reached.) and procedure stoped.
r_stat := SRW.report_status(myIdent,myPlist);
#ThinkJet, Thanks for your help.
I logon the report server, found that the report still running after I got this exception in my program, and finally finished succefully.I tested for many times, and found everytime I got the exception just 5 minutes after I started request,no matter what kind of reports I was running and what size it was (sure, all big size,running for over 5mins).I'm wondering if it's something about configuration on oracle application server?
Does anyone have idea about this? Many Thanks.
ORA-29259 while SRW.RUN_REPORT
is ias 10g , this is cause by httpd.conf timeout parameter configuration
just
1.edit $ORACLE_HOME /Apache/Apache/conf/httpd.conf
change "Timeout" great than your report running time
2.restart http server and test it.
opmnctl restartproc ias-component=HTTP_Server
It take a time on Oracle Reports side to produce a big reports so a timeouts can occur sometime. Try to increase timeout with utl_http.set_ransfer_timeout procedure before originate a request and look if it helps.
We have a new beta version of our software with some changes, but not around our database layer.
We've just started getting Error 3128 reported in our server logs. It seems that once it happens, it happens for as long as the app is open. The part of the code where it is most apparent is where we log data every second via SQLite. We've generated 47k errors on our server this month alone.
3128 Disk I/O error occurred. Indicates that an operation could not be completed because of a disk I/O error. This can happen if the runtime is attempting to delete a temporary file and another program (such as a virus protection application) is holding a lock on the file. This can also happen if the runtime is attempting to write data to a file and the data can't be written.
I don't know what could be causing this error. Maybe an anti-virus program? Maybe our app is getting confused and writing data on top of each other? We're using async connections.
It's causing lots of issues and we're at a loss. It has happened in our older version, but maybe 100 times in a month rather than 47,000 times. Either way I'd like to make it happen "0" times.
Possible solution: Exception Message: Some kind of disk I/O error occurred
Summary: There is probably not a problem with the database but a problem creating (or deleting) the temporary file once the database is opened. AIR may have permissions to the database, but not to create or delete files in the directory.
One answer that has worked for me is to use the PRAGMA statement to set the journal_mode value to something other than DELETE. You do this by issuing a PRAGMA statement in the same way you would issue a query statement.
PRAGMA journal_mode = OFF
Unfortunately, if the application crashes in the middle of a transaction when the OFF journaling mode is set, then the database file will very likely go corrupt.1.
1 http://www.sqlite.org/pragma.html#pragma_journal_mode
The solution was to make sure database delete, update, insert only happened one at at time by wrapping a little wrapper. On top of that, we had to watch for error 3128 and retry. I think this is because we have a trigger running that could lock the database after we inserted data.