[tcollins]

Hi All,

After upgrading from 8.5 to 8.6 through pulse yesterday all of my .xhtml files are generating massive amounts of content errors, nearly every line has a red underline.

Just wondering if anyone else has experienced this and more importantly, is there a solution!?!?!

cheers
Tristan

[support-joy]

Tristan,

I haven’t heard anyone reporting this issue. Can you answer below queries –
1. Can you open MyEclipse IDE, from menu options click on MyEclipse > Installation Summary > Installation Details
2. Can you look into problems tab and see what is the error reported?
3. Can you right click on the red cross and see if you can click on quick-fix?
4. Can you attach screenshots which will help me get a visual?
5. Can you try -clean and see if it helps? Please refer – https://www.genuitec.com/forums/topic/troubleshoot-using-the-clean-command-line-argument/

[tcollins]

Hi Joy,

1. Installation summary:
*** Date:
Friday, 10 September 2010 9:09:39 AM EST

** System properties:
OS=WindowsVista
OS version=6.1.0
Java version=1.6.0_13

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 8.6
Build id: 8.6-20100806

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 8.6
Build id: 8.6-20100806

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Genuitec\MyEclipse-8.6\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\Genuitec\MyEclipse-8.6\../Common/plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519\eclipse_1206.dll
-startup
C:\Genuitec\MyEclipse-8.6\../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-install
C:/Genuitec/MyEclipse-8.6
-configuration
configuration
-vm
C:/Genuitec/Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dll

2. Problems tab: Nothing is coming up in Error

3. There is no red cross to click on, I’ve tried right clicking and selecting quick fix but this just adds random bits of code to my page which I don’t want such as <element> tags ???

4. According to the “In this forum you can:” information on the main page, attaching files isn’t allowed in this forum, but picture that you are viewing a standard .xhtml page and that just about ever line has the red squiggly line under it (which usually indicates that there is a syntax error, spelling mistake or something like that). These Errors were not there prior to updating through Pulse.

5. Yep I’ve already tried running from a clean start

[support-joy]

tcollins,

Thank you for the details. Can you please look into your .log file located at [your workspace dir]/.metadata/.log and look for any relevant issues logged? Also you can either [pm] the screenshots or send mail to support@genuitec.com with reference to above weblink and add ATTN:Joy in the subject. Have you added any third party plugins to your ME profile? If yes, can you list them here. I am specifically looking for PDT plugin.

[chrisadam]

To update the operating system of your 900 Series HP 3000, complete these steps:

Mount the system load tape containing the autoboot configuration on the tape drive. Put the tape drive on-line.

Put the console in control mode by pressing CTRL and B simultaneously.

NOTE: If the ISL autoboot flag is enabled, the MPE/iX startup sequence attempts to automatically boot from the primary boot path after the system is reset. This should not occur. After resetting the system in the next step, carefully watch console messages and press any key within 10 seconds of seeing the following display on the console:

Autoboot from primary boot path enabled.

To override, press any key within 10 seconds.

Reset the system. At the control mode prompt (CM>), enter:

CM> RS

Enter Y at the prompt to confirm the reset.

If your system has autoboot enabled, override the autoboot by pressing any key within 10 seconds of seeing the following display on the console:

Autoboot from primary boot path enabled.

To override, press any key within 10 seconds.

Boot your system from the alternate boot path by responding N to the Boot from primary boot path (Y or N)?> prompt and Y to the Boot from alternate boot path (Y or N)?> prompt.

Respond Y to the Interact with IPL (Y or N)?> prompt.

The following example represents a boot sequence received at the console for a Series 950/980 with autoboot enabled, ending with the system displaying the ISL prompt. Sequences for other installations can vary.

CTRL B

CM> TC

Processor-Dependent Code (PDC) revision 2.8

Console path = 2/4.1.0.0.0.0.0

Primary boot path = 2/4.0.0.0.0.0.0

Alternate boot path = 6/4.3.0.0.0.0.0

48 MB of memory configured and tested.

Autoboot from primary path enabled.

To override, press any key within 10 seconds. RETURN

** A key is pressed **

Boot from primary boot path (Y or N)?> N

Boot from alternate boot path (Y or N?> Y

Interact with IPL( Y/N ) Y

Booting.

Console IO-Dependent Code (IODC) revision 3

Boot IO-dependent Code (IODC) revision 3

Booted.

ISL Revision 2738 September, 1987

ISL>

Disable the autoboot flag. At the ISL prompt, enter:

ISL> AUTOBOOT OFF

To confirm that FASTSIZE is set to 0000000F, follow these steps:

Display the current FASTSIZE value. At the ISL prompt, enter:

ISL> DISPLAY

Fastsize value is 0000000F

.

.

.

If FASTSIZE is any value other than 0000000F, you must change the value of FASTSIZE to 0000000F. At the ISL prompt, enter:

ISL>FASTSIZE F

If you changed the value of FASTSIZE, you must reset the system for the new value to take effect. Repeat the steps described in “Performing a Configuration Update,” beginning with step 2.

Use the UPDATE command to execute a configuration update. At the ISL prompt, enter:

ISL> UPDATE

The system prompts for the correct date and time shortly after receiving the UPDATE command. If the date and time are correct, press Return at the date prompt. If the date or the time is incorrect, press N and respond as requested with the correct date and time (in 24-hour format).

The configuration update proceeds for approximately 10 minutes. After it completes the update, your system resets itself.

Boot from the primary boot path by responding Y to the Boot from primary boot path (Y or N)?> prompt.

Respond Y to the Interact with IPL (Y or N)?> prompt.

Use the ISL AUTOBOOT command to enable the autoboot feature. At the ISL prompt, enter:

ISL> AUTOBOOT ON

Use the START command with the -R restart option, to start your system with the restart feature enabled. At the ISL prompt, enter:

ISL> START -R start_options

NOTE: When you get to the ISL prompt, be sure to use the -R option with START so that reboot occurs automatically the next time that a system abort occurs. If you do not use the -R option with START, the system does not reboot after a system abort.

When startup is complete, perform a soft reset of your system, to test successful installation and configuration of AutoRestart/iX. At the console, enter:

CTRLB

CM> TC

After resetting itself, the system executes the ISL commands in the system autoboot file. The first ISL command invoked is usually DUMP. If the dump-to-disk feature has been correctly configured, the DUMP facility locates the first dump file and proceeds to dump-to-disk.

After dump-to-disk is successfully accomplished, the next command in the system autoboot file is invoked.

You can now return your system to a normal operating state.

______________________________________________________________

Want to get-on Google’s first page and loads of traffic to our website? Hire a SEO Specialist from Ocean Groups seo pecialist

[tcollins]

Hi,

Has any progress been made on this?

cheers
Tristan

[support-joy]

Tristan,

Sorry for the late reply. Thank you for the screenshot and log file details. This issue has been fixed. The fix would be released in ME 9.0 M1 due this week and a patch release of 8.6 is due in 2 weeks.

[tcollins]

Hi Joy,
Is this fix available yet? I’m not seeing anything in your pulse service to indicate that it is.

cheers
Tristan

[Brian Fernandes]

Tristan,

Yes, we did fix this issue in 9.0M1. It will also be fixed in the upcoming 8.6.1 release due in a week or two.

As far as 8.6.0 is concerned, you can edit your .project file and add the following element to the <natures> element at the end of all the natures listed

<nature>org.eclipse.wst.jsdt.core.jsNature</nature>

, then close and reopen your project and validate it – the errors should now disappear.
Can you confirm if this works for you?

Sorry for the inconvenience caused.

[Author]

Posts