Question Locked

OWA Troubles

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello,

I have taken over technological responsibilities at a new company. The previous tech admin installed Exchange Server 2003 on a SBS SP1 server. The process was never finished and was handed over to me to complete. I uninstalled the Exchange Server and started fresh because I had no idea where he left off at and he refused to help. I have ran into numerous problems since. The latest is that I cannot access OWA internally from the server Exchange is installed. I will get a pop up log on window and type in username and password only to get denied. I am using the admin account and have given full credentials for the Exchange server and Web Access. I have also read the OWA help guide here, but not much changed, but it was very informative. One thing that I do see is that my Exchange Virtual Server mailboxes for SMTP domain path is set to www.company-name.com, I have never put this in and is probably carry over from the old install. If this is the problem then I need direction on how to change it. I have added a new ExVS called companyname.local. I try to access the OWA by servername.companyname.local/exchange. I have tried so many things I could write a small book. Any and all suggestions would be much appreciated. If I need to give more info I will post back to save space here. Thank you in advance to all who reply.

9 replies

by absolutely

The previous employee is so (1) disgruntled (2) lazy (3 - ...) some other variety of 'unprofessional', that he has refused to assist in passing his responsibilities to his replacement. I would record configuration settings from clients that rely on this server, then reinstall from scratch rather than assume that this guy has done [b]anything[/b] right.

Sorry, no technological expertise in this case, but it sounds like you're better off doing it yourself than standing on the shoulders of that sort of midget.

by jaca_4

It has been an uphill struggle since day one on even the simplest issues for this server. I have explained to my employer that this server was fundamentally flawed in its creation and honestly needs rebuilt from the ground up. Unfortunately I was denied and now is not an option.

The guy before me is now on trial for doing the unethical things we as IT should never do so I am flying solo at this point, but have great people like yourself that help me from time to time. I do thank you for your input.

by cg it

not necessarily the best thing to do.. how did you uninstall exchange? did you use the Add/Remove programs? or did you rerun setup and choose to uninstall exchange? How did you reinstall exchange?

SBS has a different way of doing things so how you uninstalled exchange and then reinstalled exchange is significant in how exchange will function.

Which version of SBS? standard or premium?

hint: you use the setup SBS shortcut on the server desktop or if not there, you put CD1 in and run setup for any and all changes you make. you don't use add/remove programs. I would advise to insert CD1 and run setup choosing maintenance for all installed applications and for Exchange to uninstall it. Then rerun setup again to install exchange properly. Just follow the wizards and your exchange server should function properly. Note: you must include OWA during setup and then from the things to do list configure remote access.

by jaca_4

I uninstalled Exchange from the add/remove programs and I went through this links: http://www.msexchange.org/tutorials/Remove-Exchange-server-entire-Exchange-organization.html recommendations for the cleaning out the registry and other clean up processes. The SBS is the Premium edition. I will follow these instructions you have given. Being that the server in question is in a production environment it may be a couple days before I can finish it. As soon as I have completed this I will respond back, should be by Wed. Thank you very much.

by cg it

Small Business Server isn't like the standard server software. Exchange, ISA server, SQL server and Sharepoint server are all intergrated into SBS [the setup wizard [including using the "Things to do" wizards configures SBS for you. You can use add/remove programs but that tends to mess up the configuration that the wizard sets up.

Pop CD1 in. run the SBS setup program. follow the wizard instructions for installing/maintenance/uninstalling the options for SBS. If you installed Exchange any other way that using the SBS setup wizard, in the drop down menu for exchange and exchange components, choose uninstall. The rerun the setup wizard for exchange and let the wizard configure it for you.

Note: SBS premium edition comes with ISA server. If ISA server is installed, that's probably why OWA doesn't work. See isaserver.org for ISA questions. Note: again the SBS wizards will install ISA server automatically and configure it for SBS. Also not you MUST use 2 NIC configuation if you use ISA.

by jaca_4

I reinstalled Exchange from the CD. The first problem I had when doing this was the owalogin.asp file had to be renamed because the installation was halting and saying exchange was already installed. I also uninstalled Outlook from the server from Add/Remove. Then reinstalled Outlook from CD after Exchange to be able to troubleshoot any emailing issues.

Also I am in the beginning stages of this so all work is being done on the server I won't even begin with the clients until I get this in working order on the Server first.

by wesglbrt

Sorry to hear about your problems with SBS 2003. I also "inherited" my company's IT position from someone else. We were at the time using Windows Server 2000 and wanted me to upgrade to SBS 2003. I tried to do this via the upgrade method and was getting some of the same errors and problems that you are getting. After many long late nights of total frustration I finally just bit my lip, said a prayer and reformated my system drive and started over with a fresh install. It worked perfectly. Just an idea... hope this helps. Oh yeah, don't EVEN try to call Microsoft because they will just want to charge you 250 dollars for even talking to you on the phone.

by jaca_4

I will do this. Thank you so much. I am learning through things such as this that SBS is a different animal and needs to be handled differently than how I was taught and from what I know. Again thank you very much. And I will read the suggested link also.

This discussion is closed to new replies.