Web request system templates was not created if Employee Portal (EP) was not configured in the license when a NAV company was created. The EP setup form now allows the user to create the templates if the EP granules are added after having created the NAV company.
This has been corrected
Form 6800 Employee Portal Setup Card
Table 6800 Employee Portal Setup
Features
P71) MS SQL 2005 Compliancy
Feature
Business Notification for Dynamics NAV can now install and run on MS SQL Server 2005.
This has been implemented
Errors fixed
I1) Navision Database Not Attached To MS SQL Server 2005
Error
The Navision Database was not attached automatically during installation when using MS SQL Server 2005.
This has been corrected
I2) MDAC Not Installed
Error
MDAC was not installed when running the installation program.
This has now been corrected
I3) Business Notification Will Not Install on MS SQL 2005
Error
It was not possible to install Business Notification on MS SQL 2005.
This has been corrected
BusinessNotificationServer msi
VSA reference: 8420589
I4) Client Installer Installs MSDE Even When Not Selected
Error
MSDE was installed even though it was not selected during the custom installation.
This has been corrected
I5) MSDE Can Not Install In Change / Repair Installation
Error
It was not possible to change the installation to include the MSDE.
This has been corrected
Errors fixed
T1) Can Not Create Connection Without Registry Key
Error
When creating a new connection with Windows Authentication an connecting would return the error messages: “Database file not found” and “Cannot read file”.
This has been corrected
T2) Translation Problems In Flow Filters
Error
The localized table names can now be used properly in the “SetFlowFilter” predicate.
This has been corrected
T3) NODBC Can Not Exchange BLOB Fields With Access
Error
When creating a linked table from MS Access, based on a Navision table containing a BLOB field it was not possible to update the BLOB field from Access.
This has been corrected
T4) Unexpected Error In DTS Package
Error
When creating a DSN and a DTS to read from the DSN it was not possible to expand the contact table from the query builder. A limitation in the length of column names could cause an unexpected error in localized databases where the column name exceeded 63 characters.
This has been corrected
VSA reference: 8363932
T5) Not Possible To Set Filters With Local Characters
Error
It was possible to create queries with local characters but they would not return any data.
This has been corrected
VSA reference: 8475276
T6) NODBC Can Not Connect Without Registry Key
Error
MSQuery could not connect to the DSN without the registry keys when using windows authentication.
This has been corrected
T7) Not Possible To Connect To NODBC
Error
It was not possible to connect to the database with NODBC if the username included names with special local characters.
This has been corrected
VSA reference: 8313330
T8) IIS Freezes When Connecting From ASP Page
Error
When several users connected to Navision from an active server page (.asp) via NODBC it could cause an error and make the IIS freeze.
This has been corrected
T9) List Of Available Tables Is Not Visible
Error
When using mail merge with an ODBC connection in a non English language it was not possible to display the list of available tables.
This has been corrected
VSA reference: 8337704
T10) NODBC Does Not Work With Linked Servers
Error
It was not possible to create a query to a linked server.
This has been corrected
T11) Password Error
Error
When using a password including “5” would give an error message.
Уважаемый посетитель!
Чтобы распечатать файл, скачайте его (в формате Word).
Ссылка на скачивание - внизу страницы.