Below are a list of common issues and their known resolutions.

From time to time, issues may arise that require an admin to resolve them. Below are some known issues that can occur, as well as their resolutions or workarounds.

Updating a Portal License

After assigning new or updated licenses to an existing portal installation (see Applying Product Licenses ), it is necessary to recycle the B1WebAPI as well as the Portal IIS application pools before license changes will take effect.

  1. On the server that hosts B1WebAPI, open IIS.
  2. In IIS, recycle the Application Pool assigned to B1WebAPI (See How to Recycle an IIS Application Pool).
  3. On the server that hosts Portal websites, open IIS.
  4. In IIS, recycle the Application Pools assigned to any Portal website (See How to Recycle an IIS Application Pool).

B1WebAPI Exception “System.Runtime.InteropService.COMException”

Cause: The B1WebAPI may lose its connection to the SAP Business One company and display this error.

Error Message:

Server Error in '/' Application.
<message>Exception from HRESULT: 0XE06D7363</message>
<exceptionType>System.Runtime.InteropServices.COMException</exceptionType>
<stackTrace>  at SAPbobsCOM.CompanyClass.GetBusinessObject(BoObjectTypes Object)
    at B1ServerEnabler.ObjectRunner.GetB1ObjectXML(String b1ObjectTypeString, String key, Boolean forEdit)
    at B1ServerEnabler.B1WebUserManager.GenerateAuthenticateB1WebUserResult(String userName, B1WebUser wu, AuthenticationResultEnum anthResult)
    at B1ServerEnabler.B1WebUserManager.AuthenticateB1WebUser(NameValueCollection parameters)
    at B1ServerEnabler.Processor.UserRequest.ProcessRequest()
    at B1ServerEnabler.B1EnablerModule.application_BeginRequest(Object sender EventArgs e)</stackTrace>

Resolution:

  1. If Vision33 Server Tools is running, exit before continuing.
  2. On the server that hosts B1WebAPI, open IIS.
  3. In IIS, recycle the Application Pool assigned to B1WebAPI (See How to Recycle an IIS Application Pool).
  4. If the Manager Add-On for SAP Business One is running, restart it before proceeding.

Portal can’t connect

If the portal can’t connect or displays one of the following error messages, perform the steps outlined below.

Error message: Server Error in / Application - Invalid URI: Invalid port specified.

This error indicates that the Portal website is trying to connect to the B1WebAPI on a URI or port that is invalid. Typically, this is a typo in the B1WebAPI URL or port that has been configured on the Portal website.

See details below for how to update the B1WebAPI URL and port.

Error message: Server Error in / Application - Invalid URI: Invalid port specified.
Error message: Server Error in / Application - Invalid URI: Invalid port specified.

Error message: Server Error in / Application - No connection could be made because the target machine actively refused it

This error indicates that the Portal website is trying to connect to the B1WebAPI on the wrong port. This can also be caused by a firewall preventing access on the correct port.

See details below for how to update an incorrect port.

Error message: Server Error in / Application - No connection could be made because the target machine actively refused it
Error message: Server Error in / Application - No connection could be made because the target machine actively refused it

Error message: Server Error in / Application - The remote name could not be resolved.

This error indicates that the Portal website can’t connect to the B1WebAPI. This typically means there is a typo in the URL used to connect to the B1WebAPI. It could also mean B1WebAPI is not installed, or that a firewall is in place which prevents the connection.

See details below for how to resolve a URL typo.

Error message: Server Error in / Application - The remote name could not be resolved
Error message: Server Error in / Application - The remote name could not be resolved

Error message: Server Error in / Application - The remote server returned an error: (401) Unauthorized.

This error indicates that the B1WebAPI username or password assigned to the Portal website is incorrect.

See details below for how to update the B1WebAPI username and password.

Error message: Server Error in / Application - The remote server returned an error: (401) Unauthorized.
Error message: Server Error in / Application - The remote server returned an error: (401) Unauthorized.

Resolving Portal Connection Issues

