Check Active Files And Executables Failed
Siri
This is a classic case where the patching failed as there were few executables/files from the HOME still active. Same you can verify in the standard logging directory cfgtoollogs for opatchauto for the patch failed.
opatchauto is a really powerful tool which even let you resume your patch even when the patching crashed in between by any reasons like server crash, reboot cases or even manual CTRL+C etc. The other two regular options are rollback and version.
The error message indicates that some files or executables within your Oracle Home directory are currently in use. Specifically, the file ORAEVRUS19.dll is active.
Found in the log c:\opt\oracle\cfgtoollogs\opatch\opatch_.log
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.
If you are facing user sign-in issues with Pass-through Authentication, don't disable the feature or uninstall Pass-through Authentication Agents without having a cloud-only Global Administrator account or a Hybrid Identity Administrator account to fall back on. Learn about adding a cloud-only Global Administrator account. Doing this step is critical and ensures that you don't get locked out of your tenant.
Ensure that the Pass-through Authentication feature is still Enabled on your tenant and the status of Authentication Agents shows Active, and not Inactive. You can check status by going to the Microsoft Entra Connect blade on the Microsoft Entra admin center.
If you get the same username/password error, this means that the Pass-through Authentication agent is working correctly and the issue may be that the on-premises UPN is non-routable. To learn more, see Configuring Alternate Login ID.
Navigate to Microsoft Entra ID -> Sign-ins on the [Microsoft Entra admin center]( ) and click a specific user's sign-in activity. Look for the SIGN-IN ERROR CODE field. Map the value of that field to a failure reason and resolution using the following table:
Pass-through Authentication Agents authenticate Microsoft Entra users by validating their usernames and passwords against Active Directory by calling the Win32 LogonUser API. As a result, if you have set the "Logon To" setting in Active Directory to limit workstation logon access, you will have to add servers hosting Pass-through Authentication Agents to the list of "Logon To" servers as well. Failing to do this will block your users from signing into Microsoft Entra ID.
Ensure that you use a cloud-only Global Administrator account or a Hybrid Identity Administrator account for all Microsoft Entra Connect or standalone Authentication Agent installation and registration operations. There is a known issue with MFA-enabled Global Administrator accounts; turn off MFA temporarily (only to complete the operations) as a workaround.
If you have Pass-through Authentication enabled on your tenant and you try to uninstall Microsoft Entra Connect, it shows you the following warning message: "Users will not be able to sign-in to Microsoft Entra ID unless you have other Pass-through Authentication agents installed on other servers."
You need to have at least one active Authentication Agent to enable Pass-through Authentication on your tenant. You can install an Authentication Agent by either installing Microsoft Entra Connect or a standalone Authentication Agent.
Ensure that you use a cloud-only Global Administrator account when enabling the feature. There is a known issue with multi-factor authentication (MFA)-enabled Global Administrator accounts; turn off MFA temporarily (only to complete the operation) as a workaround.
For errors related to the Authentication Agent, open up the Event Viewer application on the server and check under Application and Service Logs\Microsoft\AzureAdConnect\AuthenticationAgent\Admin.
For detailed analytics, enable the "Session" log (right-click inside the Event Viewer application to find this option). Don't run the Authentication Agent with this log enabled during normal operations; use only for troubleshooting. The log contents are only visible after the log is disabled again.
To troubleshoot user sign-in failures, look for trace logs at %ProgramData%\Microsoft\Azure AD Connect Authentication Agent\Trace\. These logs include reasons why a specific user sign-in failed using the Pass-through Authentication feature. These errors are also mapped to the sign-in failure reasons shown in the preceding sign-in failure reasons table. Following is an example log entry:
You can get descriptive details of the error ('1328' in the preceding example) by opening up the command prompt and running the following command (Note: Replace '1328' with the actual error number that you see in your logs):
If audit logging is enabled, additional information can be found in the security logs of your Pass-through Authentication server. A simple way to query sign-in requests is to filter security logs using the following query:
Pass-through Authentication provides high availability using multiple Authentication Agents, and not load balancing. Depending on your configuration, not all your Authentication Agents receive roughly equal number of requests. It is possible that a specific Authentication Agent receives no traffic at all.
We are trying to install SAS 9.4, 64-bit, on a Windows 10 (Enterprise 18363) machine. When the setup.exe is launched (a help desk worker with admin rights has to remote in to run the install for the user) the initial install splash screen appears, disappears, and then does nothing. We have waited more than 10 minutes, checked in task manager to see is any SAS processes are running, and there is nothing active. This has happened repeatedly, after rebooting the machine, and after re-downloading the install files. We are at a complete loss as to what to do now.
That is very recent so will be supported. Are you installing from a local hard drive SAS depot? We've had a few problems installing from a remote share, so usually install from a local drive. As already mentioned, your best bet would be a Tech Support track. They can diagnose your SAS install logs.
We are downloading the compressed install files from a university website to the machine's hard drive, unzipping the install files, then calling Help Desk so a technician can remote-in with admin privileges (it is a government owned machine) to run the install. It is a cumbersome process.
I know this is old but I think I found the fix for many of us. The fix is to do it right. Setup.exe is not what you should be running. What you want to run is SASEnterpriseGuide83_x86_x64 which can be found under ...\SAS Software Depot\standalone_installs\SAS_Enterprise_Guide_Independent_Installer\8_3.
This took me most of today to figure out. I was just doing it wrong and I suspect many of us are. All the "fixes" out there did nothing because you can't fix it when there's nothing wrong. Hope this helps someone!
@jasonjacobs - This post is about installing Foundation / Base SAS which can only be installed using the SAS Deployment Wizard (setup.exe). You are referring to the standalone installation of SAS Enterprise Guide and that indeed is the best way to install that product if that is all you need to install.
I understand that (now) but for those of us that are not super familiar with SAS, I would be willing to bet many are just doing the wrong thing. In my case, I don't use SAS, I really don't know what it even does. I'm just an IT guy that has to install it maybe once a year. This year I documented the process which I should have done before. If you read the comments following the solution, there are still a bunch of people saying the solution didn't work for them. I bet they are in my shoes and just don't know what they are even looking at.
If you're truly trying to install Foundation / Base SAS, then my comment may not be for you. If you're not sure what the difference between X and Y are, perhaps this info will help. That's all I wanted to share but thank you for clarifying the difference since that is still something I was unclear on.
Follow the suggestions in this topic to resolve common issues with Tableau Server. For additional troubleshooting steps based on process status viewed on the Status page, see Troubleshoot Server Processes.
Restart Tableau Server. Issues related to processes not fully started can be resolved by restarting Tableau Server in a controlled way. To restart Tableau Server, use the tsm restart command. This will stop all the processes associated with Tableau Server and then restart them.
Reindex Tableau Server. Issues related to indexing can be resolved by reindexing Tableau Server. To reindex Tableau Server, use the tsm maintenance reindex-search command. For more information, see Reindexing Tableau Server Search & Browse below.
When you install Tableau Server for the first time, you will be prompted for the location you want to install to. If you do not see this prompt, you may have leftover files or directories from a previous installation, even if you uninstalled Tableau. To completely remove all traces of Tableau version 2018.2 or later, run the tableau-server-obliterate.cmd script, then restart the computer and try the install again. If the previous installation was a version earlier than 2018.2, manually delete all Tableau related folders before rerunning the install program.
When you install Tableau Server the Setup program may prompt you to restart Windows at the end of the installation. In certain cases, clicking Restart does not restart the computer. This can happen when a 3rd Party component installer is requesting a restart of Windows.
c80f0f1006