is there some bad interaction with MSDE possibly ?
is anyone else experiencing this issue ???
-=-=-=-=-=-=-=-=-
Hi Chris,
First and foremost, you are right about Peachtree support, they are useless! Here is the latest info I have. We believe that the Pervasive database is listening on the same port, # 1583, that BackupExec is using. Pervasive support gave us the following instructions on how to change the port Pervasive uses. Our ISIT department hasn't been able to give it a try yet, so I don't know if it will work yet. If you have any luck, let me know.
Paul
Changing the Default Communication Ports Chapter contents Pervasive PSQL communicates through three ports. Your firewall(s) and routers need to allow access to the following ports for remote access with the server database engine:
3351 for the transactional interface 1583 for the relational interface 139 for named pipes (see note) Typically, you do not need to modify the ports unless you have a conflict with them.-------------------------------------------------------------------------------- Note The Windows operating system uses port 139 for authentication to the operating system. An alternative to allowing access to port 139 through a firewall is to enable security on the Pervasive PSQL database. Once security is enabled, users, such as "Master," are authenticated to the database through the database's own security features. See To turn on security using Pervasive PSQL Explorer and To create a new user using Pervasive PSQL Explorer , both in Advanced Operations Guide.
--------------------------------------------------------------------------------
Port assignments 1583 is configurable for the server through the Pervasive PSQL utilities. See TCP/IP Port in Advanced Operations Guide. This port is manually configurable for clients as explained in this section.
Port assignment 3351 is manually configurable for the server and the clients as explained in this section.
Ensure that the port configurations match on both the server and all clients. You must stop then start the database engine for the port assignments to take effect.
Services File The services file is a text file used by the operating system for network communications. In the services files, you can manually assign the ports used by Pervasive PSQL Server and its clients. The following table summarizes this.
Platform Location of Services File Example Addition To Services File1 Windows 32-bit \WINDOWS\SYSTEM32\DRIVERS\ETC or \WINNT\SYSTEM32\DRIVERS\ETC To specify that you want to use port 1580 for the relational interface, add the line: psql 1580/tcp To specify that you want to use port 3355 for the transactional interface, add the line: btrieve 3355/tcp Windows 98/ME \WINDOWS NetWare SYS:\ETC Linux /etc
1Entries are case-sensitive in the Linux services files and in the Windows services file for 32-bit platforms. Entries in the NetWare services file are not case-sensitive.-------------------------------------------------------------------------------- Note After changing port assignments in the services file, you must stop then start the Pervasive PSQL database engine for the changes to take effect. See Starting and Stopping the Database Engine in Pervasive PSQL User's Guide.
GOD BLESS YOU
i have been searching high and low for someone else experiencing this issue !!!
has anything become of it ? are you positive its Symantec Backup Exec ?
i am running SBS 2003 with both Backup Exec and Trend Micro's Neatsuite for SMB
I blamed it on Trend Micro until i had completely uninstalled it and the issue persisted ... Peachtree support is utterly useless -
Reply Forward Invite Paul to chat
Reply Reply to all Forward Print Add Christian to Contacts list Delete this message Report phishing Show original Message text garbled? Christian Dolese to Paul show details May 11 (5 days ago)
thank you very much for the reply , it sounds like you are a larger company using their product
what i dont understand is their complete lack of effort to diagnose anything ...
if possible can we speak on the phone one day ... i will keep in touch via email also
i just hurriedly experimented with a complete unintall of symantec backup exec and we tested and experienced the same issue - i was afraid the installs would still leave traces of the ports they used , additionaly by defauly the msde engine is part of SBS 2003 , i am running with all of the latest patches .. etc etc
again lets stay in touch over the issue - it has to be something very very new for their wonderful support people not to have a cue card to read from on it yet :-( im picking on them but really they do more harm with some users than they help
i wonder if its so much backup exec as it is any MSDE instances interaction with the PSQL instance required for quantum to funtion
again you have made my day even with our failed test - i know i am not nuts and am having my client watch me type this back to you - now she knows that too
if you are tied up i would be glad to work with your ISIT department to experiment with some fixes - but again i would ask why isnt peachtree support more involved with this ?????
- Show quoted text - On 5/11/07, Paul Roberts wrote: Hi Chris,
First and foremost, you are right about Peachtree support, they are useless! Here is the latest info I have. We believe that the Pervasive database is listening on the same port, # 1583, that BackupExec is using. Pervasive support gave us the following instructions on how to change the port Pervasive uses. Our ISIT department hasn't been able to give it a try yet, so I don't know if it will work yet. If you have any luck, let me know.
Paul
Changing the Default Communication Ports Chapter contents Pervasive PSQL communicates through three ports. Your firewall(s) and routers need to allow access to the following ports for remote access with the server database engine:
3351 for the transactional interface 1583 for the relational interface 139 for named pipes (see note) Typically, you do not need to modify the ports unless you have a conflict with them.-------------------------------------------------------------------------------- Note The Windows operating system uses port 139 for authentication to the operating system. An alternative to allowing access to port 139 through a firewall is to enable security on the Pervasive PSQL database. Once security is enabled, users, such as "Master," are authenticated to the database through the database's own security features. See To turn on security using Pervasive PSQL Explorer and To create a new user using Pervasive PSQL Explorer , both in Advanced Operations Guide.
--------------------------------------------------------------------------------
Port assignments 1583 is configurable for the server through the Pervasive PSQL utilities. See TCP/IP Port in Advanced Operations Guide. This port is manually configurable for clients as explained in this section.
Port assignment 3351 is manually configurable for the server and the clients as explained in this section.
Ensure that the port configurations match on both the server and all clients. You must stop then start the database engine for the port assignments to take effect.
Services File The services file is a text file used by the operating system for network communications. In the services files, you can manually assign the ports used by Pervasive PSQL Server and its clients. The following table summarizes this.
Platform Location of Services File Example Addition To Services File1 Windows 32-bit \WINDOWS\SYSTEM32\DRIVERS\ETC or \WINNT\SYSTEM32\DRIVERS\ETC To specify that you want to use port 1580 for the relational interface, add the line: psql 1580/tcp To specify that you want to use port 3355 for the transactional interface, add the line: btrieve 3355/tcp Windows 98/ME \WINDOWS NetWare SYS:\ETC Linux /etc
1Entries are case-sensitive in the Linux services files and in the Windows services file for 32-bit platforms. Entries in the NetWare services file are not case-sensitive.-------------------------------------------------------------------------------- Note After changing port assignments in the services file, you must stop then start the Pervasive PSQL database engine for the changes to take effect. See Starting and Stopping the Database Engine in Pervasive PSQL User's Guide.
GOD BLESS YOU
i have been searching high and low for someone else experiencing this issue !!!
has anything become of it ? are you positive its Symantec Backup Exec ?
i am running SBS 2003 with both Backup Exec and Trend Micro's Neatsuite for SMB
I blamed it on Trend Micro until i had completely uninstalled it and the issue persisted ... Peachtree support is utterly useless -
Reply Forward
Reply Reply to all Forward Print Add Christian to Contacts list Delete this message Report phishing Show original Message text garbled? Christian Dolese to cdolese show details 5:43 pm (0 minutes ago)
- Show quoted text -
---------- Forwarded message ---------- From: Christian Dolese Date: May 11, 2007 8:17 PM Subject: Re: Peachtree Pervasive conflict To: Paul Roberts
thank you very much for the reply , it sounds like you are a larger company using their product
what i dont understand is their complete lack of effort to diagnose anything ...
if possible can we speak on the phone one day ... i will keep in touch via email also
i just hurriedly experimented with a complete unintall of symantec backup exec and we tested and experienced the same issue - i was afraid the installs would still leave traces of the ports they used , additionaly by defauly the msde engine is part of SBS 2003 , i am running with all of the latest patches .. etc etc
again lets stay in touch over the issue - it has to be something very very new for their wonderful support people not to have a cue card to read from on it yet :-( im picking on them but really they do more harm with some users than they help
i wonder if its so much backup exec as it is any MSDE instances interaction with the PSQL instance required for quantum to funtion
again you have made my day even with our failed test - i know i am not nuts and am having my client watch me type this back to you - now she knows that too
if you are tied up i would be glad to work with your ISIT department to experiment with some fixes - but again i would ask why isnt peachtree support more involved with this ?????
On 5/11/07, Paul Roberts wrote: Hi Chris,
First and foremost, you are right about Peachtree support, they are useless! Here is the latest info I have. We believe that the Pervasive database is listening on the same port, # 1583, that BackupExec is using. Pervasive support gave us the following instructions on how to change the port Pervasive uses. Our ISIT department hasn't been able to give it a try yet, so I don't know if it will work yet. If you have any luck, let me know.
Paul
Changing the Default Communication Ports Chapter contents Pervasive PSQL communicates through three ports. Your firewall(s) and routers need to allow access to the following ports for remote access with the server database engine:
3351 for the transactional interface 1583 for the relational interface 139 for named pipes (see note) Typically, you do not need to modify the ports unless you have a conflict with them.-------------------------------------------------------------------------------- Note The Windows operating system uses port 139 for authentication to the operating system. An alternative to allowing access to port 139 through a firewall is to enable security on the Pervasive PSQL database. Once security is enabled, users, such as "Master," are authenticated to the database through the database's own security features. See To turn on security using Pervasive PSQL Explorer and To create a new user using Pervasive PSQL Explorer , both in Advanced Operations Guide.
--------------------------------------------------------------------------------
Port assignments 1583 is configurable for the server through the Pervasive PSQL utilities. See TCP/IP Port in Advanced Operations Guide. This port is manually configurable for clients as explained in this section.
Port assignment 3351 is manually configurable for the server and the clients as explained in this section.
Ensure that the port configurations match on both the server and all clients. You must stop then start the database engine for the port assignments to take effect.
Services File The services file is a text file used by the operating system for network communications. In the services files, you can manually assign the ports used by Pervasive PSQL Server and its clients. The following table summarizes this.
Platform Location of Services File Example Addition To Services File1 Windows 32-bit \WINDOWS\SYSTEM32\DRIVERS\ETC or \WINNT\SYSTEM32\DRIVERS\ETC To specify that you want to use port 1580 for the relational interface, add the line: psql 1580/tcp To specify that you want to use port 3355 for the transactional interface, add the line: btrieve 3355/tcp Windows 98/ME \WINDOWS NetWare SYS:\ETC Linux /etc
1Entries are case-sensitive in the Linux services files and in the Windows services file for 32-bit platforms. Entries in the NetWare services file are not case-sensitive.-------------------------------------------------------------------------------- Note After changing port assignments in the services file, you must stop then start the Pervasive PSQL database engine for the changes to take effect. See Starting and Stopping the Database Engine in Pervasive PSQL User's Guide.
GOD BLESS YOU
i have been searching high and low for someone else experiencing this issue !!!
has anything become of it ? are you positive its Symantec Backup Exec ?
i am running SBS 2003 with both Backup Exec and Trend Micro's Neatsuite for SMB
I blamed it on Trend Micro until i had completely uninstalled it and the issue persisted ... Peachtree support is utterly useless -
Reply Forward
Your message has been sent.
Reply Reply to all Forward Print Add Christian to Contacts list Delete this message Report phishing Show original Message text garbled? Christian Dolese to Paul show details 5:57 pm (0 minutes ago)
Hi Paul ,
any more news on this issue from your end ?
- Show quoted text - Hi Chris,
First and foremost, you are right about Peachtree support, they are useless! Here is the latest info I have. We believe that the Pervasive database is listening on the same port, # 1583, that BackupExec is using. Pervasive support gave us the following instructions on how to change the port Pervasive uses. Our ISIT department hasn't been able to give it a try yet, so I don't know if it will work yet. If you have any luck, let me know.
Paul
Changing the Default Communication Ports Chapter contents Pervasive PSQL communicates through three ports. Your firewall(s) and routers need to allow access to the following ports for remote access with the server database engine:
3351 for the transactional interface 1583 for the relational interface 139 for named pipes (see note) Typically, you do not need to modify the ports unless you have a conflict with them.-------------------------------------------------------------------------------- Note The Windows operating system uses port 139 for authentication to the operating system. An alternative to allowing access to port 139 through a firewall is to enable security on the Pervasive PSQL database. Once security is enabled, users, such as "Master," are authenticated to the database through the database's own security features. See To turn on security using Pervasive PSQL Explorer and To create a new user using Pervasive PSQL Explorer , both in Advanced Operations Guide.
--------------------------------------------------------------------------------
Port assignments 1583 is configurable for the server through the Pervasive PSQL utilities. See TCP/IP Port in Advanced Operations Guide. This port is manually configurable for clients as explained in this section.
Port assignment 3351 is manually configurable for the server and the clients as explained in this section.
Ensure that the port configurations match on both the server and all clients. You must stop then start the database engine for the port assignments to take effect.
Services File The services file is a text file used by the operating system for network communications. In the services files, you can manually assign the ports used by Pervasive PSQL Server and its clients. The following table summarizes this.
Platform Location of Services File Example Addition To Services File1 Windows 32-bit \WINDOWS\SYSTEM32\DRIVERS\ETC or \WINNT\SYSTEM32\DRIVERS\ETC To specify that you want to use port 1580 for the relational interface, add the line: psql 1580/tcp To specify that you want to use port 3355 for the transactional interface, add the line: btrieve 3355/tcp Windows 98/ME \WINDOWS NetWare SYS:\ETC Linux /etc
1Entries are case-sensitive in the Linux services files and in the Windows services file for 32-bit platforms. Entries in the NetWare services file are not case-sensitive.-------------------------------------------------------------------------------- Note After changing port assignments in the services file, you must stop then start the Pervasive PSQL database engine for the changes to take effect. See Starting and Stopping the Database Engine in Pervasive PSQL User's Guide.
GOD BLESS YOU
i have been searching high and low for someone else experiencing this issue !!!
has anything become of it ? are you positive its Symantec Backup Exec ?
i am running SBS 2003 with both Backup Exec and Trend Micro's Neatsuite for SMB
I blamed it on Trend Micro until i had completely uninstalled it and the issue persisted ... Peachtree support is utterly useless -