You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/reference-app-settings.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ The following environment variables are related to the app environment in genera
41
41
|`WEBSITE_PROACTIVE_AUTOHEAL_ENABLED`| By default, a VM instance is proactively corrected when it uses more than 90% of allocated memory for more than 30 seconds, or when 80% of the total requests in the last two minutes take longer than 200 seconds. If a VM instance triggers one of these rules, the recovery process is an overlapping restart of the instance.<br/><br/>Set to `false` to disable this recovery behavior. The default is `true`.<br/><br/>For more information, see the [Introducing Proactive Auto Heal](https://azure.github.io/AppService/2017/08/17/Introducing-Proactive-Auto-Heal.html) blog post. |
42
42
|`WEBSITE_PROACTIVE_CRASHMONITORING_ENABLED`| Whenever the w3wp.exe process on a VM instance of your app crashes due to an unhandled exception for more than three times in 24 hours, a debugger process is attached to the main worker process on that instance. The debugger process collects a memory dump when the worker process crashes again. This memory dump is then analyzed, and the call stack of the thread that caused the crash is logged in your App Service logs.<br/><br/>Set to `false` to disable this automatic monitoring behavior. The default is `true`.<br/><br/>For more information, see the [Proactive Crash Monitoring in Azure App Service](https://azure.github.io/AppService/2021/03/01/Proactive-Crash-Monitoring-in-Azure-App-Service.html) blog post. |
43
43
|`WEBSITE_DAAS_STORAGE_SASURI`| During crash monitoring (proactive or manual), the memory dumps are deleted by default. To save the memory dumps to a storage blob container, specify the shared access signature (SAS) URI. |
44
-
|`WEBSITE_CRASHMONITORING_ENABLED`| Set to `true` to enable [crash monitoring](https://azure.github.io/AppService/2020/08/11/Crash-Monitoring-Feature-in-Azure-App-Service.html) manually. You must also set `WEBSITE_DAAS_STORAGE_SASURI` and `WEBSITE_CRASHMONITORING_SETTINGS`. The default is `false`.<br/><br/>This setting has no effect if remote debugging is enabled. Also, if this setting is set to `true`, [proactive crash monitoring](https://azure.github.io/AppService/2021/03/01/Proactive-Crash-Monitoring-Feature-in-Azure-App-Service.html) is disabled. |
44
+
|`WEBSITE_CRASHMONITORING_ENABLED`| Set to `true` to enable [crash monitoring](https://azure.github.io/AppService/2020/08/11/Crash-Monitoring-Feature-in-Azure-App-Service.html) manually. You must also set `WEBSITE_DAAS_STORAGE_SASURI` and `WEBSITE_CRASHMONITORING_SETTINGS`. The default is `false`.<br/><br/>This setting has no effect if remote debugging is enabled. Also, if this setting is set to `true`, [proactive crash monitoring](https://azure.github.io/AppService/2021/03/01/Proactive-Crash-Monitoring-in-Azure-App-Service.html) is disabled. |
45
45
|`WEBSITE_CRASHMONITORING_SETTINGS`| JSON with the following format:`{"StartTimeUtc": "2020-02-10T08:21","MaxHours": "<elapsed-hours-from-StartTimeUtc>","MaxDumpCount": "<max-number-of-crash-dumps>"}`. Required to configure [crash monitoring](https://azure.github.io/AppService/2020/08/11/Crash-Monitoring-Feature-in-Azure-App-Service.html) if `WEBSITE_CRASHMONITORING_ENABLED` is specified. To log the call stack without saving the crash dump in the storage account, add `,"UseStorageAccount":"false"` in the JSON. |
|`WEBSITE_CONTENTAZUREFILECONNECTIONSTRING`| By default, App Service creates a shared storage for you at app creation. To use a custom storage account instead, set to the connection string of your storage account. For functions, see [App settings reference for Azure Functions](../azure-functions/functions-app-settings.md#website_contentazurefileconnectionstring).<br/><br/>Example: `DefaultEndpointsProtocol=https;AccountName=<name>;AccountKey=<key>`|
@@ -180,6 +180,7 @@ This section shows the configurable runtime settings for each supported language
180
180
|`WEBSITE_JAVA_MAX_HEAP_MB`| Java maximum heap, in megabytes. This setting is effective only when you use an experimental Tomcat version. |
181
181
|`WEBSITE_DISABLE_JAVA_HEAP_CONFIGURATION`| Manually disable `WEBSITE_JAVA_MAX_HEAP_MB` by setting this variable to `true` or `1`. |
182
182
|`WEBSITE_AUTH_SKIP_PRINCIPAL`| By default, the following Tomcat [HttpServletRequest interfaces](https://tomcat.apache.org/tomcat-5.5-doc/servletapi/javax/servlet/http/HttpServletRequest.html) are hydrated when you enable the built-in [authentication](overview-authentication-authorization.md): `isSecure`, `getRemoteAddr`, `getRemoteHost`, `getScheme`, `getServerPort`, `getLocalPort`, `getRequestURL`. To disable it, set the value to `1`. |
183
+
|`WEBSITE_AUTH_EXPIRED_SESSION_LOGOFF`| If a webapp uses EasyAuth, set this to `true` or `1` to force a redirect to the EasyAuth logout page if the session associated to a request has expired (e.g. for webapps running on Tomcat, this is defined by the element `session-timeout` in the file `web.xml`). |
183
184
|`WEBSITE_SKIP_FILTERS`| To disable all servlet filters that App Service added, set to `1`. |
184
185
|`IGNORE_CATALINA_BASE`| By default, App Service checks if the Tomcat variable `CATALINA_BASE` is defined. If not, it looks for the existence of `%HOME%\tomcat\conf\server.xml`. If the file exists, it sets `CATALINA_BASE` to `%HOME%\tomcat`. To disable this behavior and remove `CATALINA_BASE`, set this variable to `1` or `true`. |
185
186
|`PORT`| Read-only. For Linux apps, the port that the Java runtime listens to in the container. |
@@ -95,7 +95,7 @@ After you've verified that the function runs correctly on your local computer, i
95
95
96
96
## Publish the project to Azure
97
97
98
-
Visual Studio can publish your local project to Azure. Before you can publish your project, you must have a function app in your Azure subscription. If you don't already have a function app in Azure, Visual Studio publishing creates one for you the first time you publish your project. In this article, you create a function app and related Azure resources.
98
+
Visual Studio can publish your local project to Azure. Before you can publish your project, you must have a function app in your Azure subscription. If you don't already have a function app in Azure, Visual Studio can help you create one before you publish your project. In this article, you create a function app that runs on Linux in a Flex Consumption plan, which is the recommended plan for event-driven and secure serverless functions.
99
99
100
100
[!INCLUDE [Publish the project to Azure](../../includes/functions-vstools-publish.md)]
101
101
@@ -105,7 +105,7 @@ Visual Studio can publish your local project to Azure. Before you can publish yo
105
105
106
106
1. Under **Functions**, select your new function named **HttpExample**, then in the function page select **Get function URL** and then the **Copy to clipboard icon**.
107
107
108
-
1. In the address bar in your browser, paste the URL you just copied and run the request.
108
+
1. In the address bar in your browser, paste the URL you copied and run the request.
109
109
110
110
The URL that calls your HTTP trigger function is in the following format:
111
111
@@ -119,7 +119,7 @@ Visual Studio can publish your local project to Azure. Before you can publish yo
119
119
120
120
*Resources* in Azure refer to function apps, functions, storage accounts, and so forth. They're grouped into *resource groups*, and you can delete everything in a group by deleting the group.
121
121
122
-
You created Azure resources to complete this quickstart. You may be billed for these resources, depending on your [account status](https://azure.microsoft.com/account/) and [service pricing](https://azure.microsoft.com/pricing/). Other quickstarts in this collection build upon this quickstart. If you plan to work with subsequent quickstarts, tutorials, or with any of the services you've created in this quickstart, don't clean up the resources.
122
+
You created Azure resources to complete this quickstart. You could be billed for these resources, depending on your [account status](https://azure.microsoft.com/account/) and [service pricing](https://azure.microsoft.com/pricing/). Other quickstarts in this collection build upon this quickstart. If you plan to work with subsequent quickstarts, tutorials, or with any of the services you've created in this quickstart, don't clean up the resources.
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-premium-plan.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Azure Functions Premium plan
3
3
description: Learn about details and configuration options (virtual network, no cold start, unlimited execution duration) for the Azure Functions Premium plan.
@@ -56,21 +56,21 @@ In the Premium plan, you can have your app always ready on a specified number of
56
56
57
57
This app-level setting also controls your plan's minimum instances. For example, consider having three function apps in the same Premium plan. When two of your apps have always-ready instance count set to one, and the third app is set to five, the minimum number for your whole plan is five. This also reflects the minimum number of instances for which your plan is billed. The maximum number of always-ready instances we support per app is 20.
58
58
59
-
# [Portal](#tab/portal)
59
+
####[Portal](#tab/portal)
60
60
61
61
You can configure the number of always ready instances in the Azure portal by selecting your **Function App**, going to the **Platform Features** tab, and selecting the **Scale Out** options. In the function app edit window, always ready instances are specific to that app.
62
62
63
63
:::image type="content" source="media/functions-premium-plan/scale-out.png" alt-text="Screenshot that shows the elastic scale settings in the portal.":::
64
64
65
-
# [Azure CLI](#tab/azurecli)
65
+
####[Azure CLI](#tab/azurecli)
66
66
67
67
You can also configure always ready instances for an app by using the Azure CLI.
68
68
69
69
```azurecli-interactive
70
70
az functionapp update -g <RESOURCE_GROUP> -n <FUNCTION_APP_NAME> --set siteConfig.minimumElasticInstanceCount=<YOUR_ALWAYS_READY_COUNT>
71
71
```
72
72
73
-
# [Azure PowerShell](#tab/azure-powershell)
73
+
####[Azure PowerShell](#tab/azure-powershell)
74
74
75
75
You can also configure always ready instances for an app by using Azure PowerShell.
76
76
@@ -99,19 +99,19 @@ Consider this example that shows how always ready instances and prewarmed instan
99
99
1. As load increases and your app needs more instances to handle HTTP traffic, that prewarmed instance is swapped to an active instance. HTTP load is now routed to all three instances, and a fourth instance is instantly provisioned to fill the prewarmed buffer.
100
100
1. This sequence of scaling and prewarming continues until the maximum instance count for the app is reached or load decreases causing the platform to scale back in after a period. No instances are prewarmed or activated beyond the maximum.
101
101
102
-
# [Portal](#tab/portal)
102
+
####[Portal](#tab/portal)
103
103
104
104
You can't change the prewarmed instance count setting in the portal. You must instead use the Azure CLI or Azure PowerShell.
105
105
106
-
# [Azure CLI](#tab/azurecli)
106
+
####[Azure CLI](#tab/azurecli)
107
107
108
108
You can modify the number of prewarmed instances for an app using the Azure CLI.
109
109
110
110
```azurecli-interactive
111
111
az functionapp update -g <RESOURCE_GROUP> -n <FUNCTION_APP_NAME> --set siteConfig.preWarmedInstanceCount=<YOUR_PREWARMED_COUNT>
112
112
```
113
113
114
-
# [Azure PowerShell](#tab/azure-powershell)
114
+
####[Azure PowerShell](#tab/azure-powershell)
115
115
116
116
You can modify the number of prewarmed instances for an app using the Azure PowerShell.
Copy file name to clipboardExpand all lines: articles/backup/troubleshoot-sap-ase-sybase-database-backup.md
+52-1Lines changed: 52 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Troubleshooting SAP ASE (Sybase) database backup (preview) using Azure Backup
3
3
description: Learn to troubleshoot SAP ASE (Sybase) database backup using Azure Backup.
4
4
ms.topic: troubleshooting
5
-
ms.date: 11/23/2024
5
+
ms.date: 05/02/2025
6
6
ms.service: azure-backup
7
7
author: jyothisuri
8
8
ms.author: jsuri
@@ -190,6 +190,57 @@ This article provides troubleshooting details for error codes that appears when
190
190
191
191
**Recommended action**: Run the updated pre-registration script in the virtual machine, which will add the default configuration in the `config` file and retry. If the error persists after that, contact Microsoft Support.
192
192
193
+
### DatabaseConnectionError
194
+
195
+
**Error code**: `DatabaseConnectionError`
196
+
197
+
**Error message**: An error occurred while executing the query on the database. The database is already open and can only have one user at a time.
198
+
199
+
**Cause**: The database might be set to single user mode, which prevents additional connections.
200
+
201
+
**Recommended action**: To resolve the error, follow these steps:
202
+
203
+
1. Check the database configuration to ensure that it allows multiple connections if required.
204
+
1. Validate and disable the single user mode if it is enabled using `sp_dboption`. Learn how to [use `sp_dboption`](https://help.sap.com/docs/SAP_ASE/29a04b8081884fb5b715fe4aa1ab4ad2/ab5c9f3abc2b1014978feb816ba90fa0.html).
205
+
206
+
If the issue persists, contact Microsoft support.
207
+
208
+
### SingleUserModeIsEnabled
209
+
210
+
**Error code**: `SingleUserModeIsEnabled`
211
+
212
+
**Error message**: Database (`{databaseName}`) is currently in single user mode.
213
+
214
+
**Cause**: The database is currently in single user mode, which might cause the restore operation to fail. Attempt to disable single user mode was unsuccessful.
215
+
216
+
**Recommended action**: Sign in to the ASE server and disable the single user mode for the database using the `sp_dboption` stored procedure. Learn how to [use `sp_dboption`](https://help.sap.com/docs/SAP_ASE/29a04b8081884fb5b715fe4aa1ab4ad2/ab5c9f3abc2b1014978feb816ba90fa0.html).
217
+
218
+
If the issue persists, contact Microsoft support.
219
+
220
+
221
+
### NotAbleToEnableSingleUserMode
222
+
223
+
**Error code**: `NotAbleToEnableSingleUserMode`
224
+
225
+
**Error message**: The single user mode didn't change for database (`{databaseName}`) after you attempt to enable it.
226
+
227
+
**Cause**: This issue may occur due to a problem preventing the change of single user mode.
228
+
229
+
**Recommended action**: Sign in to the ASE server and manually attempt to enable and disable the single user mode for the database, then retry the operation. Learn how to [use `sp_dboption`](https://help.sap.com/docs/SAP_ASE/29a04b8081884fb5b715fe4aa1ab4ad2/ab5c9f3abc2b1014978feb816ba90fa0.html).
230
+
231
+
If the issue persists, contact Microsoft support.
232
+
233
+
234
+
### NotAbleToDisableSingleUserMode
235
+
236
+
**Error code**: `NotAbleToDisableSingleUserMode`
237
+
238
+
**Error message**: The single user mode didn't change for database (`{databaseName}`) after you attempt to disable it.
239
+
240
+
**Recommended action**: Sign in to the SAP ASE server and disable the single user mode for the database using the `sp_dboption` stored procedure. Learn how to [use `sp_dboption`](https://help.sap.com/docs/SAP_ASE/29a04b8081884fb5b715fe4aa1ab4ad2/ab5c9f3abc2b1014978feb816ba90fa0.html).
0 commit comments