Xslt8690 ошибка при обработке xslt

Extensive research did not lead me to understanding why the below happens — I hope that the SO community can help…

I copied the files mentioned in Why HTML1113: Document mode restart from IE9 Standards to Quirks to local filesystem and opened the xml in IE9 (by specifying the path D:... in the url bar).
Surprisingly, the behavior is quite different from opening the web version.
Now I can understand that «My Computer» zone settings differing from Internet zone ones explain the pop-up windows mentioned below, but I don’t understand why the result is different and why quirks mode is not automatically chosen, just like was done when opening the xml on the web.

When I open the local file, I get the following:

AllowScripts

which no doubt is caused by a local zone setting. Next, the browser mode is IE9 (not auto quirks as earlier) and it fails on applying the XSLT:

XSLT8690

First I thought that this was caused by MSXML6 DOM basic settings like AllowXsltScript not being set to true, but I am not sure about that any more, because it all works OK when opening the web version.
So why does the local one fail?

Stranger still, opening the web version led to auto quirks mode and correct result, but when I switch to quirks mode for the local file, it fails on the MSXML6 DOM object — actually this makes more sense to me than no error, because quirks mode probably only offers MSXML3 (or should only offer that — but then why was auto quirks in web version OK?).

Quirks1

After accepting, it changes to

Quirks2

Now, when selecting IE9 standards mode again, I get

IE9take2_console

and the result is the expected

IE9take2

Reciting events when using local files (apart from zone setting differences):

  1. IE9 standards mode XSLT8690 error
  2. Switching to quirks mode errors
  3. Switching back to IE9 standards mode is OK now

