Page 22 of 951« First...10...2021222324...304050...Last »

Description of the Access 2003 hotfix package (Vbe6.msp): December 16, 2008

This article
describes the Microsoft Office Access 2003 issue that is fixed in the Office
Access 2003 hotfix package that is dated December 16,
2008.

This article describes the following items about the hotfix package:

  • The issues that the hotfix package fixes.
  • The prerequisites for installing the hotfix
    package.
  • Whether you must restart the computer after you install
    the hotfix package.
  • Whether the hotfix package is replaced by any other
    hotfix package.
  • Whether you must make any registry changes.
  • The files that the hotfix package contains.

Issue that this hotfix package fixes

This hotfix fixes the
following issue that is not previously documented in a Microsoft Knowledge Base
article:

  • Word
    2003 crashes when a Microsoft Visual Studio Tools for Office Template is
    opened, and an image is added to the document from the Control Toolbox Toolbar.

Hotfix information

A
supported hotfix is available from Microsoft. However, this hotfix is intended
to correct only the problem that is described in this article. Apply this
hotfix only to systems that are experiencing the problem described in this
article. This hotfix might receive additional testing. Therefore, if you are
not severely affected by this problem, we recommend that you wait for the next
software update that contains this hotfix.

If the hotfix is available
for download, there is a “Hotfix download available” section at the top of this
Knowledge Base article. If this section does not appear, contact Microsoft
Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required,
you might have to create a separate service request. The usual support costs
will apply to additional support questions and issues that do not qualify for
this specific hotfix. For a complete list of Microsoft Customer Service and
Support telephone numbers or to create a separate service request, visit the
following Microsoft Web site:

Note The “Hotfix download available” form displays the languages for
which the hotfix is available. If you do not see your language, it is because a
hotfix is not available for that language.

Prerequisites

There are no prerequisites for
installing this hotfix.

Restart requirement

You do
not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released
hotfix.

Registry information

To use one of the hotfixes in
this package, you do not have to make any changes to the
registry.

File information

This hotfix may not
contain all the files that you must have to fully update a product to the
latest build. This hotfix contains only the files that you must have to correct
the issue that is listed in this article.

The
global version of this hotfix package uses a Microsoft Windows Installer
package to install the hotfix package. The dates and the times for these files
are listed in Coordinated Universal Time (UTC) in the following table. When you
view the file information, the date is converted to local time. To find the
difference between UTC and local time, use the Time Zone tab
in the Date and Time item in Control Panel.

Download information

Collapse this tableExpand this table

File name File version File
size
Date Time Platform
Office2003-kb960420-glb.exe 11.0.8243.0 1,632,128 03-Dec-2008 20:24 x86

Microsoft Windows Installer .msp file information

Collapse this tableExpand this table

File name File version File
size
Date Time Platform
Vbe6.msp Not
Applicable
6,052,864 03-Dec-2008 04:22 Not
Applicable

After the hotfix is installed, the global version of this
hotfix has the file attributes, or a later version of the file attributes, that
are listed in the following table:

Collapse this tableExpand this table

File name File version File
size
Date Time Platform
Vbe6.dll 6.05.10.34 2,585,592 19-Jun-2008 10:28 x86
For more information about
software update terminology, click the following article number to view the
article in the Microsoft Knowledge Base:
824684

(http://support.microsoft.com/kb/824684/
)

Description of the standard terminology that is used to describe Microsoft software updates

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 960420 – Last Review: January 12, 2015 – Revision: 1.0


Applies to
  • Microsoft Office Access 2003
kbnosurvey kbarchive kbsurveynew kbexpertiseinter kbqfe kbhotfixrollup kbautohotfix kbhotfixserver KB960420

Read the original post:
Description of the Access 2003 hotfix package (Vbe6.msp): December 16, 2008

Error message when you try to run a report in Microsoft Dynamics CRM 4.0: "The report cannot be displayed"

When you try to run a report in Microsoft Dynamics CRM 4.0, you receive the following error message:

Reporting Error
The report cannot be displayed.

Additionally, if the DevErrors value is set to On in the Web.config file, you receive the following error message:

Error Description:
An error occurred during report rendering.

Error Details:
An error occurred during report rendering.

Full Stack:
MissingParameterException: The ‘CRM_CalendarType’ parameter is missing a value

at Microsoft.Reporting.WebForms.ParametersArea.ValidateNonVisibleReportInputsSatisfied()

at Microsoft.Reporting.WebForms.ReportViewer.OnPreRender(EventArgs e)

