Hi,

I am new to Project and about to purchase on premise Project professional 2021, but to ascertain the usability of Project, today purchased Project 3 plan (monthly) in the hope that I get Desktop client to test for a month. As you know, Project professional does not allow trial download, so I have to route to Project 3 plan.

Now, issue is, I am unable to download the desktop client from this Project 3 subscription. In the Apps, I see option of installing Project (image below), if downloaded, I get set up file names ‘OfficeSetup.exe’, and if I install it, office 365 is installed, but I cant find Project.

I tried to follow  https://answers.microsoft.com/en-us/msoffice/forum/all/how-can-i-download-ms-project-in-my-computer/2fd8f0bb-4c2c-47f2-9c74-647fbf53b3b7

but so far no success.

can you please guide me? Thanks in anticipation.

​Hi,I am new to Project and about to purchase on premise Project professional 2021, but to ascertain the usability of Project, today purchased Project 3 plan (monthly) in the hope that I get Desktop client to test for a month. As you know, Project professional does not allow trial download, so I have to route to Project 3 plan. Now, issue is, I am unable to download the desktop client from this Project 3 subscription. In the Apps, I see option of installing Project (image below), if downloaded, I get set up file names ‘OfficeSetup.exe’, and if I install it, office 365 is installed, but I cant find Project.  I tried to follow  https://answers.microsoft.com/en-us/msoffice/forum/all/how-can-i-download-ms-project-in-my-computer/2fd8f0bb-4c2c-47f2-9c74-647fbf53b3b7but so far no success. can you please guide me? Thanks in anticipation.   Read More

​

Hoping someone can shed some light on this as I can’t find any documentation. For upcoming Teams meetings where we have added an agenda (loop component in Teams), we can view and edit that Loop component from the event in Outlook on the web, but not from Outlook desktop app. The desktop app only shows the agenda/loop component for meetings in the past.

Does anyone have any links to documentation or information on when we might see upcoming meeting agendas in Outlook desktop?

I know there are workarounds for this, but we have some folks not interested in workarounds.

Thank you!

​Hoping someone can shed some light on this as I can’t find any documentation. For upcoming Teams meetings where we have added an agenda (loop component in Teams), we can view and edit that Loop component from the event in Outlook on the web, but not from Outlook desktop app. The desktop app only shows the agenda/loop component for meetings in the past. Does anyone have any links to documentation or information on when we might see upcoming meeting agendas in Outlook desktop? I know there are workarounds for this, but we have some folks not interested in workarounds. Thank you!  Read More

​

I’m trying to rename several sheets based on cell values but can’t figure out how to check for duplicate values and add a number to those names.

This is the code I’m starting with, which gets the job done so long as no other worksheets have the same values in both F4 and E4. 

Sub Rename_Sheet()

ActiveSheet.name = Range(“F4″) & ” to ” & Range(“E4”)

End Sub

​I’m trying to rename several sheets based on cell values but can’t figure out how to check for duplicate values and add a number to those names. This is the code I’m starting with, which gets the job done so long as no other worksheets have the same values in both F4 and E4.  Sub Rename_Sheet()ActiveSheet.name = Range(“F4″) & ” to ” & Range(“E4”)End Sub   Read More

​

Hello Experts,

I am trying to use a DateDiff to find the day count between 2 dates. 

I need a Where Clause (blue part)

I am getting a #error though. 

I am not sure if the where clause below is accurate? 

I am not sure if i can use a where clause with a “datediff” like I am doing. 

DayCountDD: Abs(DateDiff(“d”,[qryDrawsDecliningCumDrawn].[FundingDate],”ID=” & [qryDrawsDecliningCumDrawn].[ID] & ” And [FirstOfIDDetailpk] < ” & [qryDrawsDecliningCumDrawn].[FirstOfIDDetailpk],[DayLastBdMo]))

