| Author |
 Topic  |
|
|
alm007
Starting Member
6 Posts |
 Posted - 15 July 2002 : 12:59:05
|
I've used v.4.0 in russian. And have some problem:
Sometimes when someone is clicking link on forum site, for example a last post name, the cpu utilization goes up to 100% and the forum does not respond.
In this time task man shows the mtx.exe processe is very active.
In result i need to reboot the system to launch the forum.
I've used NT6a + rollup, IIS4
Could anyone help me to solve the problem?
=============
I've used:
- MS SQL 6.50.201
- MDAC 2.70.9001
- connection string strDBType = "sqlserver"
Thanks,
Alm007
Edited by - alm007 on 16 July 2002 09:11:17
===========================================
i've tried to reinstall MDAC/Jet Driver stuff (the latest version MDAC 2.70.9001.0), but it's not worked.
The problem remains the same :(
Please help!!!
Edited by - alm007 on 16 July 2002 10:20:32
[moved by bozden on 03 October 2002]
< |
Edited by - Deleted on 03 October 2002 20:25:13 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
|
HuwR
Forum Admin
United Kingdom
20593 Posts |
Posted - 15 July 2002 : 13:00:58
|
I have no idea what mtx.exe is , it is not a file normally related to website activity
< |
 |
|
|
dayve
Forum Moderator
USA
5820 Posts |
|
|
Deleted
deleted
4116 Posts |
Posted - 15 July 2002 : 15:47:04
|
That happened to me before. Try to reinstall the MDAC/Jet Driver stuff, latest versions (even if you have the latest).
This has nothing to do with v4 of course :)
Think Pink
==> Start Internationalization Here< |
|
|
|
alm007
Starting Member
6 Posts |
Posted - 16 July 2002 : 09:07:36
|
I've used:
- MS SQL 6.50.201
- MDAC 2.70.9001
- connection string strDBType = "sqlserver"
Thanks,
Alm007
[quote]
What database and connection string are you using?
< |
|
|
|
alm007
Starting Member
6 Posts |
Posted - 16 July 2002 : 10:16:53
|
i've tried to reinstall MDAC/Jet Driver stuff )the latest version MDAC 2.70.9001.0), but it's not worked. The problem remains the same :(
quote:
That happened to me before. Try to reinstall the MDAC/Jet Driver stuff, latest versions (even if you have the latest).
This has nothing to do with v4 of course :)
[
< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 16 July 2002 : 10:30:48
|
quote:
I've used:
- MS SQL 6.50.201
- MDAC 2.70.9001
- connection string strDBType = "sqlserver"
Thanks,
Alm007
This is not what I asked. I need to know the value for strConnString in config.asp.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs< |
|
|
|
alm007
Starting Member
6 Posts |
Posted - 16 July 2002 : 11:40:30
|
The value is
strConnString = "driver={SQL Server};server=SQL;uid=forum;pwd=password;database=forum" '## MS SQL Server 2000
quote:
This is not what I asked. I need to know the value for strConnString in config.asp.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs
< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 16 July 2002 : 11:49:59
|
Try replacing it to:
strConnString = "Provider=SQLOLEDB;Data Source=SQL;Initial Catalog=forum;User ID=forum;Password=password;"
Tell me if it works.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs< |
|
|
|
alm007
Starting Member
6 Posts |
Posted - 16 July 2002 : 12:16:56
|
it seems has worked!!!
i've tested forum in 15 min. No one crash!!!
Now all are OK.
i hope all'll OK in future 
Thank you very much!
================================
let me to know why it's helped to my forum?
Edited by - alm007 on 16 July 2002 12:22:31< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 16 July 2002 : 12:35:30
|
quote:
let me to know why it's helped to my forum?
Well, changing the connection string changed the type of database driver you are using. Previously you were using ODBC drivers, with this new connection string you are using OLEDB drivers. OLEDB drivers are faster and more robust, so they should be used whenever possible.
I've found that sometimes ODBC drivers cause this situation you were experiencing. I admit there is some kind of problem with some ODBC drivers that cause this problem. I've also found that using OLEDB drivers in those situations fixes the problem.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs< |
|
|
|
alm007
Starting Member
6 Posts |
Posted - 16 July 2002 : 12:50:41
|
Thank you
< |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
| |
Topic |
|
.