Jump to content

Scowndrel

Members
  • Posts

    7
  • Joined

  • Last visited

Reputation

0 Neutral
  1. There is no such product as Small Business Server 2007. The customer's server is SBS 2008, which runs on Windows Server 2008, which is listed in the system requirements. Small Business Server 2011 runs on Server 2008 R2. SBS 2011 is not listed in the system requirements either. If the product does not work on SBS versions of Windows, that should be noted in the system requirements, since the OSes that SBS runs on ARE listed. This is a failure of proper documentation. The customer is not willing to undertake a $2000+ migration project to support a product whose purchase price for 8 users is only a couple hundred dollars. We will most likely just do a refund and look elsewhere for malwarebytes protection.
  2. Yes. I have run though a couple of things, tried an older version of the installer as requested by the support rep, and submitted a few batches of logs. But when they asked for a large list of logs from all over the system, I had to call it quits. The customer is not willing to pay even for the troubleshooting that I have already done, and I'm not going further down the rabbit hole on my dime to troubleshoot an installation that should have taken 15 minutes (and has, at other customer sites). I'm not willing to be an unpaid software tester for MBAM console development issues. We'll either run it unmanaged, or obtain a refund.
  3. Windows Updates and reboot completed. Problem still exists. Back to the drawing board, I guess.
  4. Thank you for the suggestions. I'll see if the client is willing to do a reboot at lunch today so I can apply the 39 updates that the server is waiting for. Some of them are for .Net Framework, so that might be relevant. Regarding the SQL connectivity, it is my understanding that TCP/IP and/or Named Pipes only needs to be enabled for other computers to access the database over the network; not for local applications installed on the same server to access it. For example if I wanted to install the mgmt console on a user's PC, I would need to enable those. I have not enabled those on other servers that I have successfully installed this product on. However, as a troubleshooting step based on your suggestion I did enable those, and restarted the services, and it did not solve the issue.
  5. I'm also looking at a failure to log into the admin console. Mine is a fresh install. I started a thread here: https://forums.malwarebytes.org/index.php?/topic/179461-blank-admin-password-not-working-during-initial-setup/, would very much appreciate someone PMing me that SQL script so I can eliminate that possibility.
  6. I also have this issue. I started my own thread here: https://forums.malwarebytes.org/index.php?/topic/179461-blank-admin-password-not-working-during-initial-setup/ And I also started a support incident. But the customer is waiting. I would very much appreciate learning that SQL script. Thank you for your time.
  7. When I try to log into the Management Console for the first time, it does not accept a blank Admin password. I am not sure whether this is a password issue, or whether the console did not finish installing correctly. Background: The server is Small Business Server 2007. When I first installed the product, it installed the IIS 7.5 Express and the SQL database. At the end of that portion of setup, it asked for a reboot. I chose the option to manually reboot later. I expected the setup to exit at that point, but it did not. It went on with the MBAM console setup, which errored out. I figured this error was due to the lack of reboot after the SQL component. Later in the day, I rebooted. After the reboot, I could not find an MBAM console icon. When I tried to run Setup again, it told me the product was already installed. Then I uninstalled the product (but not IIS 7.5 or the SQL instance). I chose a different port than last time. Then I re-ran setup. It skipped right past the IIS and SQL portions, did the database prep, and installed the console. When I double-click the Icon, I get the logon screen, with the Server Address and User Name pre-populated with 127.0.0.1 and Admin. When I click the Login button, it thinks about it for a couple of seconds, then I get an error: Login failed for user: Admin. I have tried running the "Server Configuration" utility to select new/open ports, which appeared to complete successfully but which had no effect on my login issue. The best I can figure is that something went wrong due to the aborted initial setup and uninstall/reinstall, and the routine where the blank password is accepted and then changed after the first logon has been bypassed. So I need instructions to reset the password, and/or ideas on what else might be wrong. Thank you for your time.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.