CrmException: An error occurred during report rendering.

at Microsoft.Crm.Web.Reporting.SrsReportViewer.ReportErrorHandler(Object sender, ReportErrorEventArgs e)

at Microsoft.Reporting.WebForms.ReportViewer.OnError(Exception e)

at Microsoft.Reporting.WebForms.ReportViewer.OnPreRender(EventArgs e)

at System.Web.UI.Control.PreRenderRecursiveInternal()

at System.Web.UI.Control.PreRenderRecursiveInternal()

at System.Web.UI.Control.PreRenderRecursiveInternal()

at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

HttpUnhandledException: Exception of type ‘System.Web.HttpUnhandledException’ was thrown.

at System.Web.UI.Page.HandleError(Exception e)

at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

at System.Web.UI.Page.ProcessRequest()

at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)

at System.Web.UI.Page.ProcessRequest(HttpContext context)

at ASP.online_crmreports_rsviewer_reportviewer_aspx.ProcessRequest(HttpContext context)

at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously

This problem occurs because you do not have some required privileges on the User Settings entity. You must have a minimum of the Business Unit level for the Read privilege of the User Settings entity.
To resolve this problem, follow these steps:

  1. Log on to the Microsoft Dynamics CRM 4.0 Web client as an administrator.
  2. Click Settings, click Administration, and then click Security Roles.
  3. Double-click the security role that you use.
  4. On the Business Management tab, set the Read privilege of the User Settings entity at least to the Business Unit level.
  5. Click Save and Close.

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Article ID: 961306 – Last Review: January 12, 2015 – Revision: 2.0


Applies to
  • Microsoft Dynamics CRM 4.0
kbnosurvey kbarchive kberrmsg kbmbsreports kbsurveynew kbtshoot kbprb kbnomt kbmbsmigrate kbexpertiseinter KB961306

View the original here:
Error message when you try to run a report in Microsoft Dynamics CRM 4.0: "The report cannot be displayed"

Support for .NET in Microsoft Application Virtualization 4.5 (App-V)

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Background

Microsoft has made several architectural changes in the implementation of Microsoft Application Virtualization (App-V) 4.5 to ensure that the product is aligned with our roadmap for future innovation. One such change entailed moving the API intercepts from kernel mode into user mode. This change had a side-effect of changing the App-V compatibility with the .NET Framework from previous versions of App-V.

App-V 4.5 continues to be fully compatible with .NET applications. The change in compatibility only manifests itself with the .NET Framework.

This article provides specific guidance for sequencing and using .NET applications with App-V 4.5.

Guidance for sequencing .NET applications with the 4.5 sequencer

Scenario #1: Sequencing applications to be deployed to Windows Vista RTM clients

·         A version of .NET that is  greater than or equal to the applications’ .NET requirement must be locally installed on the sequencing station

o   Example: Windows Vista RTM includes .NET 3.0. If the application that is being sequenced requires a version of .NET that is newer than 3.0 you must install the newer version of .NET on the sequencing workstation before you proceed to sequence the application.

Scenario #2: Sequencing applications to be deployed to Windows Vista SP1 clients

·         .NET 3.5 RTM, not .NET 3.5 SP1, can be sequenced successfully on a fully patched Windows Vista SP1 system, no additional installation of .NET is required on the sequencing workstation

Scenario #3: Sequencing applications to be deployed to Windows XP clients

·          The version of .NET that is required by the application to be sequenced must be  locally installed on the sequencing workstation prior to sequencing the application

Guidance for using .NET with virtual applications sequenced in App-V 4.5

In order to use an application that has a dependency on any version of .NET, it is required that .NET is installed locally on the client.

Scenario #1: A single virtualized application on a client with a .NET dependency

·         .NET must be locally installed on that client

·         The locally installed .NET version must be greater than or equal to the application’s .NET requirement

Scenario #2: Several virtualized applications on a client with a .NET dependency

·         .NET must be locally installed on that client

·         The locally installed .NET version must be greater than or equal to the greatest version .NET dependency of all the applications

o   Example: If two packages are to be deployed, one with a .NET 2.0 dependency and the other with a .NET 3.0 dependency, in order for both to function correctly, .NET 3.0 must be locally installed.

Exception: If the application has a dependency on .NET 3.5 RTM and it will be deployed to a Vista SP1 system, a local installation of .NET 3.5 on the target system is not required. This exception does not apply to .NET 3.5 SP1.

Support for legacy packages (pre App-V 4.5) that have .NET sequenced inside the package

