[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 236
  • Last Modified:

Why is my outlook rule not firing on my 2nd machine?

Greetings experts!

I have 2 machines, 1 office 2007one office 2003.  Yesterday I created a rule that fired on both machins when a message was received.  
The rule was pointing to an excel file on a network share and life was good for the mostpart.  Early in the morning, the network shares are sometimes alseep and need to be kicked.  If this happens, the outlook rule will fire, but it can possibly never run if it cannt see the excel file.

I modified the rule today, pointing the rule to a local c:\automation directory that contans a batch file that wakes the shares then calls the excel on the network share.  Now if the 2003 machine has outlook open, the 2007 machine will not fire the rule.  If I close the 2003 outlook, and send the triggering message, the 2007 machiend works every time.  

I tried closing and opening outlook on each machine in a different sequence, even logginf off the machines.  No change.  I deleted and re-created the rule.  No change.

If I change the rule to fire the original excel file from the network share, it fires on both machines.  pretty wierd...I am stumped.  This has to go over to India for production and I prefer not to get into developing and documenting an outlook module to wake the shares, as I then need to put a module on multiple machines.  Is there a better way to accomplish this, and ever seen this event?

I am testing this with a sinble login, but my users will have different ID, so this may not be a big factor.

Any thoughts?

Thanks in advance!
0
MrAutomate
Asked:
MrAutomate
  • 3
  • 2
1 Solution
 
giltjrCommented:
What does the rule do?  If it moves the e-mail, then which ever system sees the e-mail first will trigger the rule and the other system will not see it.

Also, I'm not sure what you mean the the shares are asleep.  A share may get disconnected, but as soon as something attempts to access the share, it should get reconnected and be able to see/access the share without any problems.
0
 
MrAutomateAuthor Commented:
The rule starts an application.  It starts excel.   The excel file is located on a network share.  The network is Novell.  Novell custs users off at 12:30 each evening for maintenance purposes.  Some machines havea hard time reconnecting.  I agree with you that when something attempts to connect, it should communicate with that shared resource.  This does not always happen, however.  
0
 
giltjrCommented:
I have never used Novel, does it have any type of file locking that would prevent a second opening of the same file?

If you had to couldn't you just fire off a batch/command file that does a net use and then starts Excel?  I would think you would need that any way, because you can't guarantee that share will always be there (file server could be down) and therefor you would need some type of error checking.
0
 
MrAutomateAuthor Commented:
giltjr:
Sorry, been out of town.  we had the same thoughts.   Yes, I had in place da batch file that I calls an AT task that the workstation runs at 3, 4, and 5 AM to make sure the network stays alive.  This has worked over the past month.  I was hoping to avoid abbitional batch files, or vba modules in outlook to wake the shares once the rule fires from VBA.  An interesting finding, but not hard to solve.
0
 
MrAutomateAuthor Commented:
Thanks!
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now