This is just a collection of things I find out. Maybe they'll be indexed on google or something and save somebody else great headaches.
W2K server hangs on "Applying Personal Settings" - anyone know what to do? It seems that it will eventually logon - we are talking in the order of HOURS - leave it overnight and go home.
Turn of auto scaling in the chart areas. There's a problem with the number of fonts that Excel can handle - see MSKB Q168650 . Auto Scaling means that each chart takes two fonts of Excel's maximum of 256 fonts.
Native mode AD domain is better - but does this mean that a win98 workstation cannot logon to a Native Mode AD domain WITHOUT the AD client? (In other words, when we move to native mode, we loose interoperability with NT4 BDC's, but what about NT4 workstation without AD client? Win98 without AD client? I presume we interoperate with NT4 with AD client and Win98 with AD client.)
Win98 AD Client DFS: Does this exihibit site affinity? It certainly doesn't look like it does from emperical testing. (Appears to connect to any old DFS replica; whereas W2K Pro connects to a DFS replica in the same AD Site)
If anyone knows, please tell me. I would like to know.
How is browsing supposed to go? Is it? Are we supposed to manually add every shared folder to the AD tree? Shared folders in the AD tree seem, well, good idea but lacking sorely in follow-through. Why can't I directly use them as if they were transparent?
This newsgroup message got it working for me. Obiviously, YMMV, but what the heck. This isn't good enough for my production work - I can't rely on windowsian authentication working across the many and varied connections and what not; although in theory I should be able to. But that doesn't matter as loosing debugger capabilities on the production server in exchange for anonymous access is worth it - debugger capabilities on the production server are unlikely to be used anyways.
| Viewing message <1474201c0d320$5e2d86b0$19ef2ecf@tkmsftngxa01> |
|
Subject: Debugging VB components of SOAP 2 Gold services Newsgroups: microsoft.public.xml.soapsdk
|
I'm having problems debugging VB components of a web service; I get "WSDLOperation: Instantiating the dispatch object for method ~ failed", where ~ is the name of one of my methods. If the component is not being debugged, ie VB is not running the project, it works perfectly!
What do I need to do to enable debugging?
This seems a major problem if it is a limitation of the current toolkit...
Thanks,
Rupert Martin.
Solved it!
By default, the IIS virtual directory had anonymous access allowed, hence all requests to my service were under that account, and that didn't have access rights to connect to VB to debug. To enable debugging, use Windows Authentication only on the virtual directory.
Rupert.
Check that there is a protocol rule allowing HTTP traffic. I know it seems wierd - why on earth would it need to allow HTTP traffic as it's acting as an application level proxy. But trust me, stick it in and see if that helps. Odd, I know. Blame MS for trying to make it "easy" to understand. So, stick in both the "Protocol rules" (allow HTTP) and the "Site and Content Rules" (allow the specific HTTP content you want.) You'd figure you'd only need the latter, but try it and see if you don't believe me.