Topics > DataPlus Sage Accounting Integration > DataPlus 4.0 Sage 100 > FAQ ID # 78

FAQ ID # 78
Last Update : 2018/10/07
Print this FAQ

Question / Issue
DataPlus 4.0 Sage 100 - Messages

Answer / Solution
PROGRAM: DataPlus for Sage 100 - Messages
Table of Contents

DataPlus Installation
    Notice
    DataPlus 4.0 Warning
    Unable to insert update database. Reason given: Unable to create or establish connection to linked server. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

    Reason 1

  1. Allow External Access was not configured.

    Resolution

  2. Open Company Maintenance
  3. Preferences
  4. Check Allow External Access

    Reason 2

  5. ODBC Basic/Database Directory: Incorrect path to PROVIDEX.DDF

    Resolution

  6. C:\Sage\Sage 100 Standard ERP\MAS90
  7. C:\Sage\Sage 100 Advanced\MAS90
  8. Check Allow External Access
Type: DataPlus Configuration

    Notice
    DataPlus 4.0 Warning
    Unable to insert update database. Reason given: Unable to create or establish connection to linked server. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

    Resolution

  1. Sage company code, user name and or password was entered in incorrect.
Type: DataPlus Configuration

    Configure Data Source (ODBC)
  1. Click on System DSN tab
    Configure Data Source (ODBC)
  1. Click on Source Name [S100_ABC]
  2. Click on Configure
    Configure Data Source (ODBC)
  1. Click on Login Tab
  2. Modify Company code: sagecompanycode
  3. Modify Default UserID: sageuserid
  4. Modify Password: sagepassword
  5. Click on Debug Tab
    Configure Data Source (ODBC)
  1. Click on Apply
  2. Click on Test Connection
  3. If successful click on OK
    SQL Instance Restart
  1. Restart SQL instance
    Notice
  1. Click on OK
    Previous Database Create
  1. Click on Previous
    Continue Installation
  1. Click on Next
    Notice
    Unable to insert update database.
    Reason given: Invalid column name 'TaxAmt'.

    Reason

  1. Business Insights Module not Active
    Resolution
  2. Open Sage 100
  3. Modules / Library Master / Company Maintenance
  4. Choose Company Code
  5. Activate
  6. Business Insights

    Reason

  7. Sage 100 Database has not been converted
    Resolution
  8. Open Sage 100
  9. Modules / Library Master / Company Maintenance
  10. Choose Company Code
  11. Convert
    WARNING! Data entry files may be cleared. Back up your data before converting.
    The data will be converted to the newest version installed.
  12. Accept
  13. Close
  14. Continue DataPlus Installer
  15. Previous/Next
Type: Sage 100 Configuration

    Notice
    Unable to insert update database.
    Reason given: Cannot open the table "IT_Category" from OLE DB provider "MSDASQL" for linked server

    NOTE: If this is your first install, you must set default view permissions and re-load DataPlus.

    Resolution

  1. Activate Business Insights Module and Accept KB Line 163
  2. Enable I/T eBusiness Manager KB Line 163
Type: Sage 100 Configuration

    Notice
    Unable to insert update database.
    Reason given: Cannot open the table "IT....

    NOTE: If this is your first install, you must set default view permissions and re-load DataPlus.

    Resolution

  1. Enable I/T eBusiness Manager KB Line 163
Type: Sage 100 Configuration

    Notice
    Unable to create database objects.
    Reason given: spMenuConfigCreateNew : Must declare the scalar variable "@TableName".

    Resolution

Type: Sage 100 Configuration

DataPlus Configuration
    Action
  1. Server/Client: DataPlus Configuration Manager
  2. Click on Test Connection

    Error
    DataPlus 4.0 Warning
    Unable to get configuration from server.
    The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character amoung the padding characters.

    Resolution

  3. Current user does not have permission to create DataPlus-Connection.xml file
  4. Location
    1. C:\Program Files (x86)\Hogan Data\DataPlus 4.0
    2. C:\Program Files (x86)\ACT\Act for Windows\Plugins\DataPlus 4.0
