Skip to main content
M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
January 19, 2010
Question

Blank error message - IE 6

  • January 19, 2010
  • 11 replies
  • 3062 views

Today we're seeing the attached error message while using Principal Administrator.

Advice on why this is happening / how to troubleshoot and fix?

Notes:

1. Repeatable for given user on given client accessing production.

2. Does not occur for same user on same client accessing a test Windchill server.

3. Clearing both IE and Java caches has no effect.

4. No known recent changes to IE or Windows.

11 replies

S
sdrzewiczewski10-Marble
10-Marble
January 20, 2010
I would check the Tomcat log or M.S. log to see if there is any info there.
May need to clear the Tomcat cache???



Nice getting to meet you last week. You'll be glad to know my eye doctor
gave me an Alcon sample for my contact lens solution. J



Steve D.


C
colmacpro1-Visitor
1-Visitor
January 20, 2010

Had this problem last week and it took a bunch of time to figure it out.

the following is from the java site.

To clear the Java Plug-in cache:

  1. Click Start > Control Panel.

  3. Double-click the Java icon in the control panel.
    The Java Control Panel appears.
  1. Click Settings under Temporary Internet Files.
    The Temporary Files Settings dialog box appears.
  1. Click Delete Files.
    The Delete Temporary Files dialog box appears.
There are three options on this window to clear the cache.
  1. Delete Files
  2. View Applications
  3. View Applets
  1. Click OK on Delete Temporary Files window.
    Note: This deletes all the Downloaded Applications and Applets from the cache.

  3. Click OK on Temporary Files Settings window.
    Note: If you want to delete a specific application and applet from the cache, click on View Application and View Applet options respectively.
Hope this helps
Joe
M
22-Sapphire I
MikeLockwood22-Sapphire IAuthor
22-Sapphire I
January 20, 2010
Great thought. This was our first action for troubleshooting - didn't make any difference for us.

This also happened once in that past to one person. We deleted their account and re-created. It worked ok for a while but then re-appeared. Now it occurs for site admin as well.

baffling...
R
rdayalu1-Visitor
1-Visitor
January 20, 2010
Mike,



Try this. We do this all the time.



Delete priv9.ser for the user (please see below)



Have the user Accept (Grant all permissions) it prompts next time.



Regards,

Rekha







From: Lockwood,Mike,IRVINE,R&D [
M
22-Sapphire I
MikeLockwood22-Sapphire IAuthor
22-Sapphire I
January 20, 2010
Great thought - Just tried it - no effect.

Ok, I'm getting desperate - and now offering a LARGE cup of coffee (or a beer if you like) for whoever solves this mystery.

thanks!
J
jessh12-Amethyst
12-Amethyst
January 20, 2010
Note that all the Java cache (and priv.ser) things only apply to applets
(and PSE).

As I recall the original issue didn't involve any applets.

Lockwood,Mike,IRVINE,R&D wrote:
> Great thought - Just tried it - no effect.
>
> Ok, I'm getting desperate - and now offering a LARGE cup of coffee (or
> a beer if you like) for whoever solves this mystery.
>
> thanks!
>
P
PreetiGupta15-Moonstone
15-Moonstone
January 20, 2010
This issue is reproduced at every client machine for same windchill user account. I don't think it is a client issue. Just looked at tomcat errors when I do the same operation.....

Nested exception is: java.lang.Exception: , msg=java.lang.Exception: , lmsg=java.lang.Exception:
Nested exception is: java.lang.Exception
---------- exception -----------------
wt.federation.FederationServicesException: java.lang.Exception:
Nested exception is: java.lang.Exception:
at com.infoengine.connector.DataAccessObject.execute(DataAccessObject.java:215)
at wt.federation.RPCHelper.doAction(RPCHelper.java:497)
at com.ptc.core.ca.co.client.doer.CoDoerHelper_Soap.executeTask(CoDoerHelper_Soap.java:52)
at com.ptc.core.ca.co.client.doer.CoDoerHelper.executeTask(CoDoerHelper.java:208)
at com.ptc.core.ca.co.client.doer.CoAbstractTaskDoer.executeTask(CoAbstractTaskDoer.java:211)
at com.ptc.core.ca.co.client.doer.CoAbstractTaskDoer.execute(CoAbstractTaskDoer.java:87)
at com.ptc.core.ca.co.client.doer.CoDefaultModelTaskDoer.execute(CoDefaultModelTaskDoer.java:129)
at com.ptc.core.ca.co.client.primitive.CoDataDrivenEnumerator.updateModel(CoDataDrivenEnumerator.java:249)
at com.ptc.core.ca.co.client.element.CoElement.default_init(CoElement.java:614)
at com.ptc.core.ca.web.client.layout.WebLayoutRowRenderHandler.render(WebLayoutRowRenderHandler.java:186)
at com.ptc.core.ca.web.client.element.WebRenderHandler.render(WebRenderHandler.java:117)
at com.ptc.core.ca.web.client.element.WebElementUtils.render(WebElementUtils.java:387)
at com.ptc.core.ca.web.client.layout.WebLayoutRow.render(WebLayoutRow.java:226)
at com.ptc.core.ca.co.client.element.CoElement.default_render(CoElement.java:709)
at com.ptc.core.ca.co.client.element.CoElement.default_draw(CoElement.java:558)
at com.ptc.core.ca.co.client.element.CoElement.draw(CoElement.java:509)
P
pyalavarthi1-Visitor
1-Visitor
January 20, 2010
Looks like issue with user data corruption in the database. We ran into this
type of user issue multiple times.
I use the following sql script to check if the user data in database is
fine. This should return only one record if everything is ok. In corrupted
cases it will either return more than one result or none. Most of the time I
notice user corresponding record in the remoteobjectinfo table is deleted.

select * from remoteobjectid
where ida2a2 in (
select remoteid from remoteobjectinfo
where ida3a3 in (
select ida2a2 from wtuser where name like '%*<username>*
%'
)
)

Regards,
Prathap
P
PreetiGupta15-Moonstone
15-Moonstone
January 21, 2010
This is becoming a mystery now, I deleted the tomcat cache, everything was fine. As soon as added two users... problem comes bach within 5 minutes...

Atleast I can reproduce the issue...
J
jessh12-Amethyst
12-Amethyst
January 21, 2010
Which release/MOR is this again?

--
Jess Holle

Gupta,Preeti,IRVINE,R&D wrote:
> This is becoming a mystery now, I deleted the tomcat cache, everything
> was fine. As soon as added two users... problem comes bach within 5
> minutes...
>
> Atleast I can reproduce the issue...
>
Show more replies
Terms & ConditionsCookie settingsAccessibility statement