The "Unspecified error" workaround rollup appears for the win server file upload download

Environment

　　Win Platform IIS Server

Often appears on ASPX pages

Summary

1. Permissions issues

　　Scenario: Based on an Access database

Cause resolution:

1. First you need to troubleshoot your own problems, such as the use of keywords, formatting errors, insert data and database type mismatch, etc.

2.TEMP permission check to get current server permissions when data is written to the database only the temp Write permission of IIS is set for data writing

　Workaround:

The first workaround: Use the "Tools, Database Utility," and "Compress and Repair Database" in MS Access to fix the Db/global.asa. If the repair is still an error, please check the DB directory for the Global.dbl file, if you do not delete, please end the server w3wp.exe process (win2003) or Aspnet_wp.exe process (Win2000) and then delete.
Description: This method is suitable for database setup errors, resulting in data write failures, and is more likely to find the problem

The second solution:
To set the application pool in Internet Information Services (IIS) Manager, change the properties of the site's program pool see:

　　　　

You can fix the problem after adjusting.
Description: Standard IIS Server Permissions settings issue, General Enterprise has operations department dedicated maintenance usually does not appear in this situation

The third workaround:
In fact, just a few simple steps:
Begin... Run... regsvr32 jscript.dll start ...
Run... regsvr32 vbscript.dll start ...
Run... IISReset

Description: Simple Baidu a bit REGSVR32 for the system registration and anti-registration tools, the tool is mainly used to repair system files such as the above refers to Regsvr32 jscript.dll Fixed the JS file native registration problem is equivalent to re-fix the concept of reference (not sure) it contains a lot of tools to see for themselves, the last sentence iisreset restart the IIS service

2. System service Issues

Scene: Various file uploads, EXCEL WORD, etc.

Reason analysis: Most of the uploaded files under win platform are divided into two kinds of oldb and Npoi

OLDB: When the file is uploaded to the server, the server needs to invoke its parser to read the current file to get the data through the link string to feed the dataset or DataTable data, and analyze the underlying code as follows

　　　　

When a link is made, the exception is thrown directly, of course, the above test

Workaround:

First of all, if the situation occurs on the production server first take the Npoi mode upload does not affect the normal business, followed by the discovery of problem tracking after comparing the server configuration, unchanged compared to the win service determines whether due to the update caused some service exception, finally try to resolve.

Error Analysis:

　　

Exception Details: System.Data.OleDb.OleDbException: Unspecified error [OleDbException (0x80004005): Unspecified error] System.Data.OleDb.OleDbConnectionInternal. ctor (OLEDBConnectionString constr, OleDbConnection connection) +1131233System.Data.OleDb.OleDbConnectionFactory.CreateConnection (dbconnectionoptions options, Object Poolgroupproviderinfo, Dbconnectionpool Pool, DbConnection owningobject) + -System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection (DbConnection owningconnection, Dbconnectionpoolgroup Poolgroup) There are many solutions on the web, and the correct answer is this: when connecting to a database: Public StaticOleDbConnection Getxwdtconn () {stringConnectionString = webconfigurationmanager.connectionstrings["xwdtconnection"]. ConnectionString; OleDbConnection con=NewOleDbConnection (connectionstring);returncon;} There is no problem in MS SQL or access, and debugging is not a problem. It will appear as an error message after publishing. Because there must be oledbdatadapter, or datasets, in the operation of the database, and Con.open () and Con.close () are used. The specific solution is simply to delete the open and close, because the use of a disconnected connection. If you use static variables as a method

　　　　

The "Unspecified error" workaround rollup appears for the win server file upload download