C library issue

Question

Hello all - our app (on UDS 5.2.0) uses a C library and now we are upgrading the library. Everything seems ok while importing, compiling and distiriuting the updated library but when we try to integrate the workspace with the changes we get an error -
Forte_cl0: SYSTEM ERROR: Error fetching system object (1,0xa5e0e,0)
fromshadow!Class: qqsp_ImplementationException
Error #: [1101, 279]
Detected at: qqrp_ShadowRepositorySession::Fetch(FlatObject)
Last TOOL statement: method
abSurrogateRepositoryClient.IntegrateWorkspace
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= D89DBB80-4A53-11DA-92CE-76AFF250AA77:0x69b:0x2, taskId =
[D89DBB80-4A53-11DA-92CE-76AFF250AA77:0x69b:0x2.18]) in
application
"FTLaunch_cl0", pid 1352 on node TESTPRO in environment DEVP
And after this error no matter no matter what we do - compile,revert changes, unistall the library, the same error appears when we intergate workspace and we have to recreate the whole thing from scratch - the repos, environment etc. We are not using shadow repositories and are directly connected to the central repos. Has anyone seen this error before? Is there any issue wuth using C libraries on UDS? Any help would be appreciated...thanks!

Answer 1

I got the same issue, trying to use UDS 5.2 and UDS 5.0 concurrently on my Win2K machine (I was testing upgrading to UDS 5.2). The solution is probably the same for other OSs.
I have included the email correspondance with Sun below.
Stephen.
Hi Mary,
Once I added the UDS 5.2 userlib and install/bin directories to my PATH, repository issue went away.
You can close this request.
Thanks for oyur help,
Stephen.
-----Original Message-----
From: Mary McCarthy [mailto:[email protected]]
Sent: 16 February 2005 10:45
To: Boyatsis, Steven
Cc: Montgomery, Stephen (LIT); Smyth, Ray(LIT)
Subject: Re: Case # 64448594 - UDS 5.2 Shadow Repository Issue
Hi Steven,
I'm just checking in to learn the latest status of your shadow repository configuration. Have you been able to get past the ImplementationException?
Thanks,
Mary
Mary McCarthy wrote:
Hi Stephen,
I checked with the backline team and found that strictly speaking, we
don't recommend installing more than one UDS release runtime per
machine. This is because the installer assumes only one release and
it doesn't cater for multiple releases. Below is their advice for
getting this work properly. Please keep us posted with your results.
Thanks,
Mary
The problem comes with the values for the environment variables FORTE_*, WWW_* and PATH being different for each UDS release runtime. They may reside in any of the following Windows registry folders and are searched in this order.
HKEY_CURRENT_USER\Environment
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
HKEY_CURRENT_USER\Software\ForteSoftwareInc\Forte
HKEY_LOCAL_MACHINE\SOFTWARE\ForteSoftwareInc\Forte\<release>
In the case of the environment variables FORTE_* and WWW_*, the UDS runtime is able to retrieve them from the release specific folder in the Windows registry, so they should not present a problem, if they are only defined there with their release-specific value.
HKEY_LOCAL_MACHINE\SOFTWARE\ForteSoftwareInc\Forte\<release>
The environment variable PATH is used by the operating system when activating the UDS runtime libraries in %FORTE_ROOT%\install\bin, so the trick is to make sure that each UDS runtime has a distinct setting for PATH. Beware that only the following Windows registry folders are searched by the operating system.
HKEY_CURRENT_USER\Environment
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment
The Windows NT Services for each release needs to start up as its own service account and not as the default 'Local System acount'.
UDS Environment Manager <release>
UDS Repository Manager <release>
I suggest that the customer creates two service accounts.
uds5_0_9
uds5_2_0
Log in to each account and set the environment variable PATH appropriately as a User environment variable and not as a System environment variable. Check the value of PATH in the following Windows registry folder.
HKEY_CURRENT_USER\Environment
Then change the four Windows NT Services to start up as the appropriate service account and then recycle the Windows NT Services in order that they will pick up the new local user registry hive that has the appropriate PATH setting.
As with some things Windows related, the customer may need to recycle the operating system, if the new local user registry hive doesn't get loaded after these changes.Montgomery, Stephen (LIT) wrote:
Hi Mary,
I have further investigated this and I'm pretty sure it has to with
having UDS 5.2 and UDS 5.0.9 installed on the same PC:
Current Win2k Environment Settings :- defaultenv.txt
I have my environment settings pointing to UDS 5.0, installed at
c:\forte. I have UDS 5.2 installed at c:\forte52. I was using the
following shortcut to use my UDS 5.2 workspace:
where the full target command is "C:\forte52\install\bin\ftexec.exe
-fr
bt:c:\forte52\repos\dev52 -fi bt:c:\forte52\userapp\forte\cl0\forte
-fm "(n:96000,x:128000)" -fns gardenia:6101 -fw montgoms_workspace"
I consistently get the workspace error below either from importing a
public plan, searching for text etc,
SYSTEM ERROR: Error fetching system object (1,0xa5e11,0) from shadow!
Class: qqsp_ImplementationException
Error #: [1101, 279]
Detected at: qqrp_ShadowRepositorySession::Fetch(FlatObject)
Last TOOL statement: method
abSurrogateRepositoryClient.ListPublicPlansWithData
Error Time: Mon Feb 07 07:51:48
Exception occurred (locally) on partition "Forte_cl0_Client",
(partitionId
= 5A4CD430-75F6-11D9-9ACC-6BC7A19DAA77:0xf06:0x1, taskId =
[5A4CD430-75F6-11D9-9ACC-6BC7A19DAA77:0xf06:0x1.13]) in application
"Forte_cl0", pid 804 on node DWS186 in environment T_env.
However, if I set up a script to change the FORTE_ROOT variable to
c:\forte52 and add the c:\forte52\userlib and c:\forte52\install\bin
to start of my PATH variable, the error disappears. Previously I had
tried just to change the FORTE_ROOT variable to C:\forte52 and then
run the shortcut. This isn't enough though - you need to include the
install and userlib directories on the PATH.
Stephen.
-----Original Message-----
From: Mary McCarthy [mailto:[email protected]]
Sent: 03 February 2005 15:44
To: Montgomery, Stephen (LIT); Boyatsis, Steven
Cc: Smyth, Ray(LIT)
Subject: Re: Case # 64448594 - UDS 5.2 Shadow Repository Issue
Hi Stephen and Steven,
It sounds like the shadow still thinks it's detached. But the fact
that you can do this through fscript contradicts that.
Can you try attaching the shadow again? It might be a good idea to
get everything checked in, all the shadows attached, then recreate
them again. I've reviewed our list of known issues and we haven't
seen repository corruption in ages.
Thanks,
Mary
Montgomery, Stephen (LIT) wrote:
Hi Mary,
All of our Forte environments (including the repositories) run on AIX
5.1. We have a large number of back-end UDS components that also run
on AIX. Our clients and developers all use Windows 2000 SP4 to run
the application front end/gui.
The issue I have raised is being experienced only on Win2k when I've
created a shadow repository for my new workspace using UDS 5.2.0
Developer Edition. I then detach and reattach to pull in all the
public plans into my local 'cache' in shadow. I then receive this
intermittent error when I have tried importing new public plans,
searching for text and once integrating...
Hope this helps,
Stephen.
-----Original Message-----
From: Mary McCarthy [mailto:[email protected]]
Sent: 02 February 2005 18:10
To: Montgomery, Stephen (LIT); Boyatsis, Steven
Subject: Case # 64448594 - UDS 5.2 Shadow Repository Issue
Hi Steven,
I've been assigned to work with you on this support issue. I'm not
terribly familiar with AIX. Would you mind clarifing the AIX version
for me? Which portion of UDS is running on AIX, the server?
Thanks,
Mary
Hardware Platform: IBM
Component Affected: Languages/Development Tools OS and Kernel Version:
AIX gardenia 1 5 0001DC5A4C00 Describe the problem: UDS 5.2 Shadow
Repository Issue.
Background Information:
1. Running UDS 5.2.0 on client and server. Remote repository is
newlycreated UDS 5.2.
2. Created shadow repository for workspace on Win2k PC.
3. Detached shadow to pull down/cache workspace plans locally on my
machine 4. Attached Shadow to reconnect.
5. Have been happily checking out/unchecking, branching, updating,compiling etc in shadow workspace for 2-3 days.
Shadow Repository Info:
Repository information:
Connected to repository bt:c:\forte52\repos\dev52.
Connected to an attached shadow (65).
Current workspace is (montgoms_workspace)
Workspace created: 24-Jan-2005 10:44:43
Last Updated: 26-Jan-2005 11:27:05
Up-to-date with integration #2.
Last Integrated: (Never)
Repository create date 13-Jan-2005 10:23:46.
Persistent counter value (75737).
This is a compressed repository.
Shadow is on central repository dev_repos52.
List of workspaces cached in this shadow.
advap_workspace (220541)
montgoms_workspace (220892)
2 of a maximum of 15 workspaces are currently cached in thisshadow.
Completed printing repository information.
Issue:
1. Attempt to include public plan from remote repository by Plan,Include Public. The following exception is raised and the list of
available public plans is not shown.
SYSTEM ERROR: Error fetching system object (1,0xa5e11,0) from shadow!
Class: qqsp_ImplementationException
Error #: [1101, 279]
Detected at: qqrp_ShadowRepositorySession::Fetch(FlatObject)
Last TOOL statement: method
abSurrogateRepositoryClient.ListPublicPlansWithData
Error Time: Thu Jan 27 10:04:49
Exception occurred (locally) on partition "Forte_cl0_Client",(partitionId
= CAF940B0-3D47-11D9-BCA0-F9B6F329AA77:0x7277:0x1, taskId =
[CAF940B0-3D47-11D9-BCA0-F9B6F329AA77:0x7277:0x1.13]) inapplication
"Forte_cl0", pid 1036 on node DWS186 in environment T_env.
This exception is raised for each workspace cached in the local
shadowbut I can import public plans into the workspaces using fscript.
I also encountered the same error while performing a word search on
another workspace in another UDS5.2 repository
Thanks,
Stephen
This system is SRS Net Connect enabled: No I will be sending an
Explorer file: No List steps to reproduce the problem(if applicable):
When was the problem first noticed: week ago The problem is: staying
the same Any changes recently?: None What software is having the
problem?: UDS 5.2.0 on Windows 2000 SP 4.
Desired start date for this service request: normal (according to
service coverage) Alternate contact first name: stephen Alternate
contact last name: montgomery Alternate contact phone: [phone]
445629 Alternate contact email: [email protected] Email
copy of original Service Request to primary contact: Yes Preferred
Method of Response: Email Email copy of Service Request to alternate
contact: Yes Email primary and alternate contacts when a Sun
engineer updates this Service Request: Yes
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\n0105003\Application Data
CLASSPATH=.;C:\Program Files\SQLLIB\java\db2java.zip;C:\Program
Files\SQLLIB\java\runtime.zip;C:\Program Files\SQLLIB\bin
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=DWS186
ComSpec=C:\WINNT\system32\cmd.exe
DB2INSTANCE=DB2
DB2TEMPDIR=C:\Program Files\SQLLIB
FORTE_ROOT=c:\forte
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\n0105003 ICM_FOLDER=Information
Catalog Manager IMNINST=help IMNINSTSRV=C:\PROGRA~1\IBM\IMNNQ
INCLUDE=C:\Program Files\Microsoft Visual C++ Toolkit
2003\include;C:\Program Files\Microsoft SDK\include;C:\Program
Files\SQLLIB\INCLUDE;C:\Program Files\SQLLIB\TEMPLATES\INCLUDE
Lib=C:\Program Files\Microsoft Visual C++ Toolkit 2003\lib;C:\Program
Files\Microsoft SDK\Lib;c:\sybase\LIB LOGONSERVER=\\BART
MDIS_PROFILE=C:\Program Files\SQLLIB\METADATA\PROFILES
NUMBER_OF_PROCESSORS=1
OS=Windows_NT
Os2LibPath=C:\WINNT\system32\os2\dll;
Path=C:\WINNT\MS\SMS\CORE\BIN;C:\sybase\JS-12_5\bin;C:\sybase\OCS-12_5
\dll;C:\sybase\OCS-12_5\bin;C:\Program Files\Microsoft Visual C++
Toolkit 2003\bin;C:\Program Files\Microsoft
SDK\Bin;C:\Perl\bin\;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem
;c:\sybase\dll;c:\sybase\bin;C:\Program
Files\Rational\common;C:\Program Files\SQLLIB\BIN;C:\Program
Files\SQLLIB\FUNCTION;C:\Program Files\SQLLIB\SAMPLES\REPL;C:\Program
Files\SQLLIB\HELP;C:\PROGRA~1\IBM\IMNNQ;C:\PROGRA~1\TextPad
4;C:\JBuilderX\jdk1.4;C:\JBuilderX\jdk1.4\bin;C:\Program Files\Common
Files\GTK\2.0\bin;C:\Program Files\Executive
Software\Diskeeper\;C:\Program Files\Unrar;C:\Program
Files\Embarcadero\RSQL57;C:\Program
Files\Embarcadero\Feb2001Shared;C:\Program
Files\Embarcadero\RSQL57;C:\Program Files\Embarcadero\Feb2001Shared
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 9, GenuineIntel
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0209
ProgramFiles=C:\Program Files
PROMPT=$P$G
SMS_LOCAL_DIR=C:\WINNT
SYBASE=C:\sybase
SYBASE_JRE=C:\sybase\shared-1_0\JRE-1_3
SYBASE_OCS=OCS-12_5
SystemDrive=C:
SystemRoot=C:\WINNT
TEMP=C:\Temp
TMP=C:\Temp
USERDNSDOMAIN=lit.lmig.com
USERDOMAIN=LIT0
USERNAME=n0105003
USERPROFILE=C:\Documents and Settings\n0105003
VCToolkitInstallDir=C:\Program Files\Microsoft Visual C++ Toolkit
2003\ VWSPATH=C:\Program Files\SQLLIB VWS_FOLDER=IBM DB2
VWS_LOGGING=C:\Program Files\SQLLIB\LOGGING VWS_TEMPLATES=C:\Program
Files\SQLLIB\TEMPLATES windir=C:\WINNT