How to check obfuscation process status on Informatica, as I started the process about 8 hours ago and due to idle time was exceeded, my VM got logged off shutting all the applications.
You can still check the session logs from the integration server. They'll be in the installation directory / SessLogs
The Session Logs will be in readable format , only if you have selected - "Write backwards session logs" Option.
You can check session log in server in \server\infa_shared\SessLogs. Session logs will be saved in the server with time-stamp. To read the content of the log you can either open it through the workflow monitor, right-click on the session and select "Get session log".
Related
This is the error am getting in work flow log:
ERROR 7/15/2020 3:00:19 PM node01_DESKTOP-CK55616 7080 LM_36320 Session task instance [s_m_Importing_XML1]: Execution failed.
I cannot open the session log.. even session fails means also we can open the session log, but now I can't able to open the session log.
session log error:
An internal exception occurred with [LGS_10052]
help me out!!
There may be few causes.
Workflow failed to start the session at all - check workflow log.
Session log config is invalid - review and fix
Session log has been deleted from file system
Sharing workflow log details would shed some light.
You cannot open the session logs in case you have issue with the workflow configurations. Informatica will fail during the start of the workflow itself and there will not be any session logs, therefore it throes error when you try to open session logs. Open the workflow log, identify and fix the issue you are getting in the workflow.
I have a speech project which uses web service. I have set the timeout for 45 seconds in OD but when I deploy it, I get the following error for the first calling user in EP log viewer:
Fetch time out when opening timed stream for url =
http://example.com/AppName/SetLanguage?___DDSESSIONID=EF3397385F3E9BC0E89D526B3FCB811A%3A%2FAppName.
Timeout was = 15000
Session=ccmpp03-2018026140450-10
I think, EP has some default timeout of 15 sec.
1)Is there a way to increase it?
2)Is there any other solutions for this problem?
You should check this:
How to change the default Avaya Voice Browser (AVB) timeout value from an Avaya Voice Portal system?
you can change fetch time in AEP that is for all the application configured in AEP. if you want to change the fetch time for single speech application you need to add a property in the root then configured the fetch time for individual speech application.
enter image description here
enter image description here
I installed "Coveo Enterprise Search 7.0 " and "Coveo Search API " Locally on my PC "which use Window 7 OS" from link text
When I tried to start "RabbitMQ for Coveo" it always stop and log the below error in the Event views
RabbitMQ for Coveo: Erlang machine voluntarily stopped. The service is
not restarted as OnFail is set to ignore.
I tried to change the log in user for the service which is by default "Local System Account" to my domain user and the same error logged
I have stop and restart services(Sharepoint Administration & Sharepoint Timer Service)
I cleaned the Configuration Cache by using mentioned steps.
Summary of the steps to clear the timer job:
Stop SharePoint Timer service on all servers in the farm.
Browse to C:\ProgramData\Microsoft\SharePoint\Config{GUID} where the {GUID} folder contains a bunch of XML files and NOT the files with a “.PERSITEDFILE” extension.
Delete all the XML files
Update the contents of the Cache.ini file to just say “1” (without quotes).
Restart the SharePoint Timer service on each server
Reanalyze the issue in Health Analyzer
Does anyone know why this keeps occurring and how I can stop it?
First of all try and check your ULS Logs and see if there is any error that arise.
Secondly try and maybe check the event viewer on your SharePoint server to see if any errors are shown and make sure you have enough disk space available.
and also you might want to check this :Clearing Timer Services
Let me know if you see any error post it here.
hope it helps.
Yotam.
I try to validate the SASApp - Stored Process Server through SAS Management console. But the error is occured here:
[20.01.14 16:49] INFO: Starting extended validation for Stored Process server (level 1) - Making a connection
[20.01.14 16:49] SEVERE: Connection refused: connect
[20.01.14 16:49] SEVERE: The application could not log on to the server "server:8601". No server is available at that port on that machine.
I've checked in the properties the port for this server is 8601.
The official SAS Institute patch from http://support.sas.com/kb/46/844.html didn't solve the problem.
Has anybody had the same problem?
Four years late, but I ran into the same issue during a deployment workshop twice this week- both times it was because of a password mismatch with the service account responsible for accessing the servers. I re-updated the password in SAS Management Console and updated the password using deployment manager and then reattempted the validation and was successful. Hope this helps anyone else having the same issue!
More on updating passwords through Deployment Manager can be found here: https://communities.sas.com/t5/SAS-Communities-Library/Updating-Managed-Passwords/ta-p/361613