ASP runtime error, Microsoft OLE DB Provider for ODBC Drivers error code 0x80040E14 Unable to implem

ssql, adcmdtext prompts that this sentence is wrong, this syntax is wrong, how can it be written like this.

This sentence, adcmdtext is something. The context is not explained.

By feeling, the correct usage should be like this:

ssqlssql is a variable of the SQL statement to be executed.

In addition, the usage of this connection,How to use the local address directly?,You can't use the connection like this.。

Don't be lazy, write ** like this, it's definitely not easy to find the reason for the error.

You try it. If there is still an error in this way, it is not a problem with the data format.

It may be a problem with the permissions of the Windows temp directory of the system disk, and some temporary files will be generated in this directory when ASP is running, and if there is no relevant access permission, it will be wrong.

You give the temp directory user user and try with writable permissions.

In the same way, do you check if the directory where your database is located has writable permissions? Is there any permission to update scripts in IIS?

You carefully check your SQL statement. You use it first"ssql"), count the ssql statements. You'll know what's wrong. Wherever there is a problem, it can be solved in this way.

'Enable buffering.

on error resume next

dim conn,dbstr,html_titledim sqldatabase,sql_pass_word,sql_user_id,sql_data_source

sqldatabase="The name of the database"

sql_pass_word="Password"

sql_user_id="Accounts"

sql_data_source=""

set conn = "")

dbstr doesn't specify your connection driver, change this again!

Microsoft OLE DB Provider for ODBC drivers error'80004005'[Microsoft][ODBC", the cause of this issue: Some Dynamic Link Library files are not registered correctly (.).dll file).

The solution and operation steps are as follows:

1. First of all, press the keyboard "win+r" to punch in the "run" window, as shown in the figure below.

2. Secondly, enter the "cmd" command in the input box and press enter to confirm, as shown in the following figure.

3. Then, pop up the "Command Runner" window, enter the command "regsvr32" in turn, and press enter each command you enter, as shown in the following figure.

4. Finally, the following dialog box pops up, indicating that the problem has been solved, as shown in the figure below.

Solution:1Check that you have enough disk space left, and if there is no disk space left, clean up the disk to make space.

2.Check your disk partition format: if it's FAT16, the data file can only be up to 2G, if it's FAT32, the data file can only be up to 4G, and if it's NTFS partition, there is no such limitation.

3.Check that you have no limit on the size of the database file

Enterprise Manager -- Right-click on your database -- Properties -- File Growth Limit -- If there is a limit on the size of the change, remove the limit.

4.Check your SQL version, if you use MSDE, the maximum data file size is 2G.

5.You can also add a new data file to the primary group to solve this problem.

alter database add file(name = logical file name, filename = c: actual file name. ndf'。

In fact, the database is selected through Enterprise Manager"attributes">> State volt database file is more convenient. With the addition of an NDF, the problem is solved!

It is a problem with the SQL Server database. It is recommended that you find a professional to solve the problem. I can't tell for a moment.