Supress rightfax pop up window
HI ,
I want to suppress the window that opens when I click send fax in the outlook plug in. I am not sure what reg does this to supress . It should say no and proceed to next window.
If anyone has come across the same, please share.
Thanks.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
dunnpy
8 years ago
This message looks the type of thing that would pop up every time you try and perform the fax action in Outlook - because it can't connect to the Rightfax backend.
Does it do it every time, or it is a one off pop up?
If it's one off, then use you favourite lightweight snapshot tool (InstallRite/PictureTaker/InstallWatch) and snap clicking the button to see where it's storing that registry or file setting.
If it's every time, then it would look like your configuraiton is off as the plugin can't communicate with RightFax.
Dunnpy
Does it do it every time, or it is a one off pop up?
If it's one off, then use you favourite lightweight snapshot tool (InstallRite/PictureTaker/InstallWatch) and snap clicking the button to see where it's storing that registry or file setting.
If it's every time, then it would look like your configuraiton is off as the plugin can't communicate with RightFax.
Dunnpy
Posted by:
dunnpy
8 years ago
The configuration options are somewhere in Outlook, maybe under 'File>Rightfax' or under the plugin configuration options.
It could be any number of things that are preventing a connection, probably best to contact your internal support/external support for the solution to confirm settings and the service status.
Dunnpy
It could be any number of things that are preventing a connection, probably best to contact your internal support/external support for the solution to confirm settings and the service status.
Dunnpy
Comments:
-
no luck, don't see anything with that as well. - shamu 8 years ago
Posted by:
dunnpy
8 years ago
You haven't mentioned that you're packaging the plugin, or if this is from a normal installation.
If this occurs only with the package and the manual installation works fine - then there's an issue with your package.
If a manual installation also doesn't work - then as I said, it's a problem with the configuration or the Rightfax backend.
I believe that theres config on the server, and there's also a Rightfax exchange module for an email/fax gateway - depending on your set up.
If you are the exchange/RightFax support internally, then it's time to contact RightFax themselves.
If there is another internal support team for this, push back to them with this issue.
If this occurs only with the package and the manual installation works fine - then there's an issue with your package.
If a manual installation also doesn't work - then as I said, it's a problem with the configuration or the Rightfax backend.
I believe that theres config on the server, and there's also a Rightfax exchange module for an email/fax gateway - depending on your set up.
If you are the exchange/RightFax support internally, then it's time to contact RightFax themselves.
If there is another internal support team for this, push back to them with this issue.
Comments:
-
It is a vendor MSI I am using, And a manual install shows the similar manner. - shamu 8 years ago
Posted by:
dunnpy
8 years ago
The same issue with a manual install would point to a configuration issue somewhere.
You would need to verify that the backend is all in place, and that the acount you're testing with has the correct permissions.
I've worked in environments where packaging of software that utilises a backend is done in parallel to the server set up - so there is no backend in place to test and verify against. It is packaged and set aside until things align and the package can be tested, on the understanding that discovery wasn't validated prior to work commencing.
I've also had packages to create that 'should' work with the configuration discovery provided - but no one has actually maually installed and configured the software to verify the settings and connectivity prior to it coming through for packaging.
You have to push back in this situation, because it's potentially wasting your time and effort on something that may never work.
You would need to verify that the backend is all in place, and that the acount you're testing with has the correct permissions.
I've worked in environments where packaging of software that utilises a backend is done in parallel to the server set up - so there is no backend in place to test and verify against. It is packaged and set aside until things align and the package can be tested, on the understanding that discovery wasn't validated prior to work commencing.
I've also had packages to create that 'should' work with the configuration discovery provided - but no one has actually maually installed and configured the software to verify the settings and connectivity prior to it coming through for packaging.
You have to push back in this situation, because it's potentially wasting your time and effort on something that may never work.
