Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: ASP.net error

  1. #11
    Join Date
    Oct 2005
    Posts
    745
    Rep Power
    0

    Default

    The actual problem is because of the Microsoft Indexing Services which scans the Temporary ASP.NET Files and while doing so, the system puts a lock on the same.

    To resolve this, the following steps need to be carried out:-

    1. Start - Settings - Control Panel - Administrative Tools - Computer mangement.

    2. Expand the services and applications node and select the Indexing service node.

    3. Expand the Indexing Service Node and then select and expand the System Node.

    4. Right click on Directories and select new directory. browse the path to the temporary asp.net files c:\winnt\microsoft.net\framework\v1.1.4322\.

    5. Select the temporary asp.net files. give ok and then select the "NO" in the Include in index radiobutton.

    6. give ok and then stop and start the indexing service.
    . .
    Last edited by recursion; Dec 10, 2007 at 04:51 PM.
    3.14159265358979323846264338327950288
    4197169399375105820974944592307816406
    28620899862803482534211706798 pi 101

  2. #12
    Join Date
    Jul 2006
    Posts
    276
    Rep Power
    0

    Default

    So will that solve the Object reference not set to an instance of an object error?
    The greatest discovery of all men through lifetime is that a man can alter his life by altering his attitude!

  3. #13
    Join Date
    Oct 2005
    Posts
    745
    Rep Power
    0

    Default

    Quote Originally Posted by norminator View Post
    So will that solve the Object reference not set to an instance of an object error?
    Not necessarily, that could be a totally unrelated problem.
    3.14159265358979323846264338327950288
    4197169399375105820974944592307816406
    28620899862803482534211706798 pi 101

  4. #14
    Join Date
    Jul 2006
    Posts
    276
    Rep Power
    0

    Default

    so what could be causing the object reference error?
    The greatest discovery of all men through lifetime is that a man can alter his life by altering his attitude!

  5. #15
    Join Date
    Dec 2004
    Posts
    159
    Rep Power
    0

    Default

    Try reinstalling the ASP.NET user on the local machine.
    1. Go to the command prompt
    2. Go to the 'C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322' folder
    3. Run 'aspnet_regiis -u' //this cmd uninstalls the asp.net
    4. Run 'aspnet_regiis -i' //this cmd reinstalls the asp.net
    5. Restart IIS from Computer Management

    You can try the application after this. tell me how it goes.
    live good today cause u will never know wat will happen 2marrow and it was never promised to no man either

  6. #16
    Join Date
    May 2003
    Posts
    108
    Rep Power
    0

    Default

    Check if the interop.mscomctllib.dll file is in the application BIN directory. If it is not, copy the fille there. The file may not be on the system that u r running the application on, and that is the reason u r getting the Object reference error.
    www.pixJM.com - View and upload photos/videos of what's currently happening in the streets of Jamaica.

  7. #17
    Join Date
    Oct 2005
    Posts
    745
    Rep Power
    0

    Default

    That error could be caused by many things so we might need to know what you're doing. If it's possible to attach a debugger to the process then you could try that. As I said the two problems could be completely unrelated so some code snippets might help your cause.
    3.14159265358979323846264338327950288
    4197169399375105820974944592307816406
    28620899862803482534211706798 pi 101

  8. #18
    Join Date
    Jul 2006
    Posts
    276
    Rep Power
    0

    Default

    Problem solved, What I had to do was to reinstall back the whole application. Then I got rid of that annoying error!
    The greatest discovery of all men through lifetime is that a man can alter his life by altering his attitude!

  9. #19
    Join Date
    Dec 2002
    Posts
    500
    Rep Power
    0

    Default

    im sorry to be so very late... whenever you have Interop.XXX in your bin directory, its usually ActiveX wrappers. The actual ActiveX controls need to be registered on the system using them (because thats how they are instantiated via COM), even if all the dlls are copied. usually the problem is solved by installation/re-installation because that registers the ActiveX controls from the dlls used.

    alternatively if you dont have the installer you can try the regdll.exe /i with the dll.

    that should help next time someone sees the object not set to an instance error... because of an unregistered COM dependency.
    Cultured in Aggression and Koding like a Warrior!!
    “Common sense is instinct. Enough of it is genius.” - George Bernard Shaw.
    "The significant problems we face cannot be solved by the same level of thinking that created them." - Albert Einstein

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •