IIS problem with SQL Reporting on SBS2k3 with BCM, MOA, and Mobile

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Give me a moment and you'll understand why am posting this in so many areas;
please read before telling me wrong board.

I have installed BCM2k7 and MOA2k7 on my SBS 2003 R2 Premium box with SQL
2005 . Everything is working with regard to this as far as I can tell. I have
also installed the "Messaging and Security Feature Pack (MSFP)" to enable
the remote wipe of Mobile 5.

Here's the problem: when I went to test the remote wipe I found that it had
installed into a second "Default Web Site" along with a something from Office
Accounting. So normally I would just wipe the bad Default Web Site and
reinstall the MSFP into the correct web site. But now this bad Default Web
Site has MobileAdmin, Reports$MSOACCOUNTING, and ReportServer$MSOACCOUNTING.

So here's the question: If I remove the Reports$.... and the
ReportServer$...., will I break anything in BCM or Office Accounting? Should
I do something else?

Thanx, David.
 
Give me a moment and you'll understand why am posting this in so many areas;
please read before telling me wrong board.

I have installed BCM2k7 and MOA2k7 on my SBS 2003 R2 Premium box with SQL
2005 . Everything is working with regard to this as far as I can tell. I have
also installed the "Messaging and Security Feature Pack (MSFP)" to enable
the remote wipe of Mobile 5.

Here's the problem: when I went to test the remote wipe I found that it had
installed into a second "Default Web Site" along with a something from Office
Accounting. So normally I would just wipe the bad Default Web Site and
reinstall the MSFP into the correct web site. But now this bad Default Web
Site has MobileAdmin, Reports$MSOACCOUNTING, and ReportServer$MSOACCOUNTING.

So here's the question: If I remove the Reports$.... and the
ReportServer$...., will I break anything in BCM or Office Accounting? Should
I do something else?

Thanx, David.
Click to expand...

I haven't run across any connection between BCM and IIS since BCM v1,
and that was indirectly caused by a "feature" in Crystal Reports.
 
Back
Top