Search results for query: *

This problem started for me about 3 weeks ago, but I THINK it's been fixed (it's been 72 hours now without a shutdown). I re-applied W2K SP4, then I re-applied Exchange SP3. Windows update didn't figure out that I needed to re-apply all the patches I've installed since then, so I used the demo...

Some things to try/check: - is your com+ package set to be a server or library process? (activation tab); in most cases you should use server so that it runs in a dedicated process as opposed to library which runs it within the creators process - do all your public middle tier methods dispose...

Have you upgraded your app to use the COM+ Admin Type library instead of the MTS object model? CreateInstance is no longer required in COM+ (you can use createobject and if it is a com+ object it will still be enlisted in the same transaction). Something to try anyways. Good luck!

I've had a large COM+ application in production for years now, and have been using COM+ security at the component level without incident. New requirements have raised the need for a more granular security matrix, so we have moved to method level security. The security itself works great...

Hi again. This is bizarre but true, and we've verified it. If you run the Crystal 8.0 install with Typical selected (instead of complete/custom), none of the crystal objects work properly until you reinstall the SAME installation again. We've done this on clean W2K Server boxes 3 times now...

Hi again. I looked at the doc you sent; those are access/jet DLL's that the article mentions, so I dont think theyll help us (its a SQL Server database we're connecting to) - unless I'm misunderstanding something which is also entirely possible.

I'll read through the article right away but thought I'd respond to your other question: yes we did install crystal on the web server and the report runs fine in the crystal environment. I noticed the ref to the p2sodbc.dll in the method call, but that dll does not exist in our dev environment...

Hi again. In reading through Crystal's documentation, they don't recommend using RDC over the web and instead recommend the Report Application Server (which requires a rather large licensing fee) so I don't think that's going to work as a solution.

Hi there. Thanks for the reply! The ODBC connection is fine; our web application uses the same one to access the database and it works fine. When running the report in the crystal environment we use the same ODBC connection there as well and it's also fine. We can look at moving to the RDC...

In our dev environment (W2K, Crystal 8.0) our .asp code works fine. In the production environment (W2K, Crystal 8.0) we get the error "Incorrect Log On Parameters" when calling the LogOnServer method of the Crystal Application object. We have also tried using the SetLogonInfo method...