-
Posted to
Classic ASP
by
jimbo_jnr
on
12-22-2008, 5:08 AM
Hi,
It appears that this is indeed the case. The Components seem to be only accessable when an administrator is logged into the server.
Unfortunately I have been asked not to make any further changes to the system until the new year so I cannot play around with the components identity settings or create a new user account.
I will update this ...
-
Posted to
Classic ASP
by
jimbo_jnr
on
12-18-2008, 10:33 AM
Hi Tom,
The Component is used for database connectivity and executing all of the applications
DB interaction. I do not know what is different about the other users except
that they are accessing the site from network computers and I am accessing
directly from the server whilst being logged in with an admin account.
This is a strange problem ...
-
Posted to
Classic ASP
by
jimbo_jnr
on
12-17-2008, 1:18 PM
Hello,
I have an IIS6.0, Classic ASP application that is having some difficulties as I do not understand about permission/access rights etc. I have created a COM+, Components Service Application from a dll. This component needs to be accessible to the IIS user.
How do I set this up? Does anyone know what the identity should be for the Component ...
-
Posted to
Classic ASP
by
jimbo_jnr
on
12-05-2008, 4:53 AM
I have found the solution.
Original Problem
Classic ASP dlls could not be registered under Com Serivces on Win2003 box. The only way to run the site is to register the dlls explicitly through regsvr32.
Effect
Thousands of SQL connections being created and not managed and w3wp.exe chewing memory until IIS or SQL Server 2005 ...
-
Posted to
Classic ASP
by
jimbo_jnr
on
12-03-2008, 11:44 AM
Thanks for you reply Andrew.
I have enquired and the hotfix mentioned is already in place. It seems that the chewing of memory by w3wp.exe is related to the fact that my application is creating thousands of connections to the sql 2005 DB and is not managing them properly.
As I cannot add the dlls used to Component Services I fear that the only ...
-
Posted to
Classic ASP
by
jimbo_jnr
on
11-28-2008, 7:55 AM
My problem is this:
The application creates thousands of connecitons to the database to the point that SQL server crashes. This did not happpen when the application was being managed by Com Services on the old box. Therefore I need to try to get the dlls into Component Services on the new box but I cant seem to get it working.
To alleviate ...
-
Posted to
Classic ASP
by
jimbo_jnr
on
11-27-2008, 4:37 AM
I can get the site to run by registering the 2 dlls through regsvr32 but I need component services to manage the connection pooling etc. so I unregistered them.
I then created an application manually in component services using one dll. I can see all the components so Im not sure if the dll is bad or the old component service application. Either ...
-
Posted to
Classic ASP
by
jimbo_jnr
on
11-26-2008, 1:36 PM
I am trying to get an asp application running on windows 2003 from windows 2000. The app compiles to 2 dlls which are registered as 2 applications through component services. I exported one application (msi) and created the application on the new box. The 2nd application would not export claiming it is damaged. I then created the application ...
-
Posted to
Classic ASP
by
jimbo_jnr
on
11-26-2008, 1:26 PM
This seems to be an old product and Im finding it difficult to get information about it! I will continue and updte the post when I have more information
-
Posted to
Classic ASP
by
jimbo_jnr
on
11-24-2008, 4:44 AM
Hi,
I have migrated an asp application from windows 2000 with SQL2000 to windows 2003 with SQL 2005. I needed to change the iis metabase values to allow uploading of large files and also to lengthen the asp script timeout value for the same.
My problem is when I upload a file the application will appear to hang. If I refresh the browser ...