Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
HTML SBM Version Diff
Differences Between Versions ... +112, 14 @@ ... :52: 14 .000000000 ... 04-12 14 :13: ... ... :07: 14 .000000000 ... "\f 14 a"} ... "\f 14 b"} ... \f 14 c"} ... "\f 14 d"} ... "\f 14 e"} ... ... normal normal normal 14 px/1 ... ... "\f 14 a"} ... "\f 14 b"} ... "\f 14 c"} ...
CMS-XML How to check if SBM is 32-bit or 64-bit
One way to check if the installed version of SBM is 32-bit or 64-bit is to check the Task Manager or the "Program Files\Serena\SBM\Common\jboss405\bin" directory to see if there is a jbosssvc.exe (for 32-bit) or jbosssvc64.exe (for 64-bit).
CMS-XML Upgrading SBM from Windows 32-bit to 64-bit
Custom install that installs one or more SBM
CMS-XML Webservices Examples not installed with 64 bit version of SBM
The documentation states the WS examples should be installed in <SBM Install Folder>\Application Engine\webservices\. With the 32 bit installer this is correct, however when installing the 64 bit version of SBM the examples ( are missing.
CMS-XML Login to SBM fails: SBM gsoap application pool inadvertently changes from 64-bit to 32-bit
On 64-bit servers, if the Application Pool Defaults value in IIS is changed to 32-bit (either by an administrator or by another installed application), then the next time you apply changes in SBM Configurator, the dedicated gsoap application pool will also change to 32-bit mode (Configurator sets gsoap to match the default when you click Apply
CMS-XML Setting the Default Java Heap Size on Windows 2003 and Windows 2008 32-bit
SBM 10.1.5.X and earlier versions are supported on 32-bit systems (2003 and 2008); however, if possible, Serena recommends hosting JBoss on a 64-bit server with at least 8GB of available RAM. If you cannot install the JBoss components on one or more 64-bit servers, Serena recommends that you distribute the JBoss components on multiple servers, and that your 32-bit servers have at least 4GB of RAM available.
CMS-XML SBM Installer rolls back after a certain point and SBM 2009 R4 x64 is not installed
Whilst 2009 R4 is the first release of 64-bit SBM it has been found that some sites had managed to get the 32-bit version installed by switching IIS compatability mode on. This was never a supported installation but if this did occur then when you attempt to upgrade to SBM 2009 R4 x64, the installer will begin to install, but then roll-back your installation and SBM 2009 R4 x64 will not be installed.
CMS-XML SBM 11.2 Hotfix 3 - Composer full installation for DEF305103 DEF305144 DEF300505
3. Follow the instructions in the resulting text file. NOTE: The hotfix is alternatively also available with the SSM 5.3 installation on the SSM Application Engine server - copy the 32-bit or 64-bit client installers to each client machine from here: : ...installDir\SSM\Hotfixes\BM11_2_HF3
CMS-XML Updating SQL Server Databases to Use BIGINT Data Type
As of SBM 11.5, the data type for all TS_ID columns in the Application Engine database changed from 32-bit INT to 64-bit BIGINT for all new installations . This means that the TS_ID column is no longer limited to a maximum of 2.1 billion rows.
CMS-XML Error: Calling LoadLibraryEx on ISAPI filter "C:\Program Files\Serena\SBM\Application Engine\bin\isapi_redirect.dll" failed
this could be because the other product has changed some IIS settings on the application pool. Typcially this has been seen when SBM 64-bit has been installed and then a 32-bit application was installed and the app pool settings changed to be 32-bit . Separate the products to use different IIS application pools in this case and ensure that the one that 64-bit SBM is using is enabled for 64-bit and not 32-bit.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs