Unwanted reminders appearing

[Guest]

We are running a pilot with half a dozen users on Outlook 2007 BCM, and a
separate PC running SQL 2005 Express to host the database. Occasionally,
about once a week, one of the users will start Outlook, and their PC will
grind to a halt as BCM creates a reminder for every contact in the database.
All 3340 of them! Once Outlook has finished doing this, the users can
Dismiss All, and go for another coffee while they all disappear again. It
has happened to one user twice so far this week. I need a fix for this, or
the pilot won't be going any further.
Thanks

 

[Guest]

Gordon,
Thank you for using BCM 2007. It might be possible that the boot cache is
corrupted. One possible workaround you can try is to close outlook, make sure
the process died, and then delete the bootcahce file, then restrat outlook.
Let me know if this indeed fixed the issue.

In case the above steps doesn't fix the problem, it would be helpful if
you can turn on logging for BCM. Open the About BCM dialog from Help, and
select enable logging check box. That way we will be able to go through the
logs and figure out the problem.

Thanks,
Vamshi [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights

 

[Guest]

OK. That doesn't help at all, I'm afraid.
Deleting a file after this happens is not an acceptable workaround, it's
just a method of clearing up the mess afterwards. I've had a look at turning
on the logging, and it appears that you have to start Outlook before you can
enable logging. Having enabled it, if you close Outlook and start it again,
logging is disabled again. As this problem occurs when the user starts
Outlook, it's pretty clear that turning on logging after the event isn't
going to capture anything meaningful.
If you can give me a method of having logging enabled while Outlook starts,
I should be able to capture some useful data.
Thanks.

Gordon,
Thank you for using BCM 2007. It might be possible that the boot cache is
corrupted. One possible workaround you can try is to close outlook, make sure
the process died, and then delete the bootcahce file, then restrat outlook.
Let me know if this indeed fixed the issue.

In case the above steps doesn't fix the problem, it would be helpful if
you can turn on logging for BCM. Open the About BCM dialog from Help, and
select enable logging check box. That way we will be able to go through the
logs and figure out the problem.

Thanks,
Vamshi [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights

We are running a pilot with half a dozen users on Outlook 2007 BCM, and a
separate PC running SQL 2005 Express to host the database. Occasionally,
about once a week, one of the users will start Outlook, and their PC will
grind to a halt as BCM creates a reminder for every contact in the database.
All 3340 of them! Once Outlook has finished doing this, the users can
Dismiss All, and go for another coffee while they all disappear again. It
has happened to one user twice so far this week. I need a fix for this, or
the pilot won't be going any further.
Thanks

 

[Guest]

Gordon,
In order to have the logging turned on when you start outlook, set the
following registry key to 1, before starting outlook.

HKEY_CURRENT_USER\Software\Microsoft\Business Solutions eCRM\BCMLogging

This will be set back to 0 every time you close outlook. So set it back to
1, before you start outlook every time.

Please let me know if you were able to get anything from the logs.

Thanks,
Vamshi [MSFT]

 

[Guest]

OK, I'll do that. Where will I find the log files?

Gordon,
In order to have the logging turned on when you start outlook, set the
following registry key to 1, before starting outlook.

HKEY_CURRENT_USER\Software\Microsoft\Business Solutions eCRM\BCMLogging

This will be set back to 0 every time you close outlook. So set it back to
1, before you start outlook every time.

Please let me know if you were able to get anything from the logs.

Thanks,
Vamshi [MSFT]

OK. That doesn't help at all, I'm afraid.
Deleting a file after this happens is not an acceptable workaround, it's
just a method of clearing up the mess afterwards. I've had a look at turning
on the logging, and it appears that you have to start Outlook before you can
enable logging. Having enabled it, if you close Outlook and start it again,
logging is disabled again. As this problem occurs when the user starts
Outlook, it's pretty clear that turning on logging after the event isn't
going to capture anything meaningful.
If you can give me a method of having logging enabled while Outlook starts,
I should be able to capture some useful data.
Thanks.

 

[Luther]

OK, I'll do that. Where will I find the log files?

Gordon,
In order to have the logging turned on when you start outlook, set the
following registry key to 1, before starting outlook.

HKEY_CURRENT_USER\Software\Microsoft\Business Solutions eCRM\BCMLogging

This will be set back to 0 every time you close outlook. So set it back to
1, before you start outlook every time.

Please let me know if you were able to get anything from the logs.

Thanks,
Vamshi [MSFT]

"Gordon Brown" wrote:

- Show quoted text -

Most of the log files go to a folder like this:

C:\Documents and Settings\<user>\Local Settings\Application Data
\Microsoft\Business Contact Manager\Logs

 

[Guest]

Gordon,
Sorry for the delayed response. You can find BCM logs in the users local
settings folder. below is the path , where you need to look for logs.

C:\Documents and Settings\"user"\Local Settings\Application
Data\Microsoft\Business Contact Manager\Logs

Thanks,
Vamshi [MSFT]

OK, I'll do that. Where will I find the log files?

Gordon,
In order to have the logging turned on when you start outlook, set the
following registry key to 1, before starting outlook.

HKEY_CURRENT_USER\Software\Microsoft\Business Solutions eCRM\BCMLogging

This will be set back to 0 every time you close outlook. So set it back to
1, before you start outlook every time.

Please let me know if you were able to get anything from the logs.

Thanks,
Vamshi [MSFT]

OK. That doesn't help at all, I'm afraid.
Deleting a file after this happens is not an acceptable workaround, it's
just a method of clearing up the mess afterwards. I've had a look at turning
on the logging, and it appears that you have to start Outlook before you can
enable logging. Having enabled it, if you close Outlook and start it again,
logging is disabled again. As this problem occurs when the user starts
Outlook, it's pretty clear that turning on logging after the event isn't
going to capture anything meaningful.
If you can give me a method of having logging enabled while Outlook starts,
I should be able to capture some useful data.
Thanks.

 

[Guest]

Hi,

Since we turned on logging, the problem has only occurred once, so it seems
that even enabling logging goes some way to fixing the problem. Anyway, it
has now happened again, but there were no log files in the directory you gave
me. I have a copy of every files ending in .log from the PC at the time of
the prolem, and can e-mail them to you if you want. The user metioned that
some of the reminders that were being created looked like they were for
personal contacts, rather than BCM ones, so are we even looking at the
correct logs?
Look forward to hearing from you.
Gordon.

Gordon,
Sorry for the delayed response. You can find BCM logs in the users local
settings folder. below is the path , where you need to look for logs.

C:\Documents and Settings\"user"\Local Settings\Application
Data\Microsoft\Business Contact Manager\Logs

Thanks,
Vamshi [MSFT]

OK, I'll do that. Where will I find the log files?

Gordon,
In order to have the logging turned on when you start outlook, set the
following registry key to 1, before starting outlook.

HKEY_CURRENT_USER\Software\Microsoft\Business Solutions eCRM\BCMLogging

This will be set back to 0 every time you close outlook. So set it back to
1, before you start outlook every time.

Please let me know if you were able to get anything from the logs.

Thanks,
Vamshi [MSFT]


:

OK. That doesn't help at all, I'm afraid.
Deleting a file after this happens is not an acceptable workaround, it's
just a method of clearing up the mess afterwards. I've had a look at turning
on the logging, and it appears that you have to start Outlook before you can
enable logging. Having enabled it, if you close Outlook and start it again,
logging is disabled again. As this problem occurs when the user starts
Outlook, it's pretty clear that turning on logging after the event isn't
going to capture anything meaningful.
If you can give me a method of having logging enabled while Outlook starts,
I should be able to capture some useful data.
Thanks.

 

[Guest]

It's just hapened again. This is the first time that I have actually seen
it. Unfrtunately, BCM logging was not turned on, but Outlook logging was.
It happened at 11:50 this morning (03/07/07). I will e-mail you the logs.
Thanks
Gordon.

Gordon,
Sorry for the delayed response. You can find BCM logs in the users local
settings folder. below is the path , where you need to look for logs.

C:\Documents and Settings\"user"\Local Settings\Application
Data\Microsoft\Business Contact Manager\Logs

Thanks,
Vamshi [MSFT]

OK, I'll do that. Where will I find the log files?

Gordon,
In order to have the logging turned on when you start outlook, set the
following registry key to 1, before starting outlook.

HKEY_CURRENT_USER\Software\Microsoft\Business Solutions eCRM\BCMLogging

This will be set back to 0 every time you close outlook. So set it back to
1, before you start outlook every time.

Please let me know if you were able to get anything from the logs.

Thanks,
Vamshi [MSFT]


:

OK. That doesn't help at all, I'm afraid.
Deleting a file after this happens is not an acceptable workaround, it's
just a method of clearing up the mess afterwards. I've had a look at turning
on the logging, and it appears that you have to start Outlook before you can
enable logging. Having enabled it, if you close Outlook and start it again,
logging is disabled again. As this problem occurs when the user starts
Outlook, it's pretty clear that turning on logging after the event isn't
going to capture anything meaningful.
If you can give me a method of having logging enabled while Outlook starts,
I should be able to capture some useful data.
Thanks.

 

[Guest]

Gordon,
Please go ahead and send me the logs. If you can provide me your email
address, I will create a workspace for you where you can upload the log
files, for us to look at.

Thanks,
-Vamshi [MSFT]

It's just hapened again. This is the first time that I have actually seen
it. Unfrtunately, BCM logging was not turned on, but Outlook logging was.
It happened at 11:50 this morning (03/07/07). I will e-mail you the logs.
Thanks
Gordon.

Gordon,
Sorry for the delayed response. You can find BCM logs in the users local
settings folder. below is the path , where you need to look for logs.

C:\Documents and Settings\"user"\Local Settings\Application
Data\Microsoft\Business Contact Manager\Logs

Thanks,
Vamshi [MSFT]

OK, I'll do that. Where will I find the log files?

:

Gordon,
In order to have the logging turned on when you start outlook, set the
following registry key to 1, before starting outlook.

HKEY_CURRENT_USER\Software\Microsoft\Business Solutions eCRM\BCMLogging

This will be set back to 0 every time you close outlook. So set it back to
1, before you start outlook every time.

Please let me know if you were able to get anything from the logs.

Thanks,
Vamshi [MSFT]


:

OK. That doesn't help at all, I'm afraid.
Deleting a file after this happens is not an acceptable workaround, it's
just a method of clearing up the mess afterwards. I've had a look at turning
on the logging, and it appears that you have to start Outlook before you can
enable logging. Having enabled it, if you close Outlook and start it again,
logging is disabled again. As this problem occurs when the user starts
Outlook, it's pretty clear that turning on logging after the event isn't
going to capture anything meaningful.
If you can give me a method of having logging enabled while Outlook starts,
I should be able to capture some useful data.
Thanks.