Packages that were sequenced with APP-V 4.2 or lower that include .NET and will be deployed to 4.5 clients follow the same guidelines as App-V 4.5 sequenced applications:

·         The client OS must have .NET locally installed.  The installed version must be greater than or equal to the application’s .NET dependency

·         Windows Vista RTM includes .NET 3.0 by default, no additional .NET installation is required unless the application requires .NET 3.5 RTM or SP1

·         Windows Vista SP1 (fully-patched) includes .NET 3.0 by default, no additional .NET installation is required unless the application requires .NET 3.5 RTM or SP1

·         All Windows XP client version require a local installation of .NET because .NET is not included by default on Windows XP systems

Summary

In order to

·         Sequence .NET on an App-V 4.5 workstation

·         Deploy App-V 4.5 packages with .NET dependencies

·         Deploy legacy App-V packages that include .NET to App-V 4.5 clients

 

The following summarizes the requirements of .NET support in App-V 4.5:

 

Windows XP SP2

·         . NET versions 1.0, 1.1, 2.0, 3.0, 3.5 (all) dependency: locally install .NET version(s)

Windows Vista (RTM)

·         .NET versions 2.0, 3.0 dependency: already installed by default as part of Windows Vista

·         .NET versions 3.5 (all) dependency: locally install .NET version(s)

Windows Vista SP1 (with all patches)

·         .NET versions 2.0, 3.0, 3.5 RTM dependency: already installed by default as part of Windows Vista SP1 (with all patches)

·         .NET versions 3.5 SP1 dependency: locally install .NET version(s)

 

 

 

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 959524 – Last Review: January 12, 2015 – Revision: 3.0


Applies to
  • Microsoft Application Virtualization 4.5 for Terminal Services
  • Microsoft Application Virtualization 4.5 for Windows Desktops
kbnosurvey kbarchive kbnomt kbrapidpub KB959524

Read the original post:
Support for .NET in Microsoft Application Virtualization 4.5 (App-V)

You cannot configure an Active Directory domain schema and Microsoft Dynamics CRM 4.0 URLs independently for external Active Directory users and for internal Active Directory users

You cannot configure an Active Directory domain schema and Microsoft Dynamics CRM 4.0 URLs independently for external Active Directory users and for internal Active Directory users. Because of this, the URLs in the Software Development Kit (SDK) code cannot be resolved in a domain.
This problem occurs because the CrmServiceFactory property that is used by the pipeline and by the AsyncService service always uses the ADRootDomainScheme scheme in the ConfigDB entry. When you create a URL for the CrmService service and for the MetadataService service, the scheme prevents you from configuring a computer to use a different scheme.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756

(http://support.microsoft.com/kb/322756/
)

How to back up and restore the registry in Windows XP and Windows Vista

This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

949256

(http://support.microsoft.com/kb/949256/
)

Microsoft Dynamics CRM 4.0 updates and hotfixes

After you apply this hotfix, create a registry key that is named “ADRootDomainScheme” on the Microsoft Dynamics CRM 4.0 server. To do this, follow these steps:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSCRM

  3. Right-click MSCRM, click New, and then click String Value.
  4. In the Name box, type ADRootDomainScheme.
  5. Right-click ADRootDomainScheme, and then click Modify.
  6. In the Value box, type either http or https, and then click OK.

In addtion to the ADRootDomainScheme the following string registry entries must be added as well:

  • ADSdkRootDomain (string)
  • ADWebApplicationRootDomain (string)

If you are using IFD (Internet Facing Deployment) authentication for CRM there are an addtional set of registry entries that can be used in the same fashion as the Active Directory (AD) authentication registry entries.

  • IfdRootDomainScheme (string)
  • IfdSdkRootDomain (string)
  • IfdWebApplicationRootDomain (string)
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

950542

(http://support.microsoft.com/kb/950542/
)

Synchronous plug-ins do not respond to the events that are triggered in Microsoft Dynamics CRM 4.0

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684

(http://support.microsoft.com/kb/824684/LN/
)

Description of the standard terminology that is used to describe Microsoft software updates

For more information about Microsoft Business Solutions CRM software hotfix and update package terminology, click the following article number to view the article in the Microsoft Knowledge Base:

887283

(http://support.microsoft.com/kb/887283/
)

Microsoft Business Solutions CRM software hotfix and update package naming standards

Article ID: 959758 – Last Review: January 12, 2015 – Revision: 3.0


Applies to
  • Microsoft Dynamics CRM 4.0
