Is there a way to indicate to the os that my app be fresh restarted rather than activated and resumed when it becomes deactivated?
The Activated Event is published whenever a user returns and the app gets resumed.
Activated - Occurs when the application is being made active after previously being put into a dormant state or tombstoned.
See about all the events and interception possibilities here on msdn
If you wan't to change the start- and restart behavior, have a look at the fast app resume option.
Related
Every time i reboot my pc and try to run Dev-C++ it asks me for a First configuration.
It is like it doesnt save my preferences and keep me asking for a new configuration but only if i restart my pc.
I tried to google it and tried to see in the options.
I could think it is a feature but in any case i would like to keep my first time configuration even for the next launches
I have Windows 10 build 1511, where I have installed SQL Server 2014.
After installation everything is OK.
I've made several times shutdown on Windows 10, and after if I turn on my PC everything is OK.
But if I restart the system, after the restart, the SQL Server service remains stopped (startup type is Automatic). I try another restart and shutdown, but the service doesn't start automatically anymore.
I've started the service manually, and after the service is started and everything works ok. If I shut down everything, it is ok afterwards. But if I just restart, the problem that I've described above appears again.
What can I do ?
Thank you !
Update
It seems that the problem is already reported to Microsoft :
https://connect.microsoft.com/SQLServer/feedback/details/1873617/sql-server-not-coming-online-after-os-upgrade-to-windows-10-even-when-startup-type-is-automatic
If you starts services.msc and serach for the SqlServer service, in properties, set the startup as automatic delay instead of automatic.
I'm dealing with the same issue on Win 2012. and it looks like the same issue described here:
Add your windows level user in following path:
Click on Start - Run - Secpol.msc Go to Local Policies - User right assignments
Act as a part of the Operating system
bypass Traverse checking
Lock pages in memory
Log on as a service
Log on a batch job
Replace process level token
If not, please add them and try restarting your system. Your SQL Server should be starting as a service. All the best.
I had this issue on Windows 10 and SQL Server 2014 Express.
The delayed start option didn't work for me, but here's what did work - granting higher DCOM permissions to the Network Service and Local Service accounts.
Click Start, type Component and then click the Component Services
app
In Component Services, double-click Component Services, and then double- click Computers. Right-click My Computer, and then click Properties.
Click the COM Security tab.
In the Launch and Activation Permissions area, click Edit Default.
Click Add, type Network Service, and then click OK. While Network Service is selected, click to select the Allow check boxes for the following items:
Local Launch
Remote Launch
Local Activation
Remote Activation
Repeat step 4 for the Local Service account.
Reboot and SQL Server should not start automatically.
In my case, this is a development environment so I'm less concerned about the security implications of this change and more concerned about getting it to work. So be advised to check out potential security ramifications if that's important in your situation.
pay Attention in suffix too
example: if in your user Secedit.msc is as contoso\usersql, in the windows service needs to be the same, I was putting usersql#contoso.com and was having problems to start the service automatic, after change to contoso\usersql, working fine
follow the way,
SQL SERVER INSTALLATION CENTER (C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft SQL Server 2019\Configuration Tools) > Maintenance > Edition Upgrade
and restart service
Another solution worked for me:
Open SQL Server Configuration Manager
Select SQL Server Services
Select any service (double click or right click and properties)
Go to "Log On" tab (My Log On settings was "This Account")
Choose "Built-in account" and "Local Service" under it.
Then I did this steps for every other services and it worked. I have no more problem while I am connecting to SQL Server Databases.
SQL Server Services Log On Settings
I faced this issue today , as my server is dependent on SQL server connection , that was also not booting up. It was simple in my case. I saw in services screen its status is STOP. So I started there ans it started working.
windows+R--> services.msc--> right click on the service and start it.
I have a WP8 app with Fast App Resume enabled. When the app has been running for an extended period of time, and I tap the icon to resume it, it will immediately exit. I have an unhandled event handler that catches exceptions and uploads them to my server, but it never seems to work in this case.
How do I attach Visual Studio to my application that has been tombstoned so I can determine the cause of this crash on resume?
Trick is to enable tombstoning upon deactivation first.
See this link: http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff806372(v=vs.105).aspx
Then, just start your app under the debugger, press the start button (debugger will remain attached) & re-launch your app from the start tile.
Launch Visual Studio select from the Debug Menu Attach To Process. Select the process amd after the Debugger is attached, press Break all.
Know you can examin the stacks of all threads and check what happened
I am trying to create a new mail session in the weblogic console. I am acquiring the lock and
activating the changes to make it visible in the session. I am also able to use it in the
current session. But the problem is that mail session change is lost when I restart my
server. I have to reconfigure the mail session to use it again.
The weblogic server is running in production mode.
Please help.
Thanks & Regards,
Sujeet
It was happening because of a custom script which was overwriting the changes to config.xml upon restart.
In order to make configuration changes through the WLS console, obtain a lock on the editable collection of Configuration MBeans for all servers in the domain. The lock is obtained by clicking the Lock & Edit button.
After performing configuration changes you click the Save or the Finish button. However the changes do not take effect immediately. You have to click the Activate Changes button in the Change Center so that the configuration changes are distributed to each of the servers in the domain. Some changes require a server restart in order to take effect.
The configuration changes are saved in the config.xml file which is located in the path: your_domain_name\config.
You should see a mail-session element in the config.xml:
<mail-session>
<name>MailSession-0</name>
</mail-session>
Sometimes an exception causes application pool to shutdown. I start it manually but the question is how can I automate this behavior in IIS 7.0 (Windows server 2008).
If an application pool dies, the next request for a resource served by that pool will automatically restart it. If, however, you have rapid fail protection enabled on the app pool, and the pool dies more times than the number specified by the maximum failures property within the interval specified by the failure interval property, then you will receive a 503 Service Unavailable message. At this point, you will have to manually restart the app pool.
To work around this, either disable rapid fail protection for the app pool, or try increasing the number of faults within the time period, and then determine the root cause of the exceptions which are terminating the app pool.
open iis select your website and on right hand side u see Actions
under Browse Web site -> Advanced Setting
select start Automatically to true.
I am having a similar problem in Windows Server 2012 Standard and IIS 8. URLs with an ampersand character at the end cause IIS to freak out, and consider them malicious. This causes the App Pool to fail, crashing the website.
What you need to do is watch the Event Viewer for 1309 events. (In the Event ID column) You can set this up using Task Scheduler. When you see the event, you restart the App Pool.
To restart the App Pool, you can use a .vbs script like this:
Set oWebAdmin = GetObject("winmgmts:root\WebAdministration")
Set oAppPool = oWebAdmin.Get("ApplicationPool.Name='DefaultAppPool'")
' Recycle the application pool.
oAppPool.Recycle
Or you could use Powershell if you like that better.
I use a pretty neat C# program that I found here:
http://www.west-wind.com/weblog/posts/2012/Oct/02/A-tiny-Utility-to-recycle-an-IIS-Application-Pool
It does a great job, and seems to get around some of the permissions issues that the previous two methods have. I do have to run this script as an admin, though.
Hope this helps. It does not solve the problem, but it will take the heat off until there is a solution to this URL issue.