.NET Framework Developer Center >
.NET Development Forums
>
64-Bit .NET Framework Development.
>
Indexing services on window server 2008 is not working with .net
Indexing services on window server 2008 is not working with .net
Hi,
I am useing Microsoft indexing services in windows 2008 64 bit .I am getting error like "Exception from HRESULT: 0xC0000005" while i am createing new catlog from .net 2.0.
I am using "ciodm.dll" for adding new catlog.i am using this code for create new catelog.
Dim Admin As New CIODMLib.AdminIndexServer
Admin.AddCatalog(varContractNo, txtCatelog.Text +
"\" + varContractNo)
Admin.Stop()
Admin.Start()
AddScope(txtDocFolderPath.Text, txtSite.Text, txtCatelogname.Text)
Please help me anybody have fixed this issue on window server 2008 64 bit.
Answers
- Hi,
You may need to build with target plateform x64 or AnyCPU, if you still get same error after the change, you'd better contact the owner of that native dll to see whether there is any defects in the dll.
Thanks,
Eric
Please remember to mark helpful replies as answers and unmark them if they provide no help.- Marked As Answer bysanket shah81 Tuesday, October 27, 2009 5:13 AM
- Marked As Answer byeryangMSFT, ModeratorThursday, October 22, 2009 2:42 AM
- Unmarked As Answer bysanket shah81 Tuesday, October 27, 2009 5:13 AM
- Hello Friend ,
I have fixed the issue by enabled 32 bti application pool =false
Thanks
Sanket- Marked As Answer bysanket shah81 Tuesday, October 27, 2009 5:14 AM
All Replies
- Is your app running as 32-bit and calling a 64-bit Dll? Or the other way round?
Phil Wilson Hi
My development enviroment is 32 bit and my deployment server is 64 bit. is this problem. ?- Your development environment is not relevant. When your .NET app runs, do you know if it's running as native 64-bit or not? Is it building MSIL/AnyCpu code or x86 code? You have an interop Dll by the look of it - is that 64-bit? MSIL?
You should really be doing error checking. A likely cause of a crash on AddCatalog is that the object is null, meaning that you never actually created it, and that might be related to 32/64 bit COM Dlls.
Phil Wilson - Hi Wilson,
Thanks for your answer. i am build my application witch target x86 cpu.so i am thinking it should work..
but it still display same error.
Thanks
Sanket Shah - Hi,
You may need to build with target plateform x64 or AnyCPU, if you still get same error after the change, you'd better contact the owner of that native dll to see whether there is any defects in the dll.
Thanks,
Eric
Please remember to mark helpful replies as answers and unmark them if they provide no help.- Marked As Answer bysanket shah81 Tuesday, October 27, 2009 5:13 AM
- Marked As Answer byeryangMSFT, ModeratorThursday, October 22, 2009 2:42 AM
- Unmarked As Answer bysanket shah81 Tuesday, October 27, 2009 5:13 AM
- Hello Friend ,
I have fixed the issue by enabled 32 bti application pool =false
Thanks
Sanket- Marked As Answer bysanket shah81 Tuesday, October 27, 2009 5:14 AM


