I have an IIS Application Pool Spark.Release configured with a site pointing to a directory on a local C:\ drive. The pool starts automatically but when visiting http://localhost/ the app pool changes to "Stopped" status.
In Event Viewer Windows Logs > Application I see this:
There was an error during processing of the managed application
service auto-start for configuration path:
'MACHINE/WEBROOT/APPHOST/Spark.Release/'. The error message returned
is: ''. The worker process will be marked unhealthy and be shutdown.
The data field contains the error code.
In Windows Logs > System there are 5 occurences of:
A process serving application pool 'Spark.Release' reported a failure
during application preloading or service loading. The process id was
'2344'. Please ensure that all application preload or service
settings in the application pool are configured properly. The data
field contains the error number.
Before this:
Application pool 'Spark.Release' is being automatically disabled due
to a series of failures in the process(es) serving that application
pool.
OS is Windows Server 2016 Datacentre edition.
Where can I begin troubleshooting this? I'm not seeing any logs in my log directory either, literally zero. It's running under the ApplicationPoolIdentity identity.
A required IIS module was not installed 'URL Rewrite' which was being used by the code. There was no indication in any logs that this was the issue.
Related
I am running a Windows Server VM on GCP.
When logging in via Remote Desktop, I am starting certain applications which should actively run for a couple of hours.
But when closing my Remote Desktop Connection, all applications stop working.
How can I prevent this from happening?
In order to keep the session ongoing, you'll have to configure the RD Session Host time limits.
Open the group policy editor with: Windows+R, then type gpedit.msc, confirm with Enter.
Then in the management console, navigate to:
Computer Configuration
Administrative Templates
Windows Components
Remote Desktop Services
Remote Desktop Session Host
Session Time Limits
There one can adjust the settings:
Set time limit for disconnected sessions
Terminate session when time limits are reached
Recently our Sharepoint server 2013 database was upgraded from SQL server 2008 R2 to SQL server 2012 SP4. This has resulted in several issues.
There now two servers created in a single server farm one representing IP address and the other having host name. Both of the servers are having full set of services. Earlier it was only one server showing the host name
The search service is not running.
The Start and Stop of services on the server with IP address completes successfully, but on the server having the host name get stuck on starting or stopping stage.
Recreation of service applications like search service or user profile service also gets stuck and never complete
There are also two timer service instances, one for each machine, but starting or stopping any of them never gets completed and remains stuck.
What I want.
Only one server in the farm showing host name
All the services working i.e not getting stuck in starting stopping and service application like search and user profile working.
Server has just one application for port 80 and one for CA
This is a production server and each day 1500 to 2000 tasks are generated and similar number of workflows are run this means I cant risk outage.
Thanks in advance
Regards
Imran
Solved Search Service Issue
Stored the Search Service Application
$ssa=Get-SPEnterpriseSearchServiceapplication -Identity XXXXXXX
Stored Service instance
$si = $ssa.service.Instances
Noticed that the proxy for Search service application was also not created
created proxy
$proxy=New-SPEnterpriseSearchServiceApplicationProxy -SearchApplication $ssa
Set the admin component by
Set-SPEnterpriseSearchAdministrationComponent -SearchApplication $ssa -SearchServiceInstance $si
Noticed that Search Administration Web Service for Search Service Application was showing Stopped and Search Service Application was showing Error status, started by
$ssa.Provision()
Checked the status of both the Service Applications it was showing started
Checked the admin component by
$ssa.AdminComponent
It was showing server name
At least one of my problems was solved and my users are able to do searches. I still have to resolve other issues.
I have an EC2 (Windoes Server R2 2012) that is running a NodeJS process. Now, the detail is that once I get Disconnected from server (Disconnection it is supposed to keep everything on server, hence my NodeJS process) after a few minutes, the session is killed, so also the process.
I connect again and it is like I have signed out. How can I solve this? I really need to the process still running without stay ALWAYS connected to the server.
Normally Windows installation will not logoff disconnected sessions.
Your installation is probably customized for it to be logging off disconnected RDP sessions.
Load the Group Policy Object Editor and go to Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Session Time Limits.
Check that the setting "Set time limit for disconnected sessions" is either Not Configured, or Enabled, but with a setting of Never.
I am currently using Jetty 9.1.4 on Windows.
When I deploy the war file without hot deployment config, and then restart the Jetty service. During that 5-10 seconds starting process, all client connections to my Jetty server are waiting for the server to finish loading. Then clients will be able to view the contents.
Now with hot deployment config on, the default Jetty 404 error page shows within that 5-10 second loading interval.
Is there anyway I can make the hot deployment has the same behavior as the complete restart - clients connections will wait instead seeing the 404 error page ?
Unfortunately this does not seem to be possible currently after talking with the Jetty developers on IRC #jetty.
One solution I will try to use are two Jetty instances with a loadbalancing reverse proxy (e.g. nginx) before them and taking one instance down for deployment.
Of course this will instantly lead to new requirements (session persistence/sharing) which need to be handled. So in conclusion: much work to do in the Java world for zero downtime on deployments.
Edit: I will try this, seems like a simple enough solution http://rafaelsteil.com/zero-downtime-deploy-script-for-jetty/ Github: https://github.com/rafaelsteil/jetty-zero-downtime-deploy
I have developed a web service in c# (ASP.NET), and published it in IIS 6.1 (Windows Server 2008). Web application takes data from this web service, but time after time it does not return anything. After I restart web service it works again normally. I don't understand why web service stops returning result time after time. What can cause this? Any help please?
Hard to say without knowing any details. But an approach would be checking the event logs.
Set the Idle timeOut for an Application Pool to 0 instead of default value of 20 minutes for having no timeout when your service is idle.
using inetmgr
Open IIS Manager. For information about opening IIS Manager, see Open
IIS Manager (IIS 7).
In the Connections pane, expand the server node and click Application
Pools.
On the Application Pools page, select the application pool for
which you want to specify idle time-out settings, and then click
Advanced Settings in the Actions pane.
In the Idle Time-out (minutes) box, type a number of minutes, and then click OK.
uisng cmd
appcmd set config /section:applicationPools /[name=' string
'].processModel.idleTimeout: timeSpan
appcmd set config /section:applicationPools /[name=' Marketing '].processModel.idleTimeout:0.00:30:00