Analysis of two small problems encountered during development

I. A common problem in ASP. NET 2.0 is as follows:

 

When a connection is established to the server, a Failover occurs. When the slave node is connected to SQL Server 2005, the cause of the failure may be that, at the preset level, SQL Server does not allow the slave node to be connected. (Provider: SQL Web interface, error: 26-when searching for a specified server/Website user, the specified website is generated)
Description: exceptions that are not handled in the processes currently required by the Web. Please refer to the heap tracing to obtain the dynamic metadata and production location in the program.

Exception: System. Data. SqlClient. SqlException. When the slave node is connected to SQL Server 2005, the cause of the failure may be that, at the preset level, SQL Server does not allow the slave node to be connected. (Provider: SQL Web interface, error: 26-when searching for a specified server/Website user, the specified website is generated)

The reason for this problem is that, in the case of a temporary statement, SQL Express does not enable local connections, but only enables local connections. The solution is as follows:

 

The security of QL Server2005 is limited to local connections, and no remote connections are enabled;
Method for opening the producer terminal:
Start-> All Programs-> ms SQL Server2005-> Configuration tool-> ms SQL Server2005 application configurator-> server and zookeeper application configurator->
Select Local Connection and local connection under Database Engine. Use "TCP/IP and name pipes" at the same time"
Select local connections and local connections under Analysis Services"
Reuse of resources after application

 

2. When using SqlPersistenceService of workflow, I began to find that I could not connect to the resource without any further discussion. Later I found that I wanted to enable MSDTC.

The full coverage of MSTDC is Distributed Transaction Coordinator, which is included in server service management. the role is to handle transactions that span multiple resource administrators, such as information indexes, interest distribution columns, and Case systems.

This service cannot solve the above problem. In the past, there was another place to configure

 

Open "management tools-component services" to activate "component services-e-commerce", and click "my computers" on the right. In the MSDTC selection card, click "Security Configuration" and press "renew.
Perform the following settings in the security configuration dialog box:

Select "Web DTC FAQs"

Select "allow remote system management"

Select "Allow inbound", "Allow outbound", and "do not require access to the certificate" in the event management channel"

DTC Registration Certificate: NT Authority \ NetworkService

 

The above is a small problem I encountered during development. I made a mark so that I could not go on the road again later.