My original was like this and it does work (no #error) but the count is off since I dont have a where clause. 

DayCountDD: Abs(DateDiff(“d”,[qryDrawsDecliningCumDrawn].[FundingDate],[DayLastBdMo]))

Any thoughts are appreciated. 

thank you.

​Hello Experts, I am trying to use a DateDiff to find the day count between 2 dates. I need a Where Clause (blue part)I am getting a #error though. I am not sure if the where clause below is accurate? I am not sure if i can use a where clause with a “datediff” like I am doing.  DayCountDD: Abs(DateDiff(“d”,[qryDrawsDecliningCumDrawn].[FundingDate],”ID=” & [qryDrawsDecliningCumDrawn].[ID] & ” And [FirstOfIDDetailpk] < ” & [qryDrawsDecliningCumDrawn].[FirstOfIDDetailpk],[DayLastBdMo])) My original was like this and it does work (no #error) but the count is off since I dont have a where clause. DayCountDD: Abs(DateDiff(“d”,[qryDrawsDecliningCumDrawn].[FundingDate],[DayLastBdMo])) Any thoughts are appreciated. thank you.  Read More

​

In May 2024, we shared our Exchange Server Roadmap Update and our plans for the future of Exchange Server. Since then, we’ve been asked some questions whose answers we think you’ll find helpful.

First, here are some terms used in this post:

CU stands for Cumulative Update
SU stands for Security Update
CY stands for Calendar Year
H1 / H2 stand for First half / Second half (e.g., of a CY)
RTM stands for Release to Manufacturing (refers to the first release of a software product)
Coexistence refers to versions that can exist in the same Exchange organization

The upgrade path from Exchange Server 2016 and Exchange Server 2019 to Exchange Server Subscription Edition (SE) is different from what we’ve done in the past for several reasons, so we want to first provide details on various scenarios, timelines, and actions to take, and then we have an FAQ at the end of this post with some helpful answers.

All Exchange Server customers are affected by these changes, whether fully on-premises, in a hybrid state, or in a management tools only state (for recipient management).

What are we releasing, and when?

In our roadmap post, we detailed the next three releases for Exchange Server:

Exchange Server 2019 CU15
Exchange Server SE RTM
Exchange Server SE CU1

Here is a table summarizing these releases and their implications on coexistence with previous versions:

Release

Release Date

Details

Coexistence

Exchange Server 2019 CU15

H2 CY 2024

Our final CU for Exchange Server 2019. Code parity with Exchange Server SE RTM (except for any SUs released before Exchange SE RTM).

No coexistence with Exchange 2013
(installation blocked by CU15 Setup)

Exchange Server SE RTM

Early H2 CY 2025

Enables in-place upgrade from Exchange 2019 CU14 or CU15. Code parity with Exchange 2019 CU15 + any SUs released since CU15 (no new features or other code changes).

No coexistence with Exchange 2013
(installation blocked by RTM Setup)

Exchange Server SE CU1

Late H2 CY 2025

First introduction of new features in Exchange Server SE.

No coexistence with Exchange 2013, Exchange 2016, or Exchange 2019 (installation blocked by CU1 Setup)

Support status of Exchange Server versions

The last three versions of Exchange Server, their lifecycles, and how they are affected by the above releases are detailed in the following table:

Exchange Version (Build)

End of Support

Support status at the time of release of…

Exchange 2019 CU15

Exchange SE RTM

Exchange SE CU1

Exchange 2013 (any CU)

April 11, 2023

Not Supported

Exchange 2016 CU23

October 14, 2025

Extended Support

Extended Support

Not Supported

Exchange 2019 CU14/CU15

October 14, 2025

Extended Support

Extended Support

Not Supported

All other versions and builds of Exchange Server are unsupported, except for Exchange 2019 CU13, which will go out of support when Exchange 2019 CU15 is released.

Coexistence of different versions in the same organization

We’re making changes in Exchange Server that affect coexistence with older versions in the same organization. In the past, it was possible for you to continue running an older (and even unsupported) version of Exchange Server in an organization that had newer version(s) of Exchange Server. This is changing in two very important ways:

Setup in Exchange Server 2019 CU15 and Exchange Server SE RTM will block coexistence with Exchange Server 2013.
Setup in Exchange Server SE CU1 will block coexistence with all unsupported versions (e.g., Exchange Server 2013, Exchange Server 2016, Exchange Server 2019) and allow coexistence only with Exchange Server SE.

When Exchange Server SE CU1 is released, all other versions of Exchange Server will be out of support. As detailed in the following table, to install CU1 (or later) you will have to first decommission and remove all older versions of Exchange Server from your organization.

Version

Can coexist in the same organization as…

Exchange 2019 CU14

Exchange 2019 CU15

Exchange SE RTM

Exchange SE CU1

Exchange 2013 (any CU)

Yes, but not supported

No (blocked)

No (blocked)

No (blocked)

Exchange 2016 CU23

Yes

Yes

Yes

No (blocked)

Exchange 2019 CU14/CU15

Yes

Yes

Yes

No (blocked)

Getting from a mixed version organization to an Exchange Server SE organization

To get from where you are today to Exchange Server SE only, you have some options.  At this point, you should be running Exchange Server 2016 CU23 and/or Exchange Server 2019 CU13/CU14. If you are running Exchange 2016 with anything earlier than CU23, you should update to CU23 immediately. We recommend that Exchange 2019 customers run CU14, but we do still support CU13. If you are running any older versions of Exchange Server (e.g., Exchange 2013 or earlier), you should decommission that infrastructure by either moving to Exchange Online, or by upgrading to Exchange Server 2019 with the latest CU.

To get from Exchange 2016 and Exchange 2019 to Exchange Server SE, there are two types of upgrades that can be performed:

Legacy upgrade – the traditional way of moving to a new major version of Exchange Server. It requires introducing the newer server into the organization, moving all mailboxes and resources from older servers to new servers and uninstalling the old servers. Legacy upgrades are required when moving from Exchange 2016 to Exchange 2019, from Exchange 2016 to Exchange Server SE. They are also used when moving to new hardware or a later version of Windows Server.
In-place upgrade – a new way of upgrading to a new version of Exchange Server. It is identical to installing a CU and is available only for upgrades from Exchange 2019 CU14/CU15 to Exchange SE.

In our Exchange Server Roadmap Update we shared a table that lays out the steps needed to get from any version(s) you might be using today, to Exchange Server SE. Here is a slightly updated version of that table:

Version currently in the organization

When Exchange 2019 CU15 releases

When Exchange Server Subscription Edition (SE) RTM releases

Exchange Server 2013 (any CU)

Not supported in the organization and blocked by Setup.

Legacy upgrade to Exchange 2019 CU14 now and update to Exchange 2019 CU15 when available.

Not supported in the organization and blocked by Setup.

Legacy upgrade to Exchange 2019 CU14 now, update to CU15 when available, and in-place upgrade to Exchange Server SE when available.

Exchange Server 2016 CU23

Legacy upgrade to Exchange 2019 CU14 now and update to CU15 when available.

Legacy upgrade to Exchange 2019 CU14 now or CU15 when available, and in-place upgrade to Exchange Server SE when available.

Exchange Server 2016 CU22 and earlier

This version is out of support.

Legacy upgrade to Exchange 2019 CU14 now and update to CU15 when available; or

Update to Exchange 2016 CU23 now, and then legacy upgrade to Exchange 2019 CU15 when available.

This version is out of support.

Update to Exchange 2016 CU23, legacy upgrade to Exchange 2019 CU14/CU15, and then in-place upgrade to Exchange Server SE when available.

Exchange Server 2019 CU14/CU15

Update CU14 servers to Exchange 2019 CU15 when available.

In-place upgrade to Exchange Server SE.

Exchange Server 2019 CU13

Update to Exchange 2019 CU14 now and CU15 when available.

This version will be out of support when Exchange SE is released.

Update to Exchange Server 2019 CU14/CU15, and then in-place upgrade to Exchange Server SE.

Exchange Server 2019 CU12 and earlier

This version is out of support.

Update to Exchange 2019 CU14 now and CU15 when available.

This version is out of support.

Update to Exchange Server 2019 CU14/CU15, and then in-place upgrade to Exchange Server SE.

Here is a summary of what you should be doing and when:

FAQs

Here are some of the FAQs we’ve heard since the release of our roadmap in May 2024.

Are there any server role, edition, or prerequisite changes in Exchange Server SE RTM?
No. Exchange Server SE RTM will support all the same server roles, editions, and prerequisites as Exchange Server 2019.

Are there any performance, sizing, or architecture guidance changes in Exchange Server SE?
No. Sizing, scaling, and deployment guidance for Exchange Server SE is the same as for Exchange Server 2019.

Are there any features being deprecated or removed from Exchange Server SE?
Yes. We have announced that in Exchange SE CU1, we will remove the following features:

Support for UCMA 4.0 and the instant messaging feature in Outlook on the web
Support for Outlook Anywhere (RPC/HTTP) protocol

Why should we upgrade to Exchange Server SE RTM (from earlier versions) if there are no new features?
Exchange Server 2016 and Exchange Server 2019 reach end of support on October 14, 2025. To enable quick and easy in-place upgrades from Exchange Server 2019, we have purposely either pulled new features forward into Exchange Server 2019 CU15 or pushed them to Exchange Server SE CU1 or later, leaving the Exchange SE RTM to be a branding update that introduces new lifecycle and support policies. By moving to Exchange Server SE RTM, your servers are on the supported path to Exchange SE CU1. Once Exchange SE CU1 is released, all older versions will be out of support. We have more features planned after Exchange SE CU1, so Exchange Server development continues.

Can you clarify the license requirements for Exchange Server SE?
Licensing for Exchange Server SE is the same as Exchange Server 2019, with one exception: Microsoft is no longer offering purchases of licenses only (see Microsoft Exchange Server licensing and FAQ for details on the licensing model used by Exchange Server 2019).

For Exchange Server SE, in addition to purchasing the required Server licenses and CALs, customers must also maintain an active subscription. This means purchasing either:

Cloud subscription licenses for all users and devices that access Exchange Server SE (for example, Microsoft 365 E3 or E5 licenses); or
Exchange Server SE Server licenses and CALs with Software Assurance (SA).

Other cloud subscription licenses besides Microsoft 365 E3/E5 also satisfy, but we’re calling E3/E5 out because they include Extended Use Rights that provide an unlimited number of Office Server licenses at no additional charge (see the Microsoft Product Terms for full details).

If you don’t buy cloud subscription licenses, then Server licenses and CALs you buy must have Software Assurance.

To summarize your licensing options (choose one):

Qualifying cloud subscription licenses for users (for example, Microsoft 365 E3/E5) If you go this route, all users that access Exchange Server SE must have an E3 or E5 license.
License (Server and CALs) + SA for Exchange Server 2016/2019 Maintain SA for usage rights and access Exchange Server SE and updates.
License (Server and CALs) + SA for Exchange Server SE (once released) Maintain SA for Exchange Server SE for usage rights and access to updates.

How do we download Exchange Server SE and obtain our product keys (when available)?
Software products licensed through Volume Licensing (VL) agreements (such as Exchange Server 2019) were previously downloaded from the Volume License Service Center (VLSC).  But the legacy VLSC has been retired and distribution has moved to the Microsoft 365 admin center. Customers who purchase Exchange Server SE (and other VL software) download the product and retrieve their product keys from the Microsoft 365 admin center.  See Administering Volume Licensing Frequently Asked Questions for more information.

Does the name Exchange Server Subscription Edition mean that periodic online license validation is required?
No. As with previous versions of Exchange Server, Exchange Server SE does not perform, or have any requirement for, online license validation. Once a valid Exchange Server SE product key is entered, no additional license checks are performed. You simply need to maintain your subscription (as described above) to stay in license compliance and get access to future Exchange Server SE updates via the Volume License page in the Microsoft 365 admin center.

We have Server licenses and CALs for Exchange Server 2016 without Software Assurance (SA). Why should we buy SA for Exchange Server 2019 and upgrade now, since Exchange 2019 goes out of support in CY2025?
Moving from Exchange 2016 to Exchange 2019 is a legacy upgrade process that requires the introduction of new servers and mailbox moves to the newer version. For organizations running Exchange 2016 today, upgrading to Exchange 2019 now allows you to begin (and complete) your last legacy upgrade before Exchange Server SE is available. You can (and should) start that upgrade now instead of waiting and migrating directly from Exchange Server 2016 to Exchange Server SE. Once on Exchange Server 2019, you can upgrade in-place to Exchange Server SE when it is released. Getting to Exchange 2019 today gives you a lot more time to prepare your organization for Exchange Server SE.

Will Exchange Server SE include a free license for Hybrid servers?
Yes. As with previous versions, Exchange Server SE will continue to provide free licenses for qualified hybrid use via the Hybrid Configuration Wizard (HCW); however, unlike previous versions, you will need to either purchase SA for this license to get Exchange Server updates or have a cloud subscription license that satisfies the requirements. Please note that the Hybrid license is for the purposes of recipient management only. If you host mailboxes or need an Edge Transport server on-premises, you still need an Exchange Server license. See this FAQ. Also as with Exchange 2019, you will be able to use PowerShell and the Exchange Management Tools to manage your recipients without the need for a running Exchange Server, thereby obviating the need for any Hybrid licenses.

Will Microsoft extend the end-of-life date, offer extended support, or offer Extended Security Updates (ESU) for Exchange 2016 or Exchange 2019?
No. We are not extending the end-of-life date for Exchange 2016 or Exchange 2019, and we are not offering extended support or ESU for either version. Our efforts are focused on ensuring that the Exchange Server SE release, as well as the in-place upgrade experience, is seamless for customers running Exchange 2019. We strongly recommend all Exchange Server customers who want to remain on-premises to upgrade to Exchange 2019 as soon as possible.

Will there be a public beta of Exchange Server SE for us to validate in our labs?
No. We will not have a public beta for Exchange Server SE. Customers who are members of our TAP program will get early access to releases of Exchange Server SE. But, as we previously announced, Exchange Server SE RTM will be code equivalent to Exchange 2019 CU15 (plus any SUs released in between). In other words, for all intents and purposes, customers who are not in our TAP program can deploy Exchange 2019 CU15 in their organization and get an early look at how Exchange Server SE RTM will behave.

Will Exchange Server SE allow in-place upgrade of Windows Server operating system while Exchange is already installed?
No. Upgrades of the underlying Windows OS on an Exchange Server are not supported and will remain unsupported. We have heard this request and are evaluating it (but have nothing to announce currently). For customers building new servers, we encourage you to install the newest Windows OS before installing Exchange Server on it (including Windows Server 2025 once Exchange 2019 CU15 is released).

For version coexistence, Exchange Server has always supported N-2 (the current and two previous versions) coexisting in the same organization. Why is this changing with Exchange Server SE?
It’s changing because both Exchange Server 2016 and Exchange Server 2019 reach end of support very soon after Exchange Server SE RTM is released. With the release of Exchange Server SE CU1, Exchange Server SE will be the only supported version, and it will remain that way. Because all other versions are out of support, N-2 no longer applies.
The Exchange Server Team

​Microsoft Tech Community – Latest Blogs –Read More 

Introduction

The HTTP 500 Internal Server Error is one of the most common errors faced by developers and administrators when hosting web applications in IIS. This error indicates that the server encountered an issue preventing it completing the request, but it doesn’t provide much detail on what went wrong. To effectively troubleshoot the problem understanding of 500 status code and detailed log collection are essential. In this article, we’ll explore the 500 Internal Server Error, why it happens, and the various methods for collecting useful diagnostic logs.

Overview

The 500 Internal Server Error is a generic server error that occurs when the server cannot process the request due to an unexpected condition. IIS 7.0 and later versions define the following HTTP status codes that indicate a more specific cause of an error 500. The below table illustrate the details sub status code with descriptions.

Code

Description

Notes

500

Module or ISAPI error occurred.

This HTTP status code may occur for many server-side reasons.

500.11

Application is shutting down on the web server.

The request isn’t processed because the destination application pool is shutting down. Wait for the worker process to finish shutting down, and then try the request again. If this problem persists, the web application may be experiencing problems that prevent the web application from shutting down correctly.

500.12

Application is busy restarting on the web server.

The request isn’t processed because the destination application pool is restarting. This HTTP status code should disappear when you refresh the page. If this HTTP status code appears again after you refresh the page, the problem may be caused by antivirus software that is scanning the Global.asa file. If this problem persists, the web application may be experiencing problems that prevent the web application from restarting correctly.

500.13

Web server is too busy.

The request isn’t processed because the server is too busy to accept any new incoming requests. Typically, this HTTP status code means that the number of incoming concurrent requests exceeds the number that the IIS 7.0 and later versions web application can process. This problem may occur when the performance configuration settings are set too low, the hardware is insufficient, or a bottleneck occurs in the IIS 7.0 and later versions web application. A common troubleshooting method is to generate a memory dump file of the IIS 7.0 and later versions processes when the error is occurring and then to debug the memory dump file.

500.15

Direct requests for Global.asax aren’t allowed.

A direct request for the Global.asa file or for the Global.asax file is made.

500.19

Configuration data is invalid.

This HTTP status code occurs because of a problem in the associated applicationhost.config file or in the associated Web.config file.

500.21

Module not recognized.

500.22

An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.

500.23

An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.

500.24

An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.

500.5

A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.

Here’s where the distributed rules configuration is read for both inbound and outbound rules.

500.51

A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.

Here’s where the global rules configuration is read.

500.52

A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.

500.53

A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.

500.1

Internal ASP error.

An error occurs during the processing of an Active Server Pages (ASP) page. To obtain more specific information about the error, disable friendly HTTP error messages in the web browser. Additionally, the IIS log may show an ASP error number that corresponds to the error that occurs.

To learn more about http status codes grab this article – HTTP status code overview – Internet Information Services | Microsoft Learn.

Log Collections

Because 500 Internal Server Errors a general error, pinpointing the root cause requires in-depth investigation. This is where log collection plays a crucial role. You need to collect the following logs –

IIS Logs
Failed Request Tracing Logs
Event logs for application and system.
ETW traces
Memory dump

1. IIS Logs

It is the starting point for troubleshooting any server error. These logs provide a record of all incoming HTTP requests and the server’s response, including status codes, timestamps, and more. Follow the below steps to enable IIS logs –

Open IIS Manager.
Navigate to your website in the Connections pane.
Open Logging. Logs are typically saved in C:inetpublogsLogFiles. Update the location as per your convenience. 
And click apply.

To collect the logs, navigate to the log file directory and find the folder name that ends with site number. To know the sites number, Go to Sites from the Connection pane. And look for the ID column. For example, if the site id is 2 then the folder name would be W3SVC2.

2. Failed Request Tracing Logs

Failed Request Tracing Logs or FREB offer more granular insight than IIS logs by breaking down the request processing pipeline. They track which part of the pipeline causes the failure. Follow the below steps to configure FREB.

Open IIS Manager
Navigate to your website in the Connections pane.
Open Failed Request Tracing
Click Add from right-hand action pane.

Select All content(*)
Click Next
Check Status codes(s) checkbox.
Status code should be 500-600
And click Next.

Check all provides check boxes.
And click Finish.
Select the newly created rules and click on Edit Site Tracing.
Check Enable check box
Update a directory path(or leave it to default)
And click Ok.

To collect the logs, navigate to the log file directory and find the folder name that ends with site number. For example, if the site id is 1 then the folder name would be W3SVC1.

3. Event Log

The windows Event Log is another valuable source of information, especially when dealing with application crashes, service restarts, or other server-related issues that might trigger the 500 error.

Open Event Viewer
Export Application and System logs under Windows Logs section by saving all without any filters in .evtx format.

4. ETW Traces

You need to use PerfView tool, it is a powerful diagnostic tool for collecting performance traces and analyzing .NET applications. It’s especially helpful for investigating performance bottlenecks or runtime issues that can lead to a 500 error.

Download the Perfview tool from Releases · microsoft/perfview (github.com)on the Server. It’s a profiler tool that captures ETW events (no installation required).
Open Perfview tool and
Go to Collect menu and select Collect option.
Select Zip, Merge, Thread Time check boxes as below.
Expand the Advanced Options
Select Kernel Base, .NET, CPU Samples, IIS, and Tasks(TPL) checkboxes as show below.
In the additional provider add the string *Microsoft-Extensions-Logging  and in case of .Net Core add *Microsoft.AspNetCore.Hosting [do not miss * at the beginning]

Click Start Collection button.
Replicate the issue
Stop collection by clicking Stop collection,
Wait for some time to allow it to Merge, it will generate Perfview.etl.zip file.

5. Memory dump

When your application crashes unexpectedly, a memory dump captures the state of the application at the moment of the crash, including active threads, memory usage, and error states. This is useful for diagnosing severe issues that lead to 500 errors. Since the actual error is yet to be identified, you need to capture dumps on first chance exception. Follow the below steps –

Download and install DebugDiag tool from this official download link – Download Debug Diagnostic Tool v2 Update 3 from Official Microsoft Download Center
Open DebugDiag 2 Collection.
Click on Add Rule
And select Crash and click Next.
Select A specific IIS web application pool
Click Next
And choose the application pool of the application in question.

Select Action type to Full Userdump
And action limit count to 3.
Click Next.
Choose an output location to store the dump files.
And Save
After that Activate the Rule.

Conclusion

HTTP 500 Internal Server Errors can be elusive and challenging to troubleshoot, but with the right log collection techniques, you can narrow down the causes and find a solution more efficiently. Start with basic IIS logs for high-level information, dive deeper with Failed Request Tracing logs for detailed request failures, use PerfView for performance bottlenecks, and, if necessary, collect memory dumps for deeper analysis of crashes and unhandled exceptions.  If you are comfortable analyzing this data then you should be able to draw insights from the collected logs. If you want us to do that, please contact us with a case and we will do it for you.

​Microsoft Tech Community – Latest Blogs –Read More 

Hi,

Can the Surface laptop 4 support type-C PD charging? If I have 65W GaN power supply.

Thanks in advance.

Jason

​Hi, Can the Surface laptop 4 support type-C PD charging? If I have 65W GaN power supply. Thanks in advance. Jason  Read More

​

The marketplace value calculator is a new tool that allows you to see exactly how many direct value benefits, cloud credits, and incentives your business can unlock with the Microsoft commercial marketplace. After plugging in just a few projections, you’ll be able to see (and share with your colleagues) how these benefits, cash, and free products outweigh marketplace fees.

This will help you, and others at your company, see the costs and benefits associated with building, launching, and selling with Microsoft.

Check out the blog to learn more about this new tool available for partners on the marketplace: Introducing the marketplace value calculator – Microsoft Community Hub

​The marketplace value calculator is a new tool that allows you to see exactly how many direct value benefits, cloud credits, and incentives your business can unlock with the Microsoft commercial marketplace. After plugging in just a few projections, you’ll be able to see (and share with your colleagues) how these benefits, cash, and free products outweigh marketplace fees. This will help you, and others at your company, see the costs and benefits associated with building, launching, and selling with Microsoft.
 
Check out the blog to learn more about this new tool available for partners on the marketplace: Introducing the marketplace value calculator – Microsoft Community Hub  Read More

​

To fully understand information systems, you must understand the broader organization, management, and information technology dimensions of systems (see Figure 1. 5 ) and their power to provide solutions to challenges and problems in the business environment. We refer to this broader understanding of information systems, which encompasses an understanding of the management and organizational dimensions of systems as well as the technical dimensions of systems, as information systems literacy. Computer literacy, in contrast, focuses primarily on knowledge of information technology.

The field of management information systems (MIS) tries to achieve this broader information systems literacy. MIS deals with behavioral issues as well as technical issues surrounding the development, use, and impact of information systems used by managers and employees in the firm. Let’s examine each of the dimensions of information systems—organizations, management, and information technology.

​To fully understand information systems, you must understand the broader organization, management, and information technology dimensions of systems (see Figure 1. 5 ) and their power to provide solutions to challenges and problems in the business environment. We refer to this broader understanding of information systems, which encompasses an understanding of the management and organizational dimensions of systems as well as the technical dimensions of systems, as information systems literacy. Computer literacy, in contrast, focuses primarily on knowledge of information technology.The field of management information systems (MIS) tries to achieve this broader information systems literacy. MIS deals with behavioral issues as well as technical issues surrounding the development, use, and impact of information systems used by managers and employees in the firm. Let’s examine each of the dimensions of information systems—organizations, management, and information technology.  Read More

​

Some of my users have a new interface for web OneDrive search results (for folders shared to them) that no longer offers the Tiles view. The Tiles view is critical for our team to be able to visually search many images. It looks like the Tiles view is being removed? We are sharing large amounts of images that can not be synched, so we must be able to search OneDrive on the web, and see the results visually. It is also now happening for me, even when searching my own OneDrive. There used to be an option on the rights side above the list. It defaulted to “List” view but could be changed to “Tiles.” Now it’s gone!  

This is what it used to have:

How do I get this function back?

​Some of my users have a new interface for web OneDrive search results (for folders shared to them) that no longer offers the Tiles view. The Tiles view is critical for our team to be able to visually search many images. It looks like the Tiles view is being removed? We are sharing large amounts of images that can not be synched, so we must be able to search OneDrive on the web, and see the results visually. It is also now happening for me, even when searching my own OneDrive. There used to be an option on the rights side above the list. It defaulted to “List” view but could be changed to “Tiles.” Now it’s gone!   This is what it used to have:How do I get this function back?   Read More

​