AXForum  
Вернуться   AXForum > Microsoft Dynamics AX > DAX Blogs
All
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 13.11.2009, 21:05   #1  
Blog bot is offline
Blog bot
Участник
 
25,617 / 848 (80) +++++++
Регистрация: 28.10.2006
emeadaxsupport: Error during Hotfix installation - "Version string portion was too short or too long"
Источник: http://blogs.msdn.com/emeadaxsupport...-too-long.aspx
==============

Recently we had a problem when installing a Hotfix for AX 2009.
The installation stopped with an error and we could find the following information in the setup log:

=== Starting execution phase ===
Starting the Microsoft Dynamics AX Client executable: C:\Program Files (x86)\Microsoft Dynamics AX\50\Client\bin\ax32.exe "-regconfig=Ax2009myConfig" "-logdir=C:\Documents and Settings\All Users\Application Data\Microsoft\Dynamics AX\Dynamics AX Setup Logs\2009-10-21 12-37-06" "-startupcmd=autorun_C:\Documents and Settings\All Users\Application Data\Microsoft\Dynamics AX\Dynamics AX Setup Logs\2009-10-21 12-37-06\GetVersionInformation.xml"
Exception: System.ArgumentException

Message: Version string portion was too short or too long.

FullText: System.ArgumentException: Version string portion was too short or too long.
at System.Version..ctor(String version)
at Microsoft.Dynamics.Setup.InstallApplicationHotfix.ProcessVersionInformation(String logFilename, String versionFilename)
at Microsoft.Dynamics.Setup.InstallApplicationHotfix.FillHotfixUpdateFilesList()
at Microsoft.Dynamics.Setup.MainForm.DependencyValidation()
at Microsoft.Dynamics.Setup.MainForm.PreInstall()
at Microsoft.Dynamics.Setup.MainForm.s250Timer_Tick()

==== Setup encountered an unhandled exception and could not be completed. For details see the previous messages in the log. ===

What was the problem?

The important information was:

FullText: System.ArgumentException: Version string portion was too short or too long.
The AX Hotfix Installer is checking the AX version during the installation to ensure only valid fixes will be installed.
For this it is calling the following method within AX:

ApplicationVersion/BuildNo()

We then found out that this method has been changed so it returns also the build number of our customizations.

static SysBuildNo buildNo()
{
return ApplicationVersion::applBuildNo() + MyCustomization.myBuildNo();
}

The result of this change was that the method returned a string that was not expected by the AX Hotfix Installer and the Installer stopped with an error message.
We could finally solve the problem by removing the additional code.

static SysBuildNo buildNo()
{
return ApplicationVersion::applBuildNo();
}



Источник: http://blogs.msdn.com/emeadaxsupport...-too-long.aspx
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
emeadaxsupport: Error during processing of 'AX_CompanyName' report parameter. (rsReportParameterProcessingError) Blog bot DAX Blogs 1 11.04.2011 18:56
emeadaxsupport: How does the AX Hotfix / Service Pack installer detect existing AOS instances Blog bot DAX Blogs 0 29.10.2009 18:05
emeadaxsupport: How to fix SQL error: "Too many parameters were provided in this RPC request" Blog bot DAX Blogs 0 01.09.2009 15:05
emeadaxsupport: Group policy setting "System Objects: Default owner for objects created by members of the administrators group" is missing on Windows Server 2008 Blog bot DAX Blogs 2 28.08.2009 02:14
F1 - "Сертификация по Axapta 3.0 - Installation & Configuration" Nic Обучение 7 17.11.2006 16:15

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 14:10.