Topics started by Andrew D'Antonio

20 Topics

A
Hero (Employee)
Andrew D'AntonioHero (Employee)
posted in Alliance

Object reference not set to an instance of an object. at Astea.AO.Version.GetCustomizationServerVersion()

I recently ran into an error in my development environment after applying v15 HF6 files and wasn’t able to log in.  The error was “Object reference not set to an instance of an object. at Astea.AO.Version.GetCustomizationServerVersion()”. After reviewing the changes, I realized that I needed to run Sync Templates in Configuration editor followed by IISReset to add the “Version” property to the customizations setting.I hope this helps anyone that runs into a similar error.

1
Phil Seifert
Ultimate Hero (Employee)
3 months ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
posted in Alliance

Solution: Error accessing Schema Generator over HTTPS in 15.4

A customer recently reported an XML/JSON error while trying to access the Schema Generator and Export Template Wizard modules in the web browser version of Alliance (15.4).  After investigating the issue, it was determined that the HTTPS binding was missing from the Web_WCFServices_SSL.config.  This issue will be resolved in 15.4 SU5.Screenshot of issue:In the meantime, this issue can be resolved by adding the binding to Bin\Web_WCFServices_SSL.config: <service name="Astea.EO.SchemaGenerator.SchemaGeneratorService" behaviorConfiguration="CustomServiceBehavior"> <endpoint address="dotnetssl" binding="basicHttpBinding" bindingConfiguration="SSL" name="simpleSSL" contract="Astea.AO.Interfaces.Contracts.ISchemaGeneratorService" /> <endpoint address="dotnet" binding="basicHttpBinding" bindingConfiguration="NoSSL" name="simple" contract="Astea.AO.Interfaces.Contracts.ISchemaGeneratorService" /> <endpoint address="" binding="webHttpBinding" bindingConfiguration=

0
A
Hero (Employee)
1 year ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
published in Alliance

Solution for BI Error "The DELETE statement conflicted with the REFERENCE constraint "FK_fact_item_warranties_fact_items""

Recently, we’ve had a few issues in which the BI Cube is red, meaning the BI Increment Load failed for some reason.  If the reason for failure is the following error, we have a common data fix to correct the issue.Error: The DELETE statement conflicted with the REFERENCE constraint "FK_fact_item_warranties_fact_items". The conflict occurred in database "AsteaBIProduction_DW", table "dbo.fact_item_warranties", column 'dim_item_key'. To fix this issue, first run the following select query on the Data Warehouse database to check if there are any records where the referenced item ID doesn’t exist:select * from fact_item_warranties where fact_item_warranties.dim_item_key in (select item_id from item_Deleted);If the above query returns any results, please run the following query against the same Data Warehouse database:update fact_item_warranties set dim_item_key = -1 where fact_item_warranties.dim_item_key in (select item_id from item_Deleted);If the above mentioned error is the only error

921
A
Hero (Employee)
1 year ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
posted in Alliance

Report Export path Restriction in 15.3 HF3

We recently came across an issue with a customization that was developed for a client where invoice reports are exported to the system temp directory prior to uploading to an external system.  After upgrading this client to 15.3 HF3, the custom functionality stopped working and reports weren't being generated.After further review, we found that in 15.3 HF3, a change was implemented to improve security of the application by disallowing reports to be exported to any directory other than the FileStoragePath defined in the global XML.Once we updated the customization code to write the reports to the FileStoragePath location, the functionality begin working again.  Please keep this change in mind when upgrading clients to 15.3 HF3 and if any custom functionality like this exists in their codebase.

