How to get rid of IIS?

  • Thread starter Thread starter nosecam
  • Start date Start date
N

nosecam

Hi,

I downloaded the XPProEmulation SP2 project and it's working quite well
for me. On of the problems I have is, that I always get during the FBA
"Unable to Access the configuration of Microsoft Personal Web Server".
I disabled everything (I think) which is related to IIS, but the message
remains. Any hints how to get rid of it?

Thanks
nosecam
 
Sounds like you're using a buggy macro component that includes a dependency
on that feature that was end of life'd. "Microsoft Personal Web Server" is
not IIS, MPWS is not accessible via Target Designer, that error you got is
expected.

The emulation macro component is not a Microsoft component, you may need to
remove the dependency from that component since MPWS is not visible in TD.
 
Andy said:
Sounds like you're using a buggy macro component that includes a dependency
on that feature that was end of life'd. "Microsoft Personal Web Server" is
not IIS, MPWS is not accessible via Target Designer, that error you got is
expected.

The emulation macro component is not a Microsoft component, you may need to
remove the dependency from that component since MPWS is not visible in TD.
Click to expand...

I don't think this is the case, since the message is issued on FBA
startup and not in design time
 
That's what i'm saying. The component is hidden from you as the developer,
you can't see it because it's vis 50 i think. But when TD builds the image
the feature is still added to the runtime.

We stopped supporting that feature and it's not been maintained for years,
so it throws an error during FBA when FBA tries to register it. I've repo'd
this by manually increasing the visibility to a higher level and adding it
to a config, it does error during FBA, the error is expected.

The fix is to modify the buggy macro component, PWS is not supported on XPe.
 
Andy said:
That's what i'm saying. The component is hidden from you as the developer,
you can't see it because it's vis 50 i think. But when TD builds the image
the feature is still added to the runtime.

We stopped supporting that feature and it's not been maintained for years,
so it throws an error during FBA when FBA tries to register it. I've repo'd
this by manually increasing the visibility to a higher level and adding it
to a config, it does error during FBA, the error is expected.

The fix is to modify the buggy macro component, PWS is not supported on XPe.
Click to expand...

Okay, I see.
How can I find the macro component with this dependecy?

Thanks again
 
Hi, the macro is the 'pro emulation' component you referred to at the
beginning. Open that in component designer and locate that PWS component
dependency in the components node and delete it. I have never seen this
macro component, but i can imagine it will take several minutes to enumerate
and display all the components in the list if there's hundreds of them. Good
luck.
 
Back
Top