Reciting the events when opening the web version (apart from differences due to zone settings):

  1. quirks mode automatically
  2. page opens correctly in quirks — apparently MSXML6 is still used here in the auto quirks mode
  3. switch to IE9 standards mode is OK too
  4. Back to quirks mode errors as above («The parameter is incorrect'»)

What is causing all these peculiar differences?

Обширные исследования не привели меня к пониманию того, почему происходит следующее: я надеюсь, что сообщество SO поможет…

Я скопировал файлы, упомянутые в статье Почему HTML1113: Режим документа перезапускается из стандартов IE9 в Quirks в локальную файловую систему и открыл xml в IE9 (указав путь D:... в строке url).
Удивительно, но поведение отличается от открытия веб-версии.
Теперь я могу понять, что настройки зоны «Мой компьютер», отличные от зон интернет-зоны, объясняют всплывающие окна, упомянутые ниже, но я не понимаю, почему результат отличается и почему режим quirks не выбирается автоматически, как это было сделано, когда открытие xml в Интернете.

Когда я открываю локальный файл, я получаю следующее:

AllowScripts

что, несомненно, вызвано настройкой локальной зоны. Далее, режим браузера — IE9 (а не автоматические причуды, как раньше), и он не работает при применении XSLT:

XSLT8690

Сначала я подумал, что это вызвано базовыми настройками MSXML6 DOM, такими как AllowXsltScript не установлены в true, но я не уверен в этом, потому что все работает нормально при открытии веб-версии.
Так почему же местная неудача?

Тем не менее, незнакомец, открыв веб-версию, появился режим автоматического приведения и правильный результат, но когда я переключаюсь в режим quirks для локального файла, он терпит неудачу в объекте DOM MSXML6 — на самом деле это имеет для меня больше смысла, чем отсутствие ошибки, поскольку режим quirks возможно, только предлагает MSXML3 (или должен только предложить это — но тогда почему были автоматические причуды в веб-версии ОК?).

Quirks1

После принятия он меняет

Quirks2

Теперь, когда вы снова выбираете режим стандартов IE9, я получаю

IE9take2_console

и результат — ожидаемый

IE9take2

Чтение событий при использовании локальных файлов (кроме различий в настройках зоны):

Ошибка режима IE9 XSLT8690 Переход к ошибкам режима quirks Переход в режим стандартов IE9 в порядке

Чтение событий при открытии веб-версии (кроме различий из-за настроек зоны):

режим quirks автоматически страница открывается правильно в причудах — видимо, MSXML6 по-прежнему используется здесь в режиме автоматического причудливости переключиться на режим стандартов IE9 тоже хорошо Вернуться к ошибкам режима quirks, как указано выше («Неверный параметр»)

Что вызывает все эти своеобразные различия?

RRS feed

  • Remove From My Forums
  • Question

  • How does one go about debugging the error «XSLT8690: XSLT processing failed.»? I am trying to usean XML file with an XSLT file referenced in the header with IE11. By comparing the XML which results in this error to others which work fine with
    the same transform I’ve narrowed the problem down to the processing of certain elements. Is there some way to make IE give more detailed error information?

All replies

  • Hi,

    tools>Internet Options>Advanced tab, check «Always record developer console messages.»

    Save changes.

    Close and Open IE. Open a blank page (about:blank) then press f12 to display the dev tool.

    Select the Debug tab and choose «Break on all exceptions» dropdown (looks like a stop sign).

    Select the Networking tab and turn on logging.

    Return to the console tab. PIN the dev tool to the bottom of the browser (or dock it to a side on your screen)

    In the IE address bar type in the address to your website page.

    Use the File Properties menu in IE to confirm that it is in the expected IE security zone (expected internet). 

    Use the Emulation tab of the f12 tool to confirm that the expected IE version emulation is being used. (you may have to use IE10 for legacy intranet sites).

    If you are creating a feed for public consumption, make sure that you have Internet Options>Content tab, >Feeds and slices>check «Turn on feed reader view». Save changes.

    If possible include links to problem websites with your questions. If it is an internal intranet site mention as such.

    Regards.


    Rob^_^

    • Proposed as answer by

      Wednesday, August 29, 2018 2:01 AM

  • Thanks for the extensive instructions. I tried them and got more information but nothing relevant to the XSLT error message. The URL is http://clamb.name/S1000D/Iss2-2_stylesheets_with_bike_050921[1][1]X3DOM.bike/PMC-S1000DBIKE-U8025-00001-00_000-02.html
    .  Using the left panel navigate to Bike Manuals—>Maintenance Manual—>Bicycle—>General—>Bicycle — Description of how it is made to encounter the error.

  • Oddly, I don’t get this error when I use IE to process the files from the local disk.

Extensive research did not lead me to understanding why the below happens – I hope that the SO community can help…

I copied the files mentioned in Why HTML1113: Document mode restart from IE9 Standards to Quirks to local filesystem and opened the xml in IE9 (by specifying the path D:... in the url bar).
Surprisingly, the behavior is quite different from opening the web version.
Now I can understand that «My Computer» zone settings differing from Internet zone ones explain the pop-up windows mentioned below, but I don’t understand why the result is different and why quirks mode is not automatically chosen, just like was done when opening the xml on the web.

When I open the local file, I get the following:

AllowScripts

which no doubt is caused by a local zone setting. Next, the browser mode is IE9 (not auto quirks as earlier) and it fails on applying the XSLT:

XSLT8690

First I thought that this was caused by MSXML6 DOM basic settings like AllowXsltScript not being set to true, but I am not sure about that any more, because it all works OK when opening the web version.
So why does the local one fail?

Stranger still, opening the web version led to auto quirks mode and correct result, but when I switch to quirks mode for the local file, it fails on the MSXML6 DOM object – actually this makes more sense to me than no error, because quirks mode probably only offers MSXML3 (or should only offer that – but then why was auto quirks in web version OK?).

Quirks1

After accepting, it changes to

Quirks2

Now, when selecting IE9 standards mode again, I get

IE9take2_console

and the result is the expected

IE9take2

Reciting events when using local files (apart from zone setting differences):

  1. IE9 standards mode XSLT8690 error
  2. Switching to quirks mode errors
  3. Switching back to IE9 standards mode is OK now

Reciting the events when opening the web version (apart from differences due to zone settings):

  1. quirks mode automatically
  2. page opens correctly in quirks – apparently MSXML6 is still used here in the auto quirks mode
  3. switch to IE9 standards mode is OK too
  4. Back to quirks mode errors as above («The parameter is incorrect'»)

What is causing all these peculiar differences?

RRS feed

  • Remove From My Forums
  • Question

  • How does one go about debugging the error «XSLT8690: XSLT processing failed.»? I am trying to usean XML file with an XSLT file referenced in the header with IE11. By comparing the XML which results in this error to others which work fine with
    the same transform I’ve narrowed the problem down to the processing of certain elements. Is there some way to make IE give more detailed error information?

All replies

  • Hi,

    tools>Internet Options>Advanced tab, check «Always record developer console messages.»

    Save changes.

    Close and Open IE. Open a blank page (about:blank) then press f12 to display the dev tool.

    Select the Debug tab and choose «Break on all exceptions» dropdown (looks like a stop sign).

    Select the Networking tab and turn on logging.

    Return to the console tab. PIN the dev tool to the bottom of the browser (or dock it to a side on your screen)

    In the IE address bar type in the address to your website page.

    Use the File Properties menu in IE to confirm that it is in the expected IE security zone (expected internet). 

    Use the Emulation tab of the f12 tool to confirm that the expected IE version emulation is being used. (you may have to use IE10 for legacy intranet sites).

    If you are creating a feed for public consumption, make sure that you have Internet Options>Content tab, >Feeds and slices>check «Turn on feed reader view». Save changes.

    If possible include links to problem websites with your questions. If it is an internal intranet site mention as such.

    Regards.


    Rob^_^

    • Proposed as answer by

      Wednesday, August 29, 2018 2:01 AM

  • Thanks for the extensive instructions. I tried them and got more information but nothing relevant to the XSLT error message. The URL is http://clamb.name/S1000D/Iss2-2_stylesheets_with_bike_050921[1][1]X3DOM.bike/PMC-S1000DBIKE-U8025-00001-00_000-02.html
    .  Using the left panel navigate to Bike Manuals—>Maintenance Manual—>Bicycle—>General—>Bicycle — Description of how it is made to encounter the error.

  • Oddly, I don’t get this error when I use IE to process the files from the local disk.

  • Xrgame dll чистое небо ошибка
  • Xrengine exe системная ошибка сталкер чистое небо
  • Xrengine exe системная ошибка openal32 dll что делать
  • Xrengine exe системная ошибка msvcr120 dll call of chernobyl
  • Xrengine exe ошибка приложения 0xc000007b виндовс 10