kbnosurvey kbarchive kbfix kbexpertiseinter kbsurveynew kbmbsmigrate kbqfe KB959758

Read the original:
You cannot configure an Active Directory domain schema and Microsoft Dynamics CRM 4.0 URLs independently for external Active Directory users and for internal Active Directory users

The fixed exchange rate is not used in the destination company when you post an intercompany general ledger journal in Microsoft Dynamics AX

When you post an intercompany general ledger journal by using the fixed exchange rate in Microsoft Dynamics AX, the fixed exchange rate is used in the originating company as expected. However, the fixed exchange rate is not used in the destination company.
This problem occurs because the fixed exchange rate is created for the originating journal. However, the information about the fixed exchange rate is not transferred to the intercompany journal.

Microsoft Dynamics AX 3.0 hotfix information

A supported hotfix is now available from Microsoft. The hotfix corrects the problem that is described in this article. Apply the hotfix only to systems that are experiencing this specific problem.

To resolve this problem immediately, contact Technical Support for Microsoft Dynamics and related products to obtain the hotfix. You can log on to the Microsoft Dynamics site and create a new support request. To do this, visit the following Microsoft Web site:

You can also contact Technical Support for Microsoft Dynamics and related products by telephone at (888) 477-7877.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.If you are a customer and if you do not have a Premier Support Agreement with Microsoft, you must contact your partner to obtain this hotfix.

Installation information

If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must follow these steps:

  1. Review the changes that are documented in the .xpo file.
  2. Apply these changes in a test environment before you apply the hotfix in a production environment.

For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:

893082

(http://support.microsoft.com/kb/893082/
)

How to install a Microsoft Dynamics AX Hotfix

Prerequisites

You must have Microsoft Dynamics AX 3.0 Service Pack 5 installed to apply this hotfix.

Removal information

You cannot remove this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Objects that are affected

This hotfix affects the following object:

  • ClassesLedgerJournalCheckPost

Microsoft Dynamics AX 4.0

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

Microsoft Dynamics AX 3.0

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

Article ID: 936206 – Last Review: January 12, 2015 – Revision: 3.0


Applies to
  • Microsoft Dynamics AX 4.0
  • Microsoft Dynamics AX 3.0
  • Financials General Ledger
kbnosurvey kbarchive kbqfe kbmbsmigrate kbHotfixServer KB936206

Read this article:
The fixed exchange rate is not used in the destination company when you post an intercompany general ledger journal in Microsoft Dynamics AX

Error message when you start the Microsoft Forecaster Web Access client: “The page cannot be found HTTP Error 404 – File or directory not found”

When you start the Microsoft Forecaster Web Access client, you receive the following error message:

The page cannot be found HTTP Error 404 – File or Directory not found.

This issue occurs when the Microsoft Forecaster Web Access client is installed on Microsoft Windows Server 2003.

This issue occurs if Active Server Pages (ASP) is not enabled.
To resolve this issue, follow these steps:
  1. In Control Panel, double-click Internet Information Services (IIS) Manager.
  2. Click Web Server Extensions.
  3. Click Active Server Pages, and then click Allow.

Article ID: 936106 – Last Review: January 12, 2015 – Revision: 4.0


Applies to
  • Microsoft Forecaster 7.0
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 4.0
  • Microsoft Dynamics AX 3.0
  • Microsoft Dynamics NAV 4.0
  • Microsoft Business Solutions–Navision 3.70, when used with:
kbnosurvey kbarchive kberrmsg kbtshoot kbsolomonfrx kbgreatplainsfrx kbexpertiseinter kbexpertiseadvanced kbaxaptafrx kbmbsmigrate kbprb KB936106

View article:
Error message when you start the Microsoft Forecaster Web Access client: “The page cannot be found HTTP Error 404 – File or directory not found”

Error message when you log on to Microsoft Forecaster: "Cannot connect to the database. User user name may not have permissions to access database database name on server name"

When you log on to Microsoft Forecaster, you receive the following error message:

Cannot connect to the database. User user name may not have permissions to access database database name on server name

Notes

  • In this error message, the user name placeholder represents the name of the user who you are using to log on to Microsoft Forecaster.
  • The database name placeholder represents the name of the Microsoft Forecaster database.
  • The server name placeholder represents the name of the server on which the Microsoft Forecaster database is located.
This problem may occur because the database name contains unsupported characters. The following characters are unsupported characters.

Collapse this tableExpand this table