Type: DataPlus Configuration

DataPlus Tab
    Warning
    DataPlus 4.0 Warning
    No DataPlus menus were found. The DataPlus Tab will be disabled.

    NOTE: If this is your first install, you must set default view permissions and re-load DataPlus.

    Resolution

  1. Server Installation KB Line 163
Type: DataPlus Configuration

DataPlus Activation
    Error
    DataPlus 4.0 Error
    The following error has occurred: Product is not activated and trial has expired. All DataPlus features will be disabled. Please run activation and re-enable DataPlus.

    Resolution

  1. Server Installation KB Line 187
  2. Client Installation KB Line 27
Type: DataPlus Activation

Act Opportunity Product
    Import Summary
    Warning
    Could not import. Expected 3 tables but they were not found.

    Resolution

  1. Ensure that the service "Hogan Data Sage100 Bridge" is started
  2. Ensure that the service "Hogan Data Sage100 Bridge" has rights to run
Type: DataPlus Configuration

DataPlus Push Configuration
    Notice
    Sage 100 Configuration Notice
    Sage connection failed. There was no end point listening at http://w764-s100erp:8000/Sage100Bridge/proxy.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerExcepton, if present, for more details.

    Resolution

  1. Ensure that the service "Hogan Data Sage100 Bridge" is started
  2. Ensure that the service "Hogan Data Sage100 Bridge" has rights to run
Type: DataPlus Configuration

    Notice
    Sage 100 Configuration Notice
    Sage connection failed. The hostname could not be parsed.

    Resolution

  1. Ensure that the host server name is correct
Type: DataPlus Configuration

    Sage 100 Configuration Notice

    Action

  1. Configure Sage 100 Push
  2. Test Connection

    Notice
    Sage 100 Configuration Notice
    Sage connection failed. Exception has been thrown by the target of an invocation.

    Resolution

  3. Ensure that the service "Hogan Data Sage100 Bridge" has rights to run
    1. Test service using local
    2. Test service using local administrator
    3. Test service using domain administrator
Type: DataPlus Configuration

After testing the bridge, "Test Connection" to Sage.

Depending on your network and permissions, the test can pass with in all 3 cases or just 1.
In most cases "Local" should work.
In some cases domain administrator must be used.

    Error
    Push to Sage 100 Error
    The following error has occured: Cannot open database "dpS100_MFG" requested by the login. The login failed. Login failed for user 'HOGANDATA\administrator'.

    Resolution

  1. Database dpS100_MFG has not been configured for integration with DataPlus
Type: DataPlus Configuration

    Notice
    Sage 100 Configuration Notice
    Sage connection failed. Invalid Sage 100 Company Code

    Resolution 1

  1. Company Code is incorrect - validate code from your Sage 100 application and re-enter

    Resolution 2

  2. "Allow External Access" may not be enabled in Sage 100 "Company Maintenance" Preferences.
Type: Sage 100 Configuration

    Sage 100 Configuration Error
    The follow error has occured:
    Value cannot be null. Parameter name: source

    Steps

  1. Configure Sage 100 Push

    Reason
    Server Settings/Server Name is incorrect

    Resolution

  2. Open Inbound port for SQL on server
Type: Sage 100 Configuration

    Sage 100 Configuration Error
    The follow error has occured:
    Value cannot be null. Parameter name: source

    Steps

  1. Configure Sage 100 Push
  2. Save

    Reason

  3. User/Domain User - UAC Level 4
  4. User/Domain User - UAC Level 3 (Administrator = 2)
  5. User/Domain User - UAC Level 2 (When Admin = 2 Standard = 3)
  6. User/Domain User - UAC Level 2 (When Admin = 1 Standard = no access)

    Resolution

  7. Open Inbound port for SQL on server
