|
ConsoleOne FAXserve Snapin shows an error
message “You need to be a FAXserve administrator
to browse this item. Please log in as a FAXserve
administrator.”
Solution: Apply the latest ConsoleOne FAXserve snapin patch available from our
web site. (Download C1 patch here)
ConsoleOne FAXserve Snapin does not allow you to authorize new user
Cause:
Some required
DLLs are missing in the system.
Solution: Apply the latest ConsoleOne FAXserve snapin
patch available from our web site. Make sure you have UTIL.ZIP applied.
(Download C1 patch here)
ConsoleOne FAXserve Snapin says “No FAXserve
license installed on this server”
Cause:
Some required
DLLs are missing in the system.
Solution:
Apply the latest ConsoleOne FAXserve snapin
patch available from our web site. Make sure you have UTIL.ZIP applied.
(Download C1 patch here)
FAXserve Runtime Message screen shows an error message
"Unable to set event handle" after the fax is received. And the received fax
cannot be routed.
Cause:
The events in file FAX.SEQ are all used up.Solution:
-
Download
FAX_SEQ.ZIP – it contains the new fax.seq
file.
-
On system
console, unload faxserve
-
On FAXserve
server, go to
\\FAXSERVE\CONTROL folder
-
Backup the
original FAX.SEQ file in the folder
-
Unzip the
FAX_SEQ.ZIP. It contains a new FAX.SEQ file
-
Replace the
\\FAXSERVE\CONTROL\FAX.SEQ with
the new one (from the FAX_SEQ.Zip)
-
load
faxserve
FAX.EMA corrupted
FAX.EMA is a binary file that contains all the
faxserve users and their email address (when they are also Groupwise users)
Solution:
-
First apply
the latest ConsoleOne FAXserve snapin patch
available from our web site. (Download C1
patch here)
-
If you have
regular backup, retrieve both \faxserve\control.rt\fax.ema
and \faxserve\misc\fax.ema from your backup.
-
If you don’t
have the backup, From our ConsoleOne
FAXserve snapin -> User List -> Right click
and select Rebuild FAX.EMA
Failed to login to server: -[0x29d]
Cause:
FAXSERVE_servername user object’s password has
been changed.
Solution:
Please call/email tech support for assistance.
Failed to login to server: -[0x259]
Cause:
FAX_SERVICES_servername object does not exist.
Solution:
You can re-create the object with the correct
trustee assignment thru ConsoleOne but it is
difficult to set it up correctly. The easy way
is to re-install FAXserve.
Using US Robotic modem, in some cases, FSNW7
reported sending faxes error but the remote
receiving fax machines actually received all
faxes pages and reported successful
Cause:
The script file for US Robotic modem does not
handle some conditions correctly.
Solution:
1.
Download USR20.ZIP - It contains USR20.MSF
2.
unload faxserve
3.
copy the new USR20.MSF to the following folder:
·
faxserve\control.rt folder
·
faxserve\drivers folder (make a backup of
USR20.MSF file in this folder).
4.
load faxserve
Missing or incorrect FAXserve.ini
Solution:
·
If the file is missing and you have a backup,
retrieve it from the backup.
·
If the file is there but information is not
correct, update it correctly.
Here is a sample of FAXserve.ini (POINTS is the
server name, PTDOMDIR is PostOffice directory,
SYS is the volume that FAXserve installed on)
VERSION=7.0
[LANGUAGE]
LANG=English
[Production]
1=POINTS
[Runtime]
1=POINTS
[POINTS]
VERSION=7.0
SvcPak=0
COUNTRY=001
HOMEDIR=SYS:\FAXSERVE
MAIL=SYS:\FAXSERVE\USER
QUEUE=SYS:FAXSERVE
QHOST 1=POINTS
REMOTE_CONFIG=SYS:\FAXSERVE\CONTROL
LOCAL_CONFIG=SYS:\FAXSERVE\CONTROL.RT
TRANSMIT=SYS:\FAXSERVE\CONTROL.RT\TX
RECEIVE=SYS:\FAXSERVE\CONTROL.RT\RX
CONNECTION_TYPE=NDS
LOCAL_CONNECTION_TYPE=NDS
[GroupWise]
GATEWAYHOME=POINTS\SYS:\PTDOMDIR\WPGATE\FAXSERVE
GATEWAYDATASTORE=POINTS\SYS:\PTDOMDIR\WPGATE\FAXSERVE
LOGO=GWCOVER.PCX
ReportTimeOut=1
[EMAIL_TYPE]
EMAIL_PRODUCT=GW41
Groupwise FAXserve gateway fails to have
notifications for Groupwise users
Cause:
It is a bug in FAXserve gateway
Solution:
Apply latest NLMs patch available from our web
site. (Download NLM patch and C3PO patch here)
Cannot send faxes using the GroupWise client.
Receive an NDR from
GroupWise as: "Not authorized to use FAXserve
gateway, please ensure that this user's
GroupWise E-Mail address has been configured in
the FAXserve Administrator " and the GroupWise
server console immediately prints the follow
error message on the system console: "Not enough
memory to processing email address database. "
Cause:
·
faxserve.ini is not correct OR
·
fax.ema is corrupted OR
·
fsgate.ini is not correct. The CONNECTION_TYPE=
is missing.
Solution:
·
On FAXserve server, make sure you have
faxserve.ini in sys:\system folder. See “missing
or incorrect faxserve.ini” for detail.
·
Check for the information in faxserve.ini. See
“missing or incorrect faxserve.ini” for detail.
·
Check if fax.ema is corrupted or not. See
“FAX.EMA is corrupted” for detail.
·
The CONNECTION_TYPE=NDS in file
fsgate.ini
·
Apply latest NLMs patch available from our web
site. (Download NLM patch and C3PO patch here)
Groupwise FAXserve gateway fails to delivery
incoming faxes to Groupwise user inbox
Cause:
·
GWFAX.NLM is not loaded
·
FAXserve user profile setting does not set up
correctly
Solution:
·
Make sure fsgate.ncf load gwfax.nlm
·
From ConsoleOne FAXserve Snapin -> User List ->
Select FAXserve user -> User Profile Make sure
you have the email address shown and option
“Route Via” using E-mail. Click OK to save the
profile.
When loading FAXserve, FAXserve only has none or
limited output to system console screen and then
unloads itself.
Cause:
·
sys:\public\faxserve.ini does not exist or
corrupted
·
FAXSERVE_servername user object is missing or
the settings is incorrect
·
FAX_SERVICES_servername NDS object is missing or
the setting is incorrect
Solutions:
·
On FAXserve server, make sure you have
faxserve.ini in sys:\system folder. See “missing
or incorrect faxserve.ini” for detail.
·
If FAXSERVE_servername user object is missing,
re-install FAXserve.
·
If FAX_SERVICES_servername object is missing,
re-install FAXserve
FAXserve does not see intelligent modem card or
modems that are connected to intelligent serial
card.
Cause:
In some cases, the IO port auto detection in
FAXserve fails. Without the IO port correct
value, FAXserve cannot talk to the intelligent
card.
Solution:
·
Download Class20.zip – it contains
class20.nlm, faxdrv.nlm, and force.inf
·
See “Now to find out port address of intelligent
modem card/serial IO card”
·
Once you find out the IO Port address, update
the value to force.inf. In my example, I have
IO=150
·
On FAXserve system console, unload faxserve
·
Go to FAXserve server SYS:\SYSTEM\ folder. Make
a backup of faxdrv.nlm
·
Go to FAXserve server \FAXserve\driver\ folder.
Make a backup of class20.nlm
·
Copy the new faxdrv.nlm to SYS:\SYSTEM\ folder.
Overwrite the existing one.
·
Copy the new class20.nlm to \FAXserve\driver\
folder. Overwrite the existing one.
·
Copy updated force.inf to FAXserve
server \FAXserve\control.rt\ folder
How to find out port address of intelligent
modem card/serial IO card
Here I am using
Digi AccelePort 4r as example. You might have
some other intelligent card. Make sure you have
the correct AIOxxxx NLM driver that comes with
your intelligent card.
Here is how to
find out the driver type for your board:
1)
Download AIOTERM.ZIP – it contains AIOTERM.NLM,
AIOTRM.TXT, and README.TXT
2)
Copy AIOTERM.NLM to your FAXserve server
SYS:\SYSTEM directory.
On FAXserve server
·
load aiodgmem (This is the Digi driver. Make
sure it loads OK)
·
load aiodgxr (This is the Digi driver. Make
sure it loads OK)
·
load aioterm (After aioterm is loaded, you
should have something that is similar to the
attached driver_type.bmp)
In my example, I am using AccelePort 4r and the
Driver_Type is 150. You might have a different
value for your intelligent board. Then you
update this value to force.inf file.
How to enable debug logs for FAXserve 7
On system console, load faxserve dev (dev
is to enable debug logging)
The debug files are
·
\faxserve\control.rt\faxserve.dbg
·
\faxserve\control.rt\LOG*.TXT (LOG0.TXT,
LOG1.TXT, LOG2.TXT …)
Each fax channel has its own LOGn.TXT
How to enable debug logs for Groupwise FAXserve
Gateway
For both FAXserve server and Groupwise server on
the SAME server, modify the sys:\system\fsgate.ncf
as shown in BOLD below.
LOAD GWFAX -PH-SYS:\DOMDIR\WPGATE\FAXSERVE -PW-SYS:\DOMDIR\WPGATE\FAXSERVE
–VER=DEBUG
LOAD FAXLIB.NLM LOG=S OUTFILE=GWLOG.TXT
LOAD GWFAXSND
–VER=DEBUG
Now on system console, run fsgate.ncf
For FAXserve server and Groupwise server on the
DIFFERENT servers
On Groupwise server, modify the sys:\system\fsgate.ncf
as shown in BOLD below.
LOAD GWFAX -PH-SYS:\DOMDIR\WPGATE\FAXSERVE -PW-SYS:\DOMDIR\WPGATE\FAXSERVE
–VER=DEBUG
#LOAD GWFAXSND
On FAXserve server, create a gwsnd.ncf in
sys:\system\ folder. The content of Gwsnd.ncf
will be as below
LOAD FAXLIB.NLM LOG=S OUTFILE=GWLOG.TXT
LOAD GWFAXSND
–VER=DEBUG
Now on Groupwise Server system console, run
fsgate.ncf
On FAXserve Server system console, run gwsnd.ncf
The debug files are
·
On Groupwise server SYS:\PUBLIC\FAXGWSRV.LOG
·
On Groupwise server YourDomain\WPGATE\FAXSERVE\FAX\LOG\FAXSERVE.TXT
·
On faxserve server \FAXSERVE\CONTROL.RT\FAXSERVE.DBG
·
On faxserve server SYS:\GWLOG.TXT
How to enable debug logs for ConsoleOne FAXserve
Snapin
Method 1
·
Right Click on the ConsoleOne Icon.
·
Go
to Properties
·
Select Shortcut Tab
·
In
the Target Field type "-debug –windowout"
at the end (for example: d:\Novell\ConsoleOne\1.2\bin\ConsoleOne.exe
-debug -windowout)
·
Click on ConsoleOne Icon and launch ConsoleOne.
You will see a small debug console window.
·
You might see a warning message. Ignore it and
click OK to continue.
·
Duplicate the problem. Then save the debug
output in the console window to a file. And
send that file to support.
Method 2
·
Right Click on the ConsoleOne Icon.
·
Go
to Properties
·
Select Shortcut Tab
·
In
the Target Field type "-debug –fileout c:\temp.txt"
at the end
·
For example: C:\Novell\ConsoleOne\1.2\bin\ConsoleOne.exe
–debug –fileout c:\temp.txt
·
Now duplicate the problem and then send the c:\temp.txt
file to support.
Files we
need for support
On FAXserve server
·
sys:\public\faxserve.ini
·
\faxserve\control.rt\fax.ema
On Groupwise server
·
sys:\system\fsgate.ncf
·
sys:\public\fsgate.ini
Debug logs for FAXserve
·
\faxserve\control.rt\faxserve.dbg
·
\faxserve\control.rt\LOG*.TXT (LOG0.TXT,
LOG1.TXT, LOG2.TXT …)
Debug logs for Groupwise FAXserve gateway
·
On Groupwise server SYS:\PUBLIC\FAXGWSRV.LOG
·
On Groupwise server YourDomain\WPGATE\FAXSERVE\FAX\LOG\FAXSERVE.TXT
·
On faxserve server \FAXSERVE\CONTROL.RT\FAXSERVE.DBG
·
On faxserve
server SYS:\GWLOG.TXT
|
