Modem Connection Woes-Install of QW Deluxe 2000 causes Error 633 w/OL 2003

[Summer]

Hi,

Sorry, this is long...

Yes, I have Googled. Found posts from users with similar modem problems
after they installed Quicken but, cannot find the definitive answer to my
situation. Maybe I'm not using the best "key words".

After installing Quicken Deluxe 2000 into WinXP Pro SP2, it apparently
hijacked the modem away from Outlook 2003 (and probably *every* Windows
program that needs to use it). I can get online if I connect directly from
Control Panel, Network Connections, but when I try to Send/Receive as usual
from within Outlook I get an Error 633 stating that the modem is already in
use.

Looked in the Quicken folder and found an Outlook icon with the filename
QW.CFG. Properties state that this is an Outlook configuration file created
at the time of the Quicken installation. I removed it from the folder and
retried Send/Receive in Outlook. This time I received Error 623 - Cannot
load
dialog. Cannot find the phonebook entry for this connection. So I put the
file back.

Started Quicken and tried to find a way to tell it to let the modem go.
File, Disconnect did nothing. Not surprising as there is no *visible*
connection to begin with.

I tried deleting the dial-up connection in Control Panel, then recreating
it. Didn't work. I checked Send/Receive and Email settings in Outlook
looking for changes. None found.

I suspect this problem is related to the Windows Registry (where, no
doubt, I let Quicken make changes upon reboot after install - told Ad-Aware
to "allow" the change, not realizing the consequences.) :-(

Have done two system Restores and two reinstalls of Quicken (each time
having to call Intuit to get an "unlocking code"-Aargh! But Customer Service
was quite polite). I would rather not do this again if I can avoid it.
However, if there is *no* solution there will be no problem going back one
last time (restore point) and forgetting about installing Quicken.

I found no help in Quicken's Help file.

At the end of my patience...Does someone have a solution/suggestions on how
to get Quicken and Outlook/Windows to share the modem, or at least let
Outlook have
priority over it? Thank you for taking time to read this!

 

[Malke]

Hi,

Sorry, this is long...

Yes, I have Googled. Found posts from users with similar modem
problems after they installed Quicken but, cannot find the definitive
answer to my situation. Maybe I'm not using the best "key words".

After installing Quicken Deluxe 2000 into WinXP Pro SP2, it apparently
hijacked the modem away from Outlook 2003 (and probably *every*
Windows program that needs to use it). I can get online if I connect
directly from Control Panel, Network Connections, but when I try to
Send/Receive as usual from within Outlook I get an Error 633 stating
that the modem is already in use.

Looked in the Quicken folder and found an Outlook icon with the
filename QW.CFG. Properties state that this is an Outlook
configuration file created at the time of the Quicken installation. I
removed it from the folder and retried Send/Receive in Outlook. This
time I received Error 623 - Cannot load
dialog. Cannot find the phonebook entry for this connection. So I put
the file back.

Started Quicken and tried to find a way to tell it to let the modem
go. File, Disconnect did nothing. Not surprising as there is no
*visible* connection to begin with.

I tried deleting the dial-up connection in Control Panel, then
recreating it. Didn't work. I checked Send/Receive and Email settings
in Outlook looking for changes. None found.

I suspect this problem is related to the Windows Registry (where, no
doubt, I let Quicken make changes upon reboot after install - told
Ad-Aware
to "allow" the change, not realizing the consequences.) :-(

Have done two system Restores and two reinstalls of Quicken (each time
having to call Intuit to get an "unlocking code"-Aargh! But Customer
Service was quite polite). I would rather not do this again if I can
avoid it. However, if there is *no* solution there will be no problem
going back one last time (restore point) and forgetting about
installing Quicken.

I found no help in Quicken's Help file.

At the end of my patience...Does someone have a solution/suggestions
on how to get Quicken and Outlook/Windows to share the modem, or at
least let Outlook have
priority over it? Thank you for taking time to read this!

What did Quicken tech support say?

Malke

 

[Summer]

Well, don't know how I missed this and I'm not sure which settings change
worked but Outlook 2003 is now able to Send/Receive without errors. In Email
Accounts I found two settings had been altered by the installation of
Quicken: "My outgoing server (SMTP) requires authentication" box was
unchecked and under the Connection tab "Use the following Dial-Up networking
connection:" field was blank.

I also changed Quicken internet options to "not remain connected to
internet". Although, this was less likely the fix, as Quicken was never set
up to use the internet.

Also, WinXP Pro can now go into standby and I have NO idea how THAT became
fixed. All I changed were those two settings in Outlook and the one in
Quicken.

Just thought I'd let everybody know that I stumbled across the fix. Retraced
the troubleshooting steps I did before to see if I missed something and sure
enough, I did. Guess I wasn't as thorough as I thought. )
~Summer

 

[Summer]

Well, don't know how I missed this and I'm not sure which settings change
worked but Outlook 2003 is now able to Send/Receive without errors. In Email
Accounts I found two settings had been altered by the installation of
Quicken: "My outgoing server (SMTP) requires authentication" box was
unchecked and under the Connection tab "Use the following Dial-Up networking
connection:" field was blank.

I also changed Quicken internet options to "not remain connected to
internet". Although, this was less likely the fix, as Quicken was never set
up to use the internet.

Also, WinXP Pro can now go into standby and I have NO idea how THAT became
fixed. All I changed were those two settings in Outlook and the one in
Quicken.

Just thought I'd let everybody know that I stumbled across the fix. Retraced
the troubleshooting steps I did before to see if I missed something and sure
enough, I did. Guess I wasn't as thorough as I thought. )
~Summer