Character Name
- Minus sign
! Exclamation point
@ At sign
# Number sign
$ Dollar sign
% Percent sign
^ Caret
& Ampersand
* Asterisk
( Opening parenthesis
) Closing parenthesis
+ Plus sign
? Question mark
> Greater than sign
< Less than sign
: Colon
Single quotation mark
Quotation mark
To resolve this problem, rename the database so that the name does not use any unsupported characters.

After the database name is changed, log on to Microsoft Forecaster. To log on to Microsoft Forecaster, follow these steps:

  1. On the log on screen, type a new name in the Application name box, type a valid user name in the User name box, type a password in the Password box, and then click the OK button.
  2. The Application Maintenance window appears. In the Server name box, type the name of the database server, type the new name of the Microsoft Forecaster database in the Database name box, and then click OK.

Article ID: 936104 – Last Review: January 12, 2015 – Revision: 4.0


Applies to
  • Microsoft Forecaster 7.0
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 4.0
  • Microsoft Dynamics AX 3.0
  • Microsoft Dynamics NAV 4.0
  • Microsoft Business Solutions–Navision 3.70, when used with:
kbnosurvey kbarchive kbtshoot kbsolomonfrx kbnavisionfrx kbgreatplainsfrx kbexpertiseinter kbexpertisebeginner kberrmsg kbaxaptafrx kbmbsmigrate kbprb KB936104

Read this article:
Error message when you log on to Microsoft Forecaster: "Cannot connect to the database. User user name may not have permissions to access database database name on server name"

Error message when you try to log on to Microsoft Forecaster: "Login failed for user. Reason: Not associated with a trusted SQL Server connection"

When you try to log on to Microsoft Forecaster, you receive the following error message:

Login Failed for User. Reason: Not associated with a trusted SQL Server connection.

This problem occurs when you are using Microsoft Forecaster on a server that is running Microsoft SQL Server 2005.

This problem occurs if the authentication mode in SQL Server 2005 is set to Windows Authentication.
To resolve this problem, change the authentication mode to SQL Server and Windows Authentication. To do this, follow these steps:
  1. Start Microsoft SQL Server Management Studio.
  2. Right-click the instance of SQL Server 2005, click Properties, and then click Security.
  3. In the Authentication list, click SQL Server and Windows Authentication.
  4. Restart the server, or restart the MSSQLSERVER service.

Article ID: 936107 – Last Review: January 12, 2015 – Revision: 4.0


Applies to
  • Microsoft Forecaster 7.0
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 4.0
  • Microsoft Dynamics AX 3.0
  • Microsoft Dynamics NAV 4.0
  • Microsoft Business Solutions–Navision 3.70, when used with:
kbnosurvey kbarchive kbtshoot kbsolomonfrx kbnavisionfrx kbgreatplainsfrx kbexpertiseinter kbexpertiseadvanced kberrmsg kbaxaptafrx kbmbsmigrate kbprb KB936107

Visit site:
Error message when you try to log on to Microsoft Forecaster: "Login failed for user. Reason: Not associated with a trusted SQL Server connection"

Description of price levels and of customer discounts in Accounting Professional, in Accounting Express, or in Small Business Accounting

This article describes price levels and customer discounts
in Microsoft Office Accounting Professional, in Microsoft Office Accounting Express, and in Microsoft Office Small Business Accounting.
To apply a constant change in sales price for a customer, use a price level. To apply a change in sales price for one transaction, use a discount.

How to set up a price level

  1. In Accounting Professional, in Accounting Express, or in Small Business Accounting, click
    Price Levels on the Customers menu.
  2. Click Add to add a new price
    level.
  3. In the Price Level field, type the name of the price level.

    The name can include a number, such as “Price Level 1,” or “Price Level 2.” The name can be descriptive, such as Half off” or “5% off.”

  4. Type the percentage by which you want to increase or to decrease the sales price.
  5. Select Increase price by percentage or
    Decrease price by percentage.
  6. Click OK, and then click Save and Close.

How to assign a price level to a customer

  1. On the Customer menu, point to Customer Lists, and then click Customers.
  2. Double-click a customer record to open a customer record.
  3. Click the Details tab.
  4. In the Price Level field, select the price level.

The price level will automatically change the sales price for that customer the next time that a quote, a sales order, or an invoice is created.

Note The changes in the Price Level field will not be reflected in the Discount column of the quote, of the sales order, or
of the invoice. The changes will be reflected in the Unit Price column. The
Markup column is for the difference between the unit price and the cost, and
the Markup column is displayed only on the quote. The Discount column is for adding a sale-specific
increase or decrease in the price of the product or of the service. The behavior of the Discount column is described in the “How to set up a discount” section.