Type: Sage 100 Configuration

    Sage 100 Configuration Error
    The follow error has occured:
    Value cannot be null. Parameter name: source

    Steps

  1. Configure Sage 100 Push

    Reason
    Server Settings/Server Name is incorrect

    Resolution

  2. Open Inbound port for SQL on server
Type: Sage 100 Configuration

DataPlus Push Contacts
    Push to Sage 100
    Condition
    When pushing a customer from Act to Sage 100 the dropdown for "Salesperson No:" is empty.

    Resolution

  1. "Customer No" field must be populated first.
  2. "Salesperson No" contact field does not exist in Act
  3. "Salesperson No" must be mapped between Act and Sage 100 (KB)
Type: Sage 100 Contact Push

    Notice
    Push to Sage 100 Notice
    Push settings are not configured for this company.

    Resolution

  1. Find Resoluton
Type: Sage 100 Contact Push

    Error
    Push to Sage 100 Error
    Failed pushing contact.
    Failed pushing Customer. The request channel timed out while waiting for a reply after 00:00:59.9979999. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.

    Resolution 1

  1. Restart SQL instance in "Services"
  2. Run/services.msc

    Resolution 2

  3. Test your linkserver connection
  4. In SSMS "New Query" and execute script EXECUTE SP_TABLES_EX 'S100_ABC' (replace ABC with your company code)
  5. If it fails then this is the reason for the connection timeout
  6. Recreate Linked Server

    Resolution 3

  7. Close all instances of Sage 100
  8. Delete all *.LCK files from C:\Sage\Sage 100 Standard ERP\MAS90\LOCK\_ABC (replace ABC with your company code)
  9. When you reopen Sage 100 the files will be recreated.

    Resolution 4

  10. Exclude Sage/Mas folder
  11. Exclude file extensions also

    Resolution 5

  12. Stop SQL instance in "Services"
  13. Replace the following Providex files
    - C:\Windows\System32
    - pvxio.dll
    - pvxodbc.dll
    - pvxsec64.dll

  14. Restart SQL instance in "Services"
Type: SQL Configuration/Permissions

    Error
    Push to Sage 100 Error
    Failed pushing contact.
    Failed pushing Customer. Failed pushing Customer. You are not authorized to access this program.

    Resolution

  1. Ensure that all the Sage 100 modules have been converted in "Company Maintenance".
Type: Sage 100 Configuration

    Error
    Push to Sage 100 Error
    Failed pushing contact.
    Failed pushing Customer. Exception has been thrown by the target of an invocation.

    Resolution

  1. Ensure that all the Sage 100 modules have been converted in "Company Maintenance".
Type: Sage 100 Configuration

    Error
    Push to Sage 100 Error
    Failed pushing contact.
    Failed pushing Customer. Cannot proceed as the requested customer does not exist in system. Error #12: File does not exist (oralready exists) File: MPOABC.SOA

    Resolution

  1. Customer No, Contact No, eCustomerID, eContactID fields in Act are populated.
  2. When pushing to Sage 100 these fields indicate Customer exists
  3. If customer does not exist in Sage 100 an error will occur
  4. If you want to push the contact to "create" it in Sage, remove the data in eCustomerID and/or eContactID field in Act
Type: Sage 100 Configuration

    Error
    Push to Sage 100 Error
    Failed pushing contact.
    Failed pushing contact Customer. Failed pushing Customer. You are not authorized to access this program.

    Resolution

  1. Customer No, Contact No, eCustomerID, eContactID fields in Act are populated.
  2. When pushing to Sage 100 these fields indicate Customer exists
  3. If customer does not exist in Sage 100 an error will occur
  4. If you want to push the contact to "create" it in Sage, remove the data in eCustomerID and/or eContactID field in Act
Type: Sage 100 Configuration

DataPlus Push Transactions
    Error
    Push to Sage 100 Error
    The following error has occurred: Failed pushing Sales Order, Error #41: Invalid integer encountered (range error or non-integer) Error #41: Invalid integer encountered (range error or non-interger)

    Resolution

  1. Customer No, Contact No, eCustomerID, eContactID fields in Act are populated.
  2. When pushing to Sage 100 these fields indicate Customer exists
  3. If customer does not exist in Sage 100 an error will occur
  4. If you want to push the contact to "create" it in Sage, remove the data in eCustomerID and/or eContactID field in Act