0
A
Hero (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
posted in Alliance

Changing User E-Mail Address in Alliance

There are cases where you may want to update the e-mail address on your employee record in Alliance.  Usually, this can be done by system administrators via the Employee module; however, as an end-user, you most likely will not have access to this module.  In the case that an end-user needs to update their e-mail address or other information in Alliance, this is done via the “My Profile” module.Launch the My Profile module. Modify the e-mail address (or any other information that needs to be changed). Click Save.

1
R
Do Gooder (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
posted in Alliance

Solution: BI Incremental Load Failure (fact_inventory_daily)

At the start of the new year, a few customers reported that BI is not updating during the scheduled incremental load.  We found that the reason is the new year dates are missing from the dim_dates table in the BI data warehouse.  The issue can be identified with the following error in the ETL log:The INSERT statement conflicted with the FOREIGN KEY constraint "FK_dim_inv_versions_dim_date". The conflict occurred in database "AsteaBIAllvotec_Production_DW", table "dbo.dim_date", column 'dim_date_key'.To populate the dates, the following stored procedure can be executed.  The following example will populate the dates for the year 2022:EXECUTE sp_dim_date_populate '2022';GOAfter the stored procedure is executed, the incremental load job can be reprocessed.

0
A
Hero (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
posted in Alliance

Dispatch Console Troubleshooting (Update Password)

We ran into an issue on our staging environment for a V14 client where the Dispatch Console was disconnected.  To troubleshoot this, I performed the following actions:Check the DSE Event Log in Windows Event Viewer for errors. The following error was logged:Message body:Failed to load profile QASTG.Method Name: WriteErrorToLogFile Name: SessionManagerLine Number:49Exception details begin:------------Astea.Common.Exception.AsteaLoginFailedException: LOGIN_FAILED ---> System.Exception: Astea inner exception   --- End of inner exception stack trace ---   at Astea.Web.AsteaDSEService.Login(String ProfileName, String User, String Password, String loginKey)   at Astea.DSE.AsteaDSEServiceProxy.Login(String ProfileName, String User, String Password, String loginKey)   at Astea.DSE.Loader.DatabaseConnector.Login()   at Astea.DSE.Loader.Profile..ctor(String p_profileName, String p_username, String p_password, ServerAddress p_serverAddress, Action`2 p_profileValidityHandler, Func`2 p_getProfil

0
A
Hero (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
posted in Alliance

Another save transaction currently executing in CustomizationManager module

I was importing a customization into Alliance and the import was interrupted.  When I tried to re-import, I received the message: “Another save transaction currently executing in CustomizationManager module”To fix this, I went to the database and run the following SQL command to remove the lock.delete from ap_lock_global where ap_table_key = 'CustomizationManager';After doing so, I was able to import the customization.

0
A
Hero (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
posted in Alliance

Redis Config: Fixing Cannot Write to Read-Only Slave Error Message / Issues with DSE/DC and Mobile

When the Dispatch Console automatic updates stop working or mobile cannot connect to the cache service, it may be because of a misconfiguration in Redis cache.  If you take a look at the event log and see that the error is “Fixing Cannot Write to Read-Only Slave", the following steps will resolve the issue:On each server, stop Internet Information Services (IIS), the Astea Cache Service, and the Astea Monitoring Service. On each server, backup the redis.windows.conf and redis-sentinal.conf files located in the Bin sub-directory of the Astea Alliance installation directory.  (ie. C:\Program Files\Astea Alliance 14.0\Bin\redis.windows.conf) On each server, Using WordPad or Notepad++, open the redis.windows.conf file and redis-sentinal.conf file as administrator and remove the contents under the section # Generated by CONFIG REWRITE.Example of line to remove: On each server, open the Web.config as administrator located in the ServiceBus sub-directory of the Astea Alliance installation dir

1
Luis Aguero
Sidekick (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
posted in Alliance

Reading Stack Trace Information to Determine Root of Alliance Issues

In this example, the user performed some actions in alliance and received the following validation message:We can determine that this is a validation message and not an error because of the code defined in the title of the message “A2SET072”.  Validation messages are programmed into the application to prevent bad data from being entered into the database or to stop the user from performing actions that they do not have permissions to do.  Validation messages that are raised by the server are shown in the application event log as shown below:The stack trace is defined in the application log.  The stack trace shows the commands (functions) that occurred prior to the validation message\error.   Looking in this log, we can see that the last function call prior to Astea.AOGenericModule.ErrorRaise is Astea.BO.pm_sched_dates_Astea.CheckDuplicatePMdatesRows().  This information assists support in determining exactly the line(s) of code that are causing the problem.When an error is raised by th

0
A
Hero (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
posted in Alliance

Order Changes Log Table

I just learned today that in V15, changes to service orders are stored in the order_changes_log (Active) and c_order_changes_log (History) tables.In previous versions of Alliance, these changes were stored in the demand (Active) and demand_done (History) tables and can be retrieved with the following queries:select * from demand with (nolock) where demand.order_id = 'Order ID' and bpart_gcl_id = 'Mngt';select * from demand_done with (nolock) where demand.order_id = 'Order ID' and bpart_gcl_id = 'Mngt';For V15 and later, the Trans. Log entries can be found with the following:select * from order_changes_log with (nolock) where order_id = 'Order ID'select * from c_order_changes_log with (nolock) where order_id = 'Order ID' 

3
Y
Do Gooder (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
asked in Alliance

SQL Query - Linked IMO Demand Info from Order ID

I’ve written this query quite a few times recently and wanted to share it in-case anyone needs to do something similar either in on-prem DB analysis, reports, or in process flow.This query shows the link between a Service Order material demand and its associated Internal Material Order material demand that is created from returning the part to another warehouse.-- Get Linked IMO Demand ID and IMO ID from Order ID.select o.order_id, dm.demand_id, dmrd.demand_id, lo.logistic_order_id from order_line o with (nolock) -- Orderinner join demand_material dm with (nolock) inner join demand_mtrl_return dmr with (nolock) inner join demand_material dmrd with (nolock) inner join logistic_order lo with (nolock) on lo.logistic_order_id = dmrd.request_id -- Return IMO Order on dmrd.rb_request_type = 'L' and CONVERT(varchar, dmrd.demand_id) = dmr.request_id -- Linked Demand on return IMO on dmr.demand_id = dm.demand_id -- Order's material return information on dm.order_id = o.order_

0
A
Hero (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
posted in Alliance

Lookup Shortcuts

Just wanted to share a tip re/ data entry within Alliance.  When the focus is in a lookup field in Alliance, pressing F2 on the keyboard will launch the lookup window for that field.  While the lookup window is open, pressing CTRL+SHIFT+ENTER on the keyboard will select the highlighted record and close the lookup window.  

4
F
Do Gooder (Customer)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
asked in Alliance

Re-Running DB Upgrade Scripts

There may be times when an additional database needs to be upgraded after a patch installation, but the installer is already closed.  Administrators can perform the DB upgrade again by adding an empty text file named “dbupgrade.txt” to the same directory as the installation.  In this case, the installer will skip updating files and only prompt to run scripts against the database. Example:Upon running the installer, a prompt will display showing that it is in DB Upgrade mode.  After following the on-screen prompts, the installer will copy only the SQL scripts to the Alliance directory and run them accordingly against the database connection provided.

0
A
Hero (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
published in Alliance

Users not receiving e-mails during password initialization

A client reported earlier this week that during password initialization, the user was not receiving an e-mail confirmation of the password change.  I found that the system will only send an e-mail to the user if the “Show password on Password Initialization” check box is un-checked in the “Security SOX” module.  

700
A
Hero (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
published in Alliance

Alliance Installation Error - Global.xml in the shared folder is in use by another program.

Recently during an installation, we encountered the error “Global.xml in the shared folder is in use by another program...” The Global.xml; however, was not in use.  After researching the issue, it appeared that the Global XML templates were not synchronized, so the installer could not update the global.xml.  After synchronizing the global XML templates via the Configuration Editor utility, the installation was successful. To synchronize the XML templates:Open configuration editor. Click the “Synchronize with all templates” button. Click Save.

301
A
Hero (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
published in Alliance

Alliance 14.0.0.24 and TLS 1.2/SSO Application Address not valid

When using TLS 1.2 with Single Sign-on (SSO), users running Alliance 14.0.0.24 may encounter the following error that the “Astea Application address is not valid.”  If this happens, it may be because the 64-bit Publisher with TLS 1.2 support has not been installed on the Publisher server(s).  Please check the publisher server to ensure that publisher was installed using Alliance Publisher 14.0.0.24 Full (x64).exe.We recently had a client that utilizes TLS 1.2 and SSO and received this error after re-installing publisher.  This was because the server only supported TLS 1.2; however, the 32-bit version of Publisher was installed without TLS 1.2 support.   The client browser could not establish a connection with the server to verify the Alliance URL and as a result, the following error was displayed:  To resolve the issue, the client uninstalled Publisher from the publisher servers and re-installed using the 64-bit version with added TLS 1.2/SSO support.

600
A
Hero (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
posted in Alliance

Viewing Application Events for Hosted Solutions

​Clients using the hosted Alliance solution can view application error logs via the Log Viewer module in the Alliance Employee Portal.  This can be achieved by disabling Event Log logging mode.Steps to enable database-level event logging:Navigate to the Configuration Editor module Click the Configuration > Globals section Set IsEventLogLoggingMode to False Click the save iconSteps to view and export application events:Navigate to the Log Viewer module Click the Refresh button to refresh the log The log can be exported using the “Export” button and if necessary, sent to IFS Alliance Support.​

4
A
Hero (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
published in Alliance

Controlling Overlapping Activities in Time Sheets

In Alliance V15, overlapping activities can be controlled at both the application level and at the node level for the node associated with the time sheet.  Time sheet options defined at a node level will override the application level settings.To allow/disallow overlapping activities at the application level:Navigate to Time and Expense Options To allow activities to overlap application-wide, check the “Allow activities to overlap” checkbox.  Alternatively, this setting can be left unchecked to restrict overlapping activities at the application level Overlapping activities can also be controlled at the Node level.  To define time sheet options for a specific node:Navigate to the Node module. On the left-side navigation panel, click “Time Sheet Options” Check the “Define Time Sheet Options” checkbox to override the global settings.  This will override the settings defined in the Time and Expense Options module. Check the “Allow activities to overlap” checkbox to allow overlapping activi

470
A
Hero (Employee)
2 years ago
A
Hero (Employee)
Andrew D'AntonioHero (Employee)
published in Alliance

"Escalation" module renamed to "Workflow (D\C)" in V15

Historically, escalation rules were contained in the Escalation module.  With the introduction of the Process Flow module in V15, the Escalation module has been renamed to Workflow (D/C).  The Workflow (D/C) module can be accessed within the Alliance Employee Portal and is not yet available in the browser-based version of Alliance.To access escalation rules in Alliance V15:Log into the Alliance Employee Portal. In the Find text box, enter “Workflow (D/C)” and press enter or click the “Go” button. 

540
A
Hero (Employee)
2 years ago

Badges

Show all badges
Terms & ConditionsCookie settings