Error Messages while setting up the database script!

Q1: I am trying to set up the database using your db manager (not SQL Query Analyzer). However, I am getting this error:

Executing Script. Please wait... 0% complete


--------------------------------------------------------------------------------


Request object error 'ASP 0104 : 80004005'

Operation not Allowed

/db manager/db_functions.asp, line 212

A1: This error is caused by the default metabase.xml setting on your server. Windows 2003 (IIS 6) users might or might not have this issue.

Reason for this problem:

The new default metabase.xml set a restriction on maximum bytes an ASP script (the Request object) can receive. The default restriction is about 200 KB, and our full installation database script is more than 300 KB (upgrade script is a lot smaller) -> which is way beyond the default limit.

Workaround:

There are three workarounds:

1. if you are using a dedicated server do this (virtual server users can ask your ISPs to do it too):
   

   (thanks to Ittech who showed me this workaround):
   
   Here's the code from the metabase.xml, which you can edit and it applies changes in realtime. Never restarted the forum/site :)
   
   Gotta look under the header <IIsWebService Location ="/LM/W3SVC"
   
   or for whatever service location site name you are using...
   
   Change
   AspMaxRequestEntityAllowed="204800"
   to
   AspMaxRequestEntityAllowed="10238976"
   
   Just by coincidence i guess MS and you decided 200k is a good default limit

2. If you have SQL Query Analyzer, use it instead of our database manager.
3. Using dbmanager:
   • open the full installation SQL script
   • copy & paste portion of the SQL code (make sure the portion you copy ends at the “GO” keyword), and paste it into the window (instead of using upload) in the dbmanager, and then execute
   • erase the code in the dbmanager window, and then copy & paste the next portion of the SQL code
   • repeat this process until the all codes in full installation SQL script are executed against the database.

NOTE:

If you or your ISP cannot edit the metabase (as seen in workaround 1), then you won't be able to upload files that are larger than 200KB as file attachments.

---

Q2: I get tons of error messages when I try to run the install script in the SQL query analyzer (which I was able to get from a friend). Here is the list of them all:

Server: Msg 156, Level 15, State 1, Line 17
Incorrect syntax near the keyword ' DESC' .
Server: Msg 156, Level 15, State 1, Line 8
Incorrect syntax near the keyword ' ON' .
Server: Msg 156, Level 15, State 1, Line 8
Incorrect syntax near the keyword ' ON' .
Server: Msg 156, Level 15, State 1, Line 8
Incorrect syntax near the keyword ' ON' .
Server: Msg 156, Level 15, State 1, Line 8
Incorrect syntax near the keyword ' ON' .
Server: Msg 156, Level 15, State 1, Line 8
Incorrect syntax near the keyword ' ON' .
Server: Msg 156, Level 15, State 1, Line 8
Incorrect syntax near the keyword ' ON' .
Server: Msg 156, Level 15, State 1, Line 8
Incorrect syntax near the keyword ' ON' .
Server: Msg 156, Level 15, State 1, Line 8
Incorrect syntax near the keyword ' ON' .
Server: Msg 156, Level 15, State 1, Line 8
Incorrect syntax near the keyword ' ON' .
Server: Msg 156, Level 15, State 1, Line 8
Incorrect syntax near the keyword ' ON' .
Server: Msg 156, Level 15, State 1, Procedure spDisMsgM4_21, Line 35
Incorrect syntax near the keyword ' table' .
Server: Msg 170, Level 15, State 1, Procedure spDisMsgM4_21, Line 42
Line 42: Incorrect syntax near ' @sortTable' .
Server: Msg 170, Level 15, State 1, Procedure spDisMsgM4_21, Line 47
Line 47: Incorrect syntax near ' @sortTable' .
Server: Msg 170, Level 15, State 1, Procedure spDisMsgM4_21, Line 49

error message truncated

A2: This is not a problem of the software. It happened because you attempted to install the database on a SQL 7 server database.

Run the query using SQL Query Analyzer to see the version of the SQL server you have:SELECT @@Version

---

Q3: I got this message when I tried logging in through the database manager application:

"Login failed or database does not exist"

A3: This tells you that the SQL server cannot be accessed by the login/pass/db name/IP address you provide.

Usually when the error message shows up immediately after you hit login, it tells you that

1. you did not provide a valid combination of login/password - double check what you type, or
2. your login/password is not permitted to access the database you specified - set the correct permission for your database via Enterprise Manager, or
3. your SQL server is not set up to take SQL authentication - use Integrated Security instead without providing login/pass, or
4. you used Integrated Security, but the user account ASP runs on (usually the IUSR_machineName account) is not permitted in the SQL server to access the database - add the IUSR account to the "Login" section of your database via Enterprise Manager. If your SQL server is on a different machine and you still want to use Integrated Security, you must not use the IUSR_machinename account for ASP as it is a local account - use a domain or mirrored account.

If the error message shows up after a long time (longer than 15 seconds), it means that the SQL Server cannot be found on the network. Usually it indicates:

1. you provided a wrong SQL IP address or host name - double check, or
2. your network is blocked by a firewall - check with your network admin, or
3. your SQL server is not set to allow TCP/IP connection - use named pipe of your SQL server in the Server IP and Port textbox instead

You will need to figure out the problem yourself, and usually your best bet is to ask someone that is in charge of configuring the network/SQL server for you - usually your host or network admin.