Unable to open Chrome UI with Jenkins installed as Windows Service even on Windows Server 2019 even after doing necessary configurations
I have installed Jenkins as service on Windows Server 2019 . I did the following
Open properties window of the service -> Logon-> enable the checkbox "Allow service to interact with desktop"
Toggled the NoInteractiveServices registry key from 1 to 0 .
3)Restarted Server as well as Jenkins
Still i am not able to see the Chrome Launch from Jenkins (Its working fine as headless)
I know that we by launching from .war file we can see the browser open . But when i navigate to folder and launch the war file jenkins gets opened but all my configured jobs are not visible
Please provide workaround for any of above
I have an application that has an embedded Microsoft webbrowser ActiveX control. On the server where the application is installed - it runs fine (runs quickly, runs scripts) within the application. The application is exposed via RDP for users to run - the Microsoft webbrowser ActiveX control page does not work properly (hangs for a long time - finally displays script error message - scripts don't work) when it is run using an RDP session.
When directly accessed from any computer, the webpage that is contained in the ActiveX control runs fine.
The application.exe files are in these registry folders with the appropriate decimal value (11001):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION
I'm thinking that there is something more that I need to do to either force the version emulation or permit scripts.
Server is 2012R2 64-bit OS
Make sure client browsers are supporting ActiveX
Set sufficient permissions for clients Explained Here
Change Security Layer and User Authentication to a hexadecimal 0 in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\WinStations\RDP-Tcp
You can do this via Regedit
Reboot the server
I found that Internet Explorer on the server was pointing to an old proxy server that was likely finally removed from service. I updated the proxy server to the one that is used by the clients and it works fine.
When connecting to our Windows Server 2008 R2 desktop via MS Rdp tool (latest version), occasionally the connection is closing after displaying "Please wait for the Local Session Manager". The result is that I am unable to get into Windows desktop.
Searching the web gives me a hotfix from Microsoft (https://support.microsoft.com/nl-nl/help/2661001/-please-wait-for-local-session-manager-message-remains-for-several-minutes-when-you-disconnect-from-a-computer-that-is-running-windows-server-2008-or-windows-server-2008-r2-during-the-logon-process) which doesn't seem to be downloadable any more.
Also the tip to delete some "usrclass.dat" files did not work (
https://discussions.citrix.com/topic/291092-please-wait-for-the-local-session-manager/?p=1624478) because the files can't be deleted since they're "in use".
Only solution is to reboot Windows, but that's highly impractical for a production web server.
Windows is running virtually on VMWare's Vsphere.
Deleting usrclass.dat DID the trick here. But of course you have to delete this file logged in with admin-account...
I installed Domino Server 9.0.1 and lotus Notes. The Enable DAS option is not available at all in the web Engine tab at all.
How can II enable it as 9.0.1 must support it by default! I am using the Enterprise version. Do I need to install some plugin?
UPDATE
I tried to uninstall it and install it again ,this time selecting standalone mode and the option is available if "Load Internet configurations from Server\Internet Sites documents" to disabled as #Knut Herrmann mentioned.
The issue is that I have to use this domino server as additional server and in that mode I am not getting this option
UPDATE 2
I am using Domino server 9.0.1 in additional server mode, that connects to a main server for syncing the data which has a Domino server 8.5.3 . I am not able to get the option under Web Engine tab to enable DAS.
Set field "Load Internet configurations from Server\Internet Sites documents" to disabled on server document's basic tab:
Only if this option is disabled the section "Domino Access Services" on tab "Internet Protocols / Domino Web Engine" is visible.
I have done some research, based on the problem that my single server gives me when I try to open a document library in windows explorer from the ribbon menu item "Open in Windows Explorer".
The same problem occurs when I try to map sharepoint to a folder in windows explorer too.
The error is:
Your client does not support opening this list with Windows Explorer
From the net, suggestions are:
(Since I'm trying this operation from server itself) enable Desktop Experience
Install the KB907306 update.
Enable IIS webDav service (Some say, it's just for additional functions from the MS Whitepaper)
(Edit) Started webClient service
I've already done them. Nothing changed. Proper machine restart and iis too have done.
Need some serious advice.
Thanks in advance.
Not sure if we are having exactly the same problem BUT I have had similar problem while accessing SP via Windows Explorer in Windows Server 2k8.
What I done to fix it is following:
Install new server feature called Desktop Experience (it comes with WebDAV redirector, which allows you to connect to WebDAV) - Note: Server will need to be restarted.
In Services start WebClient service (go to properties and make sure it starts automatically)
You will now be able to access your sharepoint via entering network path such as \sharepointhost\application\myawesomeapplication\ etc.
Hope that helps.
If you are trying to do this from the server, test it from a server which is not on the SharePoint farm (or better yet, a client machine). Ensure all of your testing is done from machines which are not on the farm.
Do NOT enable the IIS WebDAV service, as SharePoint provides its own WebDAV service and the IIS one overrides it in the pipeline. Enabling this service is a sure path to breaking WebDAV.
If you have SSL enabled, you may be in for a rough time getting it to work. Start by understanding how to use the 'net use' command, and the #SSL suffix.
make sure your webdav is installed as feature
make the following registry fix (http://support.microsoft.com/kb/841215) :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
Add a new DWORD "BasicAuthLevel" and change this to "2"
Restart your machine (and make sure it is enabled in IIS)
Make sure that WebClient windows service is running in the server. This shall appear in client operating systems like Windows 7, windows 8 however, on the server operating systems like Windows Server 2008, it shall be installed by enabling the server feature "Desktop experience" using Server Manager
This issue nearly killed me. I found that I was using a 64 bit version of my browser and that is'nt supported. I changed over to the 32 bit and it works.