Fail creating virtual directory

Error: Creation of the virtual directory http://localhost/web failed with error: Could not find the server 'http://localhost' on the local machine. Creating a virtual directory is only supported on the local IIS server.

This error appear as a dialog box when trying to load a project whose virtual directory had been created formerly.

Actually, there are two dialog box:
1. The first dialog box sounds: The local IIS URL http://localhost for Web project web has not been configured. In order to open this project the directory needs to be configured. Would you like to create the virtual directory now?

2. After clicking yes, the second dialog box appears: Creation of the virtual directory http://localhost/web failed with error: Could not find the server 'http://localhost' on the local machine. Creating a virtual directory is only supported on the local IIS server.


Solution:
The solutions may vary in this case. Here are some possible solutions:
1. Make sure the asp.net is already registered to the IIS. You may want to try registering it to IIS

2. The virtual directory of the project might not have been set properly, so it can not be loaded. Edit the virtual directory of the project by right-clicking the project, choose Edit project (.csproj) file, then at the bottom part of the file, you may find something like <iisurl>http://localhost/</iisurl>
Change / add the name of the web project, e.g. <iisurl>http://localhost/webname</iisurl>

3. Make sure the IIS is running well on services.msc. To check it, press windows + Run, type "Services.msc" (without quotes), then restart IIS Admin.



Afterwards, restart the IIS by pressing windows + Run, type "inetmgr" (without quotes), then start the service.



4. This is a rare case, but someones might encounter it too. If you are using another web server on your computer, e.g. Apache, xampp, etc., make sure you stop the web server first, then start the IIS. In a case I met, it still didn't work, after about half an hour trying to find the problem, I found the issue. Someone changed the port used for the web server. So, I had to change it again.
On the IIS window, right click on the Default Web Site, choose Properties, then make sure the port used is 80 (I'm not sure if using another port is ok here).

Read More

Login fail for Sql User

Error: server: msg 18452, level 16, state 1 [microsoft][odbc sql server driver][sql server]login failed for user 'user_name'. Reason: not associated with a trusted sql server connection

Solution: Open Sql Server Enterprise Manager, go to SQL Server Group -> Choose the server -> right-click, Properties -> choose tab Security -> Choose Sql Server and Windows for Authentication, then click OK, and don't forget to restart the service to make sure the new settings work.

Read More

Awards from friend

I've just noticed the way to put awards from friends... hahaha.. lol
Awards from Ria Adria ^^

Read More

Unable to start debugging on the web server

Error : Error while trying to run project: Unable to start debugging on the web server. Server side-error occurred on sending debug HTTP request.

Make sure the server is operating correctly. Verify there are no syntax errors in web.config by doing a Debug.Start without Debugging. You may also want to refer to refer to the ASP.NET and ATL Server debugging topic in the online documentation.

This error appears as a dialog box while trying to debug a web application.

Solution : Run the application without debugging. You can :
1. Use Ctrl + F5, not F5, or
2. Directly type the URL address on the browser, or
3. Open IIS by pressing window + R, then type inetmgr, expand the web application under development, and browse it

You'll see the source of the error.

In a case I met, it's because of the unavailability of an impersonate user on the computer, while in the web.config, an impersonate user is used.

In case you meet the same condition; and in the web.config, there exists such code as:

<identity impersonate="true" username="uploaduser" password="uploaduser">

Go to Computer Management by pressing Window + R, then type "compmgmt.msc" (without quotes) -> Expand Local Users and Groups -> Users. If the user : uploaduser defined in web.config does not exist there, make the user by right-clicking, New User -> fill the user's information. Otherwise, if the user already exists, make sure that the account is not disabled. Just enable it by going to the properties if it is currently disabled.

Read More

Making table of contents in ms. word 2007

There are times when we need to make table of contents after making an article. It would be quite troublesome to make it manually if the article is long enough. Fortunately, if you're writing it in ms. office, there has been a functionality provided for it.

Here is a video about how to make table of contents using ms. word 2007. It should be more or less the same using earlier or later version of ms. word ^^

Read More

Retrieving Tables and Columns in a Database

This is how to retrieve tables & columns in the table from a database:

Dim rs As ADODB.Recordset
Set rs = New ADODB.Recordset
Set rs = con.OpenSchema(adSchemaColumns)

While Not rs.EOF
    Text1.Text = Text1.Text & rs!Table_Name & " - " & rs!COLUMN_NAME & vbCrLf
    rs.MoveNext
Wend

Read More

Retrieving Tables in a Database

This is how to retrieve all tables in a database:
Object needed:
A Textbox named Text1

Dim rs As ADODB.Recordset
Set rs = New ADODB.Recordset
Set rs = con.OpenSchema(adSchemaTables)
While Not rs.EOF
   If rs!Table_Type = "TABLE" Then Text1.Text = Text1.Text & rs!TABLE_NAME & vbCrLf
   rs.MoveNext
Wend

Read More

How to get column names of a table

This is how to retrieve column / field names of a table from VB using adodb connection:

con.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\database.mdb;Persist Security Info=False"

Set rs = New ADODB.Recordset
sql = "select * from table_name"
Set rs = con.Execute(sql)

Dim i As Integer
For i = 0 To rs.Fields.Count - 1
    MsgBox rs.Fields(i).Name
Next

Read More

CustomError mode

Error :

Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customerrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

Solution : The exact error hidden in this error message may vary. To reveal and see the error, changing the customErrors mode is necessary.
In web.config, change to mode to RemoteOnly or Off.
Changing the mode to RemoteOnly will enable the error message to be displayed when the web is viewed on the server.
Meanwhile, changing the mode to Off will enable the error message to be displayed when the web is viewed either on the server of outside.

<customErrors mode="Off" defaultRedirect="ErrorPage.aspx">
 <error statusCode="404" redirect="ErrorPage.aspx?errNo=404"/>
</customErrors>

Read More

Error detected by database DLL

Error : Error detected by database DLL

This error occurs when trying to open report produced using Crystal Report in application, one of which is application developed using VB.

Solution :
1. If you are using ODBC, make sure the ODBC has been created.

Here are the steps to create ODBC for the connection to the database, press Window + Run, then type "ODBCAD32" (without quotes). Then, on the User DSN tab, press Add.

A dialog box will be shown:

Click the Add button and choose SQL Server.

Insert the name of the database and server.

Next, if you're using SQL Server authentication, insert the login ID and password; otherwise, choose Windows Authentication.

2. If you've created the ODBC in User DSN tab, and still get the error, try doing step 1 again for the System DSN tab while creating the ODBC.

3. If still, it does not work, check the query used in your report, and make sure the stored procedure used in the report (in case you are using stored procedure) has been granted for the application itself. This is sometimes forgotten by developer ^^
To grant the stored procedure to the database user used in the application:
grant exec on spr_spname to database_user_name

Read More

Adding web reference in Visual Studio 2008 or later

Some people get confused adding web reference in Visual Studio 2008 or later, since it's not by default in the Solution explorer. Only Service reference is shown.

Web reference is actually still available on Visual Studio 2008 or later.
Just right-click on the project where the web reference is to be added, choose Add Service Reference, then click Advanced button. Click Add Web Reference beneath, then insert the URL address of the web service, Go. If the URL address is correct, it will be shown in the listbox saying "Web services found at this URL". Insert the reference name, then click Add Reference, OK.

That's all folks ^^

Read More