SYMPTOM:
Consider the case of a Strategy Narrowcast Server 10.x configured with the following services:
HOME_PATH, where HOME_PATHis the directory that you specified as the home directory during installation. —Browse to the folder binand type ./mstrconnectwiz, and then press ENTER. The Welcome page of the Connectivity Wizardopens. •On UNIX or Linux from the command line, then perform the following steps: —From a UNIX/Linux console window, browse to HOME_PATH, where HOME_PATHis the directory that you specified as the home directory during installation. —Browse to the folder binand type ./mstrconnectwiz -h, and then press ENTER. 2Click Next. A list of database drivers is displayed. The list available for Windows is different than the list available for UNIX/Linux. For a list of the available ODBC drivers for Windows, Solaris, AIX, HP-UX, and Redhat or SUSE Linux that are certified for Intelligence Server and different DBMS types, see Certified ODBC drivers for MicroStrategy Intelligence Server. 3Select a database driver with which to create a DSN and click Next. The Driver Details page opens. 4Enter the information in the appropriate fields for connecting with the selected database driver. The information to enter varies depending on the database platform that you selected. For more information, see Creating DSNs for specific data sources. 5Click Test to verify the connection. The Test Connection dialog box opens. 6Enter the User Name and Password to connect to the database. 7Click Connect to test and verify the connection. If the test is performed successfully, the connection with the database is established. If the test fails, verify the correct connection information with your database administrator and make any required changes to the information you provided in the previous steps. 8Click Close, and then Finish to create the new DSN. ▫Select Yes to make sure the DSN points to the location you are expecting. This overwrites the existing DSN. ▫Select No to save the DSN with a different name. 9Repeat the above steps to create as many DSNs as you require. At a minimum, create one for your metadata and one for your warehouse. •It is strongly recommended that you use the Connectivity Wizard when creating a new DSN for a Strategy-branded ODBC Driver. Use the Microsoft ODBC Data Source Administrator only if you intend to use a non-Strategy driver. •If you choose to create DSNs using the Microsoft ODBC Data Source Administrator, they must be system DSNs. Otherwise, Strategy interfaces cannot recognize them. 1Log in to the machine as an administrator. This gives you the ability to create a system-wide DSN, rather than a user-specific DSN. 2In most Windows systems you can access the ODBC Data Source Administrator from the Control Panel. Refer to your third-party Microsoft documentation for steps to access the ODBC Data Source Administrator tool. 3Click the System DSN tab. A list displays all the existing system data sources and their associated drivers. 4Click Add. The Create New Data Source dialog box opens. 5Select the desired driver and click Finish. A driver setup dialog box is displayed. 6Enter the information in the appropriate fields to create a data source for the selected database driver. 7Click OK to create a new DSN.9 p.m.Service 110 p.m.Service 211 p.m.Service 3 |
HOME_PATH, where HOME_PATHis the directory that you specified as the home directory during installation. —Browse to the folder binand type ./mstrconnectwiz, and then press ENTER. The Welcome page of the Connectivity Wizardopens. •On UNIX or Linux from the command line, then perform the following steps: —From a UNIX/Linux console window, browse to HOME_PATH, where HOME_PATHis the directory that you specified as the home directory during installation. —Browse to the folder binand type ./mstrconnectwiz -h, and then press ENTER. 2Click Next. A list of database drivers is displayed. The list available for Windows is different than the list available for UNIX/Linux. For a list of the available ODBC drivers for Windows, Solaris, AIX, HP-UX, and Redhat or SUSE Linux that are certified for Intelligence Server and different DBMS types, see Certified ODBC drivers for MicroStrategy Intelligence Server. 3Select a database driver with which to create a DSN and click Next. The Driver Details page opens. 4Enter the information in the appropriate fields for connecting with the selected database driver. The information to enter varies depending on the database platform that you selected. For more information, see Creating DSNs for specific data sources. 5Click Test to verify the connection. The Test Connection dialog box opens. 6Enter the User Name and Password to connect to the database. 7Click Connect to test and verify the connection. If the test is performed successfully, the connection with the database is established. If the test fails, verify the correct connection information with your database administrator and make any required changes to the information you provided in the previous steps. 8Click Close, and then Finish to create the new DSN. ▫Select Yes to make sure the DSN points to the location you are expecting. This overwrites the existing DSN. ▫Select No to save the DSN with a different name. 9Repeat the above steps to create as many DSNs as you require. At a minimum, create one for your metadata and one for your warehouse. •It is strongly recommended that you use the Connectivity Wizard when creating a new DSN for a Strategy-branded ODBC Driver. Use the Microsoft ODBC Data Source Administrator only if you intend to use a non-Strategy driver. •If you choose to create DSNs using the Microsoft ODBC Data Source Administrator, they must be system DSNs. Otherwise, Strategy interfaces cannot recognize them. 1Log in to the machine as an administrator. This gives you the ability to create a system-wide DSN, rather than a user-specific DSN. 2In most Windows systems you can access the ODBC Data Source Administrator from the Control Panel. Refer to your third-party Microsoft documentation for steps to access the ODBC Data Source Administrator tool. 3Click the System DSN tab. A list displays all the existing system data sources and their associated drivers. 4Click Add. The Create New Data Source dialog box opens. 5Select the desired driver and click Finish. A driver setup dialog box is displayed. 6Enter the information in the appropriate fields to create a data source for the selected database driver. 7Click OK to create a new DSN.9 p.m.Service 110 p.m.Service 211 p.m.Service 3 |
HOME_PATH, where HOME_PATHis the directory that you specified as the home directory during installation. —Browse to the folder binand type ./mstrconnectwiz, and then press ENTER. The Welcome page of the Connectivity Wizardopens. •On UNIX or Linux from the command line, then perform the following steps: —From a UNIX/Linux console window, browse to HOME_PATH, where HOME_PATHis the directory that you specified as the home directory during installation. —Browse to the folder binand type ./mstrconnectwiz -h, and then press ENTER. 2Click Next. A list of database drivers is displayed. The list available for Windows is different than the list available for UNIX/Linux. For a list of the available ODBC drivers for Windows, Solaris, AIX, HP-UX, and Redhat or SUSE Linux that are certified for Intelligence Server and different DBMS types, see Certified ODBC drivers for MicroStrategy Intelligence Server. 3Select a database driver with which to create a DSN and click Next. The Driver Details page opens. 4Enter the information in the appropriate fields for connecting with the selected database driver. The information to enter varies depending on the database platform that you selected. For more information, see Creating DSNs for specific data sources. 5Click Test to verify the connection. The Test Connection dialog box opens. 6Enter the User Name and Password to connect to the database. 7Click Connect to test and verify the connection. If the test is performed successfully, the connection with the database is established. If the test fails, verify the correct connection information with your database administrator and make any required changes to the information you provided in the previous steps. 8Click Close, and then Finish to create the new DSN. ▫Select Yes to make sure the DSN points to the location you are expecting. This overwrites the existing DSN. ▫Select No to save the DSN with a different name. 9Repeat the above steps to create as many DSNs as you require. At a minimum, create one for your metadata and one for your warehouse. •It is strongly recommended that you use the Connectivity Wizard when creating a new DSN for a Strategy-branded ODBC Driver. Use the Microsoft ODBC Data Source Administrator only if you intend to use a non-Strategy driver. •If you choose to create DSNs using the Microsoft ODBC Data Source Administrator, they must be system DSNs. Otherwise, Strategy interfaces cannot recognize them. 1Log in to the machine as an administrator. This gives you the ability to create a system-wide DSN, rather than a user-specific DSN. 2In most Windows systems you can access the ODBC Data Source Administrator from the Control Panel. Refer to your third-party Microsoft documentation for steps to access the ODBC Data Source Administrator tool. 3Click the System DSN tab. A list displays all the existing system data sources and their associated drivers. 4Click Add. The Create New Data Source dialog box opens. 5Select the desired driver and click Finish. A driver setup dialog box is displayed. 6Enter the information in the appropriate fields to create a data source for the selected database driver. 7Click OK to create a new DSN.9 p.m.Service 110 p.m.Service 211 p.m.Service 3 |
HOME_PATH, where HOME_PATHis the directory that you specified as the home directory during installation. —Browse to the folder binand type ./mstrconnectwiz, and then press ENTER. The Welcome page of the Connectivity Wizardopens. •On UNIX or Linux from the command line, then perform the following steps: —From a UNIX/Linux console window, browse to HOME_PATH, where HOME_PATHis the directory that you specified as the home directory during installation. —Browse to the folder binand type ./mstrconnectwiz -h, and then press ENTER. 2Click Next. A list of database drivers is displayed. The list available for Windows is different than the list available for UNIX/Linux. For a list of the available ODBC drivers for Windows, Solaris, AIX, HP-UX, and Redhat or SUSE Linux that are certified for Intelligence Server and different DBMS types, see Certified ODBC drivers for MicroStrategy Intelligence Server. 3Select a database driver with which to create a DSN and click Next. The Driver Details page opens. 4Enter the information in the appropriate fields for connecting with the selected database driver. The information to enter varies depending on the database platform that you selected. For more information, see Creating DSNs for specific data sources. 5Click Test to verify the connection. The Test Connection dialog box opens. 6Enter the User Name and Password to connect to the database. 7Click Connect to test and verify the connection. If the test is performed successfully, the connection with the database is established. If the test fails, verify the correct connection information with your database administrator and make any required changes to the information you provided in the previous steps. 8Click Close, and then Finish to create the new DSN. ▫Select Yes to make sure the DSN points to the location you are expecting. This overwrites the existing DSN. ▫Select No to save the DSN with a different name. 9Repeat the above steps to create as many DSNs as you require. At a minimum, create one for your metadata and one for your warehouse. •It is strongly recommended that you use the Connectivity Wizard when creating a new DSN for a Strategy-branded ODBC Driver. Use the Microsoft ODBC Data Source Administrator only if you intend to use a non-Strategy driver. •If you choose to create DSNs using the Microsoft ODBC Data Source Administrator, they must be system DSNs. Otherwise, Strategy interfaces cannot recognize them. 1Log in to the machine as an administrator. This gives you the ability to create a system-wide DSN, rather than a user-specific DSN. 2In most Windows systems you can access the ODBC Data Source Administrator from the Control Panel. Refer to your third-party Microsoft documentation for steps to access the ODBC Data Source Administrator tool. 3Click the System DSN tab. A list displays all the existing system data sources and their associated drivers. 4Click Add. The Create New Data Source dialog box opens. 5Select the desired driver and click Finish. A driver setup dialog box is displayed. 6Enter the information in the appropriate fields to create a data source for the selected database driver. 7Click OK to create a new DSN.9 p.m.Service 110 p.m.Service 211 p.m.Service 3 |
HOME_PATH, where HOME_PATHis the directory that you specified as the home directory during installation. —Browse to the folder binand type ./mstrconnectwiz, and then press ENTER. The Welcome page of the Connectivity Wizardopens. •On UNIX or Linux from the command line, then perform the following steps: —From a UNIX/Linux console window, browse to HOME_PATH, where HOME_PATHis the directory that you specified as the home directory during installation. —Browse to the folder binand type ./mstrconnectwiz -h, and then press ENTER. 2Click Next. A list of database drivers is displayed. The list available for Windows is different than the list available for UNIX/Linux. For a list of the available ODBC drivers for Windows, Solaris, AIX, HP-UX, and Redhat or SUSE Linux that are certified for Intelligence Server and different DBMS types, see Certified ODBC drivers for MicroStrategy Intelligence Server. 3Select a database driver with which to create a DSN and click Next. The Driver Details page opens. 4Enter the information in the appropriate fields for connecting with the selected database driver. The information to enter varies depending on the database platform that you selected. For more information, see Creating DSNs for specific data sources. 5Click Test to verify the connection. The Test Connection dialog box opens. 6Enter the User Name and Password to connect to the database. 7Click Connect to test and verify the connection. If the test is performed successfully, the connection with the database is established. If the test fails, verify the correct connection information with your database administrator and make any required changes to the information you provided in the previous steps. 8Click Close, and then Finish to create the new DSN. ▫Select Yes to make sure the DSN points to the location you are expecting. This overwrites the existing DSN. ▫Select No to save the DSN with a different name. 9Repeat the above steps to create as many DSNs as you require. At a minimum, create one for your metadata and one for your warehouse. •It is strongly recommended that you use the Connectivity Wizard when creating a new DSN for a Strategy-branded ODBC Driver. Use the Microsoft ODBC Data Source Administrator only if you intend to use a non-Strategy driver. •If you choose to create DSNs using the Microsoft ODBC Data Source Administrator, they must be system DSNs. Otherwise, Strategy interfaces cannot recognize them. 1Log in to the machine as an administrator. This gives you the ability to create a system-wide DSN, rather than a user-specific DSN. 2In most Windows systems you can access the ODBC Data Source Administrator from the Control Panel. Refer to your third-party Microsoft documentation for steps to access the ODBC Data Source Administrator tool. 3Click the System DSN tab. A list displays all the existing system data sources and their associated drivers. 4Click Add. The Create New Data Source dialog box opens. 5Select the desired driver and click Finish. A driver setup dialog box is displayed. 6Enter the information in the appropriate fields to create a data source for the selected database driver. 7Click OK to create a new DSN.9 p.m.Service 110 p.m.Service 211 p.m.Service 3 |
HOME_PATH, where HOME_PATHis the directory that you specified as the home directory during installation. —Browse to the folder binand type ./mstrconnectwiz, and then press ENTER. The Welcome page of the Connectivity Wizardopens. •On UNIX or Linux from the command line, then perform the following steps: —From a UNIX/Linux console window, browse to HOME_PATH, where HOME_PATHis the directory that you specified as the home directory during installation. —Browse to the folder binand type ./mstrconnectwiz -h, and then press ENTER. 2Click Next. A list of database drivers is displayed. The list available for Windows is different than the list available for UNIX/Linux. For a list of the available ODBC drivers for Windows, Solaris, AIX, HP-UX, and Redhat or SUSE Linux that are certified for Intelligence Server and different DBMS types, see Certified ODBC drivers for MicroStrategy Intelligence Server. 3Select a database driver with which to create a DSN and click Next. The Driver Details page opens. 4Enter the information in the appropriate fields for connecting with the selected database driver. The information to enter varies depending on the database platform that you selected. For more information, see Creating DSNs for specific data sources. 5Click Test to verify the connection. The Test Connection dialog box opens. 6Enter the User Name and Password to connect to the database. 7Click Connect to test and verify the connection. If the test is performed successfully, the connection with the database is established. If the test fails, verify the correct connection information with your database administrator and make any required changes to the information you provided in the previous steps. 8Click Close, and then Finish to create the new DSN. ▫Select Yes to make sure the DSN points to the location you are expecting. This overwrites the existing DSN. ▫Select No to save the DSN with a different name. 9Repeat the above steps to create as many DSNs as you require. At a minimum, create one for your metadata and one for your warehouse. •It is strongly recommended that you use the Connectivity Wizard when creating a new DSN for a Strategy-branded ODBC Driver. Use the Microsoft ODBC Data Source Administrator only if you intend to use a non-Strategy driver. •If you choose to create DSNs using the Microsoft ODBC Data Source Administrator, they must be system DSNs. Otherwise, Strategy interfaces cannot recognize them. 1Log in to the machine as an administrator. This gives you the ability to create a system-wide DSN, rather than a user-specific DSN. 2In most Windows systems you can access the ODBC Data Source Administrator from the Control Panel. Refer to your third-party Microsoft documentation for steps to access the ODBC Data Source Administrator tool. 3Click the System DSN tab. A list displays all the existing system data sources and their associated drivers. 4Click Add. The Create New Data Source dialog box opens. 5Select the desired driver and click Finish. A driver setup dialog box is displayed. 6Enter the information in the appropriate fields to create a data source for the selected database driver. 7Click OK to create a new DSN.9 p.m.Service 110 p.m.Service 211 p.m.Service 3 |
However, the contents from those services arrive between 7 a.m. and 9 a.m. the next day. Some of the services may fail to deliver messages entirely.
CAUSE:
A possible cause of this issue is the following combination of factors:
In the scenario, Service 1 begins executing on time, but then times out one hour later. Because the maximum failover count has not been reached, that segment is placed back in the execution queue and the segment begins to re-execute immediately.
At the same time, Service 2 begins to execute. Because the Execution Engine's configuration allows only one executing segment at a time, the segment is placed in a waiting status for the Execution Engine to become free. Service 1, however, times out again, so Service 2 never gets a chance to execute. Its segments also time out one hour later, by which time Service 1 has failed over again, leaving no available segment executors for Service 2.
This process will continue until the maximum failover count for the Strategy Narrowcast Server f8.x system is reached. The default failover count is 10, which accounts for the long time lag between service onset and delivery.
This scenario may be detected in the Delivery Engine log by the repeated presence of the following error message:
Service execution rejected due to too many concurrent service executions already
12748