How to set up a discount

  1. Create a new quote,
    a new sales order, or a new invoice by pointing to New on the Customers menu.
  2. In the Customer name box, select the customer.
  3. Type any other information that you must have on the quote, on the sales order, or on the invoice.
  4. In the Products and Services pane, select the items.
  5. In the Discount column for the appropriate line item, type the discount amount.

    Type the discount in the Discount column for the
    appropriate line item that should be discounted.

  6. Click Save and Close.

Article ID: 897534 – Last Review: January 11, 2015 – Revision: 6.0


Applies to
  • Microsoft Office Accounting Professional 2008
  • Microsoft Office Accounting Express 2008
  • Microsoft Office Accounting Professional 2007
  • Microsoft Office Accounting Express 2007
  • Microsoft Office Small Business Management Edition 2006
kbnosurvey kbarchive kbmbsmigrate kbinfo KB897534

Read the original post:
Description of price levels and of customer discounts in Accounting Professional, in Accounting Express, or in Small Business Accounting

Client installer command line parameters are ignored when used in conjunction with KEEPCURRENTSETTINGS=1 in Microsoft Application Virualization 4.5

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

The following client installer command line parameters are ignored when used in conjunction with KEEPCURRENTSETTINGS=1

 

·         SWICACHESIZE

·         MINFREESPACEMB

·         ALLOWINDEPENDENTFILESTREAMING

·          APPLICATIONSOURCEROOT

·         ICONSOURCEROOT

·         OSDSOURCEROOT

·         SYSTEMEVENTLOGLEVEL

·         SWIGLOBALDATA

·         DOTIMEOUTMINUTES

·         SWIFSDRIVE

·         AUTOLOADTARGET

·         AUTOLOADTRIGGERS

·         SWIUSERDATA

·         REQUIRESECURECONNECTION

To workaround this issue, a different mechanism needs to be used to configure the client with these settings. The App-V ADM Template can be used to set the following client settings from the list above: 

 

·         APPLICATIONSOURCEROOT

·         ICONSOURCEROOT

·          OSDSOURCEROOT

·         AUTOLOADTARGET

·         AUTOLOADTRIGGERS

·         DOTIMEOUTMINUTES

·         ALLOWINDEPENDENTFILESTREAMING

If KEEPCURRENTSETTINGS is not specified on the command line, install will behave as normal.  Any existing registry values will be overwritten by the installer.

 

Example command lines:

               

                setup.exe /s /v”/qn INSTALLDIR=C:AppV /l*v setup.txt”

                msiexec.exe /i setup.msi /qn INSTALLDIR=C:AppV /l*v setup.txt

 

Note INSTALLDIR is not one of the ADM values, so it can be specified on the command line regardless of whether KEEPCURRENTSETTINGS is specified.

 

If KEEPCURRENTSETTINGS is set to any value on the command line, install will not overwrite any existing registry values.

 

Examples:

 

There are no existing registry values.  This will behave a like normal install.

                setup.exe /s /v”/qn KEEPCURRENTSETTINGS=1 /l*v setup.txt”

               

ASR is set in the registry.  The following will not overwrite the existing value of ASR in the registry.

                setup.exe /s /v”/qn KEEPCURRENTSETTINGS=1 /l*v setup.txt APPLICATIONSOURCEROOT=c:my_asr”

               

                setup.exe /s /v”/qn KEEPCURRENTSETTINGS=0 /l*v setup.txt APPLICATIONSOURCEROOT=c:my_asr”

               

                setup.exe /s /v”/qn KEEPCURRENTSETTINGS=”Yes” /l*v setup.txt APPLICATIONSOURCEROOT=c:my_asr”

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 959521 – Last Review: January 11, 2015 – Revision: 2.0


Applies to
  • Microsoft Application Virtualization 4.5 for Terminal Services
  • Microsoft Application Virtualization 4.5 for Windows Desktops
  • Microsoft Application Virtualization for Remote Desktop Services
  • Microsoft Application Virtualization for Windows Desktops
kbnosurvey kbarchive kbnomt kbrapidpub KB959521

See the original post:
Client installer command line parameters are ignored when used in conjunction with KEEPCURRENTSETTINGS=1 in Microsoft Application Virualization 4.5

Page 22 of 951« First...10...2021222324...304050...Last »

Recent Comments

    Archives

    Categories