To resolve errors caused by incorrect B1WebAPI URL, port, username or password, the Portal website’s web.config file must be updated. This file is contianed in the portal website’s root directory. For Customer Portal, the default path is C:/inetpub/wwwroot/zed Customer Portal/. For Employee Portal, the default path is C:/Program Files (x86)/zedIT/zed Employee Portal/. For Vendor Portal, the default path is C:/Program Files (x86)/zedIT/zed Vendor Portal/.

  1. On the web server, navigate to the Portal website folder.
  2. Open the website’s web.config file.
  3. Look for a section called <b1ClientEnabler ... >. In this section, the URL (including port), username, or password can be updated. Saving this file will automatically restart the website and apply the connection changes.

Ensure enablerHost is set to the full URL, port and (if applicable) profile of the B1WebAPI instance. For example, http://192.168.0.2:4033 or http://192.168.1.23:4033/prod.

enablerDomain should be left blank.

Ensure enablerUserName is correctly set to the B1WebAPI username.

Ensure enablerPassword is correctly set to the B1WebAPI password.

For example:

<b1ClientEnabler
    enablerHost="http://192.168.1.2:4033/myProfile" enablerDomain=""
    enablerUserName="myUser" enablerPassword="myPassword"
    changePasswordPageURI="~/ChangePassword.aspx" loginPageURI="~/Login.aspx"
    defaultPageURI="~/index.aspx" />
To fix certain errors, the web.config file for the website can be manually edited. enablerHost, enablerDomain, enablerUserName and enablerPassword must be correct.
To fix certain errors, the web.config file for the website can be manually edited. enablerHost, enablerDomain, enablerUserName and enablerPassword must be correct.

Portal Updating Wrong Company

If it looks like the portal is adding data or updating data in the wrong SAP Business One company, then the portal itself may be configured to point to the wrong company. In this case, change the company configuration settings to point to the right company.

  • Look for a section called <appSettings ... > There will be a subsection called <add key="b1company" value="TestCompany">. Make sure the ‘value’ is the correct company.</p>

Object reference not set to an instance of an object

This error can occur under many situations, so in order to figure out the cause, the stack trace details are required

zedSuite.BLL.Objects.BaseConfig`1.GetUserCurrencyType(String userCurrencyCode)

The following screenshot shows an error that is caused by the ISO code not being set on the currency in SAP Business One. See Configuring Currency ISO Codes for instructions.

This error is due to currency ISO codes not being set in SAP Business One.
This error is due to currency ISO codes not being set in SAP Business One.

License Metadata Errors

During licensing of a Portal with the License Administration section of Vision33 Server Tools, errors may occur which result in a pop-up error message. Below are some known errors and their resolutions.

License Metadata Error: Error adding custom queries / Could not commit transaction

Symptom: The following error occurs in Vision33 Server Tools License Administration screen after pressing the check-box to install a license and pressing ‘yes’ to install metadata. An error window appears over the License Administration screen which states:

zedSuite Portal Meta data installation failed with error : Error
adding custom queries: V33_AddonConfig.InstallCustomQueries
failed: Could not commit transaction
Error occurs after checking the Used column during license installation.
Error occurs after checking the Used column during license installation.

Cause: This error is a generic SQL error on the SAP Business One database. However, it is usually caused by a SQL error in a stored procedure, such as SBO_SP_TransactionNotification or SBO_SP_PostTransactionNotice.

Resolution: This error can sometimes be resolved by correcting underlying SQL errors in the stored procedure. Speak with your SAP Business One Partner if you suspect this is the case.

Error: Please check the following: -10 - Update the exchange rate

Symptom: The following error message is displayed when a customer with a foreign currency attempts to create an order using Order Pad for Customer Portal.

Error dialogue: Update the exchange rate
Error dialogue: Update the exchange rate

Cause: This error is displayed when multi-currency is enabled, but exchange rates are not set up for the customer’s assigned currency. This is seen in order pad when the customer places an order with a foreign currency with unconfigured exchange rates or exchange rates that are not applicable to the current date.

Resolution: Configure exchange rates for the current date, and the customer’s foreign currency. See SAP documentation for setting up exchange rates: help.sap.com/saphelp_sbo882/helpdata/en/45/070df2e02641dfe10000000a1553f6/content.htm

Extensionless URLs aren’t working

If extension-less requests are not working in IIS7, Microsoft provides a patch for IIS7 that must be installed on the web server to support Customer Portal, Employee Portal or Vendor Portal websites: http://support.microsoft.com/kb/980368