There is no component upload issue in ASP

What does it mean if the upload is unsuccessful? Send the error **, usually a permission or path problem.

It may be caused by the IWAM password not being synchronized. IWAM is a built-in that is automatically established by the system when IIS is installed. After IWAM is established, it is used by Active Directory, IIS Metabase database and COM+ application, and the password is saved by the three parties, and the operating system is responsible for the synchronization of the IWAM passwords saved by the three parties.

The system sometimes fails to synchronize the passwords of IWAM, resulting in inconsistent passwords used by IWAM.

Solution: Open computer management first, local users and groups - change the password at the beginning of iwam to test

Start -> run cmd-> a black window appears.

In the black window:

cd c:\inetpub\adminscripts

adsutil set w3svc/wamuserpass "test"Password synchronization of IIS Metabase database passwords.

v Synchronize iWAM passwords in the COM+ app.

The result is as follows:

c:\documents and settings\administrator>cd c:\inetpub\adminscripts

c:\inetpub\adminscripts>adsutil set w3svc/wamuserpass "test"

wamuserpass : string) "***"

c:\inetpub\adminscripts> -v

w3svc, 0,root, 2,iis, 2,wj, 2,asp, 2,test, 2,out of process applications defined:

count: 1

3d14228d-fbe1-11d0-995d-00c04fd919c1}

c:\inetpub\adminscripts>

Pay attention to whether the name attribute of the form item uploaded by your frontend is the same as the name of the form item you received in the backend, if it is not always correct.

strfilename

request("file")

Get the address value of the file submitted on the previous page.

Press your **.

Let's see if the name file is the name of the form field you upload in the foreground.

Analyze the reasons first.

You have this error because you don't understand how it works. As with server languages such as php, jsp, asp, etc., they are all designed to generate pages that can be parsed by the browser, and the only language that can be parsed by the browser is html.

1. If you insert an asp:linkbutton into an aspx page, then after running the page, look at the source in the browser** and you will see that the tag is actually converted to a tag.

2. Why doesn't your writing be transformed? This is because the value that is passed to in the first place is output directly to the browser as a string in . Then your writing to the browser back source ** is still an asp:

linkbutton tag, which cannot be parsed correctly by the browser.

Solution: Knowing the reason, then if you have to write it the way you write it, then it should be like this:

" + users)session["users"])."

Modification of cancellation information.

But when you finish modifying it, you find that clicking the log button still can't be executed! Why?

This is because your linkbutton1 click1 event is not parsed in as a browser-recognizable js**.

How to fix it? Write an asp:linkbutton button in an aspx page

Log out of the run page, check the source** See what html** this newly added logout button is parsed to**, which is roughly as follows.

Set the newly added linkbutton to an invisible property.

Log out Re-edit the backend**.

" + users)session["users"])."

Modification of cancellation information.

This is to bind the tag's js event to the hidden logout button event.

Hope it helps.