I have written a DDL that utilizes an OCX for zipping and unzipping ZIP files. I have accessed this DLL through another VB project (for testing) and it's working great. But when I try to access it through ASP it's not returning the correct value. I can access other functions through ASP just fine, but the method that accesses the OCX that should return a 1 (does when going through VB), returns a 0 through ASP!?
What could I be doing wrong? If you want I can provide some code, just tell me what you'd like to see.
actually I'm using IIS on my own machine for testing. So through VB and ASP they are both accessing the exact same DLL in the exact same place. Is there something more I have to do through IIS to get this to recognize it through my ASP page? If so, any info would be great. Thanks!
It could be security issue for your browser. Go to Tools >Internet Options....>'Security' tab select Intranet and click on Custom level button. Enable everything for 'ActiveX controls and Plug-ins'
sorry andreys, it wasn't the browser. I'm positive it's something with IIS but I don't know what to do. I've been at this same damn problem for 2 days now. I'm at the point here where I literally want to punch a ****in' hole through my monitor. Sure, maybe I'll die from electricution but at least I won't have to worry about **** anymore. Has anyone ever done this? Am I just an idiot? Back to banging my head, hopefully someone will come to the rescue.
Could it be a File Permissions issue? VB runs as you, but IIS/ASP runs as IUSR_ComputerName by default.
Josh
Get these: MozillaOperaOpenBSD
I have books for sale: "MCSD in a Nutshell" and "VB Distributed Exam Cram" - PM me for details. Will also trade for a decent ATX Pentium 2 MB/CPU/RAM combo.
Just to update you on what I've discovered. I've moved the zip files I was tring to process from a subfolder under my IIS home directly to the home folder and ran it and everything works fine! Now why can't I access the subfolders through IIS? Everything should be setup to cascade rights down through filters. I havn't worked with IIS much but it looks like I have everything correct.
Ok, I tryed to put dll and ocx on my PC and run on IIS- nothing happend. I got "cannot display page" message.
Then I put dll and ocx (registred it of course) on my intranet server at work and tryed to run test.asp page - Same result NONE.
And I think your problem with your dll. As I know in a DLL projects you not supost to use OCXs. You cannot run OCX on server side, it should be done on client site. But before it could be run on clients side your OCX component must be installed on client machine. So user will get message with the prompt to load and run OCX from www.anyname.com site.
Your DLL uses OCX and this stops that dll to run on the server.
The DLL files run on the server side, but your DLL uses OCX, which could not be run on the IIS.
First of all, thanks to andreys who took the time to run my project and try and figure out what was going on.
I figured out what my problem was......NOTHING! (well sort of). I (for some desperate reason) copied a different ZIP file to that folder I was processing in and whala! It worked? I was like ***? Eventually I figured out that if you COPY the files to the IIS subfolder it finds them no problem. If you MOVE them it doesn't? Does anyone know why this works this way? This little fluke cost me 2 days work and I'm pissed. I'd like to know why this is for future reference.
Yeah, it works, but like I said, only if the files are COPIED to the subfolder in your IIS home directory. It loads pretty fast. It churns through about 50 zip files in a second or 2, and it also collects file names, file dates, and file sizes. I can finally start coding something new now! Thanks for all your help.
DLL works through VB, not through ASP?
Reply With Quote