Type: Sage 100 Sales Order Push

    Error
    Push to Sage 100 Error
    The following error has occurred: Failed pushing Sales Order. There was no endpoint listening at http://w74-s100erp:8000/Sage100Bridge/proxy.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException...

    Resolution

  1. Hogan Data S100 ERP Bridge may not started
  2. Start or restart the service and try again
Type: Sage 100 Sales Order Push

    Error
    Push to Sage 100 Error
    The following error has occurred: Failed pushing Sales Order. Error saving information for sagefield "ItemCodeDesc"

    Resolution

  1. Item Type is not allowed to push to Sage transaction
Type: Sage 100 Sales Order Push

    Error
    Push to Sage 100 Error
    The following error has occurred: Failed pushing Sales Order. Exception has been thrown by the target of an invocation.

    Reason

  1. Transaction permission fails due to proper permissions using the "Hogan Data S100 ERP Bridge"

    Resolution

  2. Change permission to local or domain administrator account
Type: Sage 100 Sales Order Push

Windows/SQL Permission
    Error
    Error connecting to SQL Server
    A network related or instance-specific error occured while establishing a connetion to SQL Server. The server was not found or was not accessible. Verify that the instance name is corrext an d that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

    Resolution

  1. Ensure that Server/Instance is correct for DataPlus Server.
  2. Ensure that SQL Server Browser Service is running.
  3. UDP port 1434 is used for SQL Server Browser. Add Inbound Rule Port UDP/1434 allow the connection
  4. Use SQL Authentication (sa:password)
Type: SQL Configuration

    Error
    Error connecting to SQL Server
    Cannot open database "dpS100_ABC2", requested by the login. The login failed. Login failed for user 'domain\username'.

    Resolution

  1. Ensure that DataPlus Database is correct.
  2. Ensure the user has SQL permission to SQL database
    - SQL Security
    - DataPlus SQL Security
Type: SQL Configuration

    Error
    Error saving
    Error Saving Connection Settings: Access to the path 'C:\Program Files (x86)\Hogan Data\DataPlus 4.0\DataPlus-Connection.xml' is denied.

    Reason
    Current Windows user does not have permission to write the the folder.

    Resolution

  1. Run DataPlus 4.0 Configuration 'as administrator'
  2. Give user rights to folder (preferred method)
Type: SQL Configuration

    Error
    Error saving
    Error getting Master Setting: Cannot open database 'dpYourDatabaseName' requested by the login. The login failed. Login for user 'DOMAIN\USER'.

    Reason
    Current Windows user does not have permission to SQL database.

    Resolution

  1. Give user permission to read SQL database
    - SQL Security
    - DataPlus SQL Security
Type: SQL Configuration

    Error
    Unable to connect to database server.
    Reason Given: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40- Could not open a connection to SQL Server)

    Reason
    Server Settings/Server Name is incorrect

    Resolution

  1. Verify the Server Name and SQL Instance Name
    - Server Name:
    - YOURSERVER\YOURSQLINSTANCE
Type: SQL Configuration

    Error
    Unable to connect to database server.
    Reason Given: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40- Could not open a connection to SQL Server)

    Reason
    Server Settings/Server Name is incorrect

    Resolution

  1. Open Inbound port for SQL on server
Type: SQL Configuration


Related FAQs
DataPlus 4.0 Sage 100 - Server Installation
DataPlus 4.0 Sage 100 - Client Installation
DataPlus 4.0 Sage 100 - Act! Database Configuration
DataPlus 4.0 Sage 100 - Contact Push Configuration
DataPlus for Sage 100 - Contact Imported from Sage 100 to Act!

Direct Link to This FAQ
http://kb.hogandata.com/?f=78

Back to Top