Lookout opc or link problems

I am using Lookout 6.0.2 on a new Win XP desktop. The Lookout OPC client object is used for communications via Rockwell Software RSLinx's (Professional Rev 2.43.01.23) OPC server to ControlLogix PLC's over ethernet. In other words, the Lookout communicates with RSLinx by OPC, and the RSLinx communicates with PLC's by ControlNet.
We have 3 Lookout processes, one which is the "server" process, and contains the OPC Client object. The other 2 process files are "client" processes, and reference the OPC Client object by symbolic link.
We have many Lookout switches in the "client" processes, that are remoted to a tag in the ControlLogix PLC using symbolic link. A typical link for a remoted switch is:
..\..\[Link_to_Drivers]\OPCclient1.PLC_12.Online.SWITCH_TAGNAME
OR IF USING ABSOLUTE REFERENCE: \\ComputerName\ProcessName\[Link_to_Drivers]\OPCclient1.PLC_12.Online.SWITCH_TAGNAME
In this way, the Lookout switch object has a read/write link.
The problem is this: Periodically the write link will stop working. When this happens, all the Lookout switches and even the Lookout pots will lose ability to write to PLC, but the read links are still working. We can read the data and the switch positions, but the changing setpoints with the pots and operating equipment with the switches is then impossible. This "lock up" can be fixed by closing down all the Lookout processes (but not Lookout), and then restarting the Lookout processes.
This problem is intermittant and not repeatable. Does anyone have idea how to troubleshoot this problem, or have an way to isolate and fix this problem? Thanks!

This problem is fixed by lookout 6.0.2 updates. It can be downloaded from http://joule.ni.com/nidu/cds/view/p/id/506/lang/en
You need first to login MyNI, and then download lo602_updates.zip. Unzip it and copy all files to lookout folder.
This update is applied to Lookout 6.0.2 server system. You don't need to copy these files to client system.
Ryan Shi
National Instruments

Similar Messages

Lookout opc problems

I am using Lookout 6.0.2 on a new Win XP desktop. The Lookout OPC client object is used for communications via Rockwell Software RSLinx's (Professional Rev 2.43.01.23) OPC server to ControlLogix PLC's over ethernet. In other words, the Lookout communicates with RSLinx by OPC, and the RSLinx communicates with PLC's by ControlNet.
We have 3 Lookout processes, one which is the "server" process, and contains the OPC Client object. The other 2 process files are "client" processes, and reference the OPC Client object by symbolic link.
We have many Lookout switches in the "client" processes, that are remoted to a tag in the ControlLogix PLC using symbolic link. A typical link for a remoted switch is:
..\..\[Link_to_Drivers]\OPCclient1.PLC_12.Online.SWITCH_TAGNAME
OR IF USING ABSOLUTE REFERENCE: \\ComputerName\ProcessName\[Link_to_Drivers]\OPCclient1.PLC_12.Online.SWITCH_TAGNAME
In this way, the Lookout switch object has a read/write link.
The problem is this: Periodically the write link will stop working. When this happens, all the Lookout switches and even the Lookout pots will lose ability to write to PLC, but the read links are still working. We can read the data and the switch positions, but the changing setpoints with the pots and operating equipment with the switches is then impossible. This "lock up" can be fixed by closing down all the Lookout processes (but not Lookout), and then restarting the Lookout processes.
This problem is intermittant and not repeatable. Does anyone have idea how to troubleshoot this problem, or have an way to isolate and fix this problem?

doug:
You may want to repost in the Lookout board:
http://forums.ni.com/ni/board?board.id=190
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

How can I edit the database in Lookout OPC Modbus driver OPC sever with the address that has a write attribute?

When I use Lookout Modbus driver OPC to communicate with my instrumnets, I edited the database number such as 41202 that has a Write attribute in my instrumnet manual, the OPC explorer got bad data, and the OPC server gave the illegal address alarm, when I input the address such as 41203 that has R/W attribute, it worked very well. Is there a way to fix this problem. When I used other OPC server, there was no this kind of problem. Thanks!

Thanks for your suggestion. I checked the Modbus manual of my instrument, the register is 16 bit. I tried to edit the data according to the Modbus data member in lookout modbus drivere server for several different member, but the OPC still gave me the illegal address. I think the problem may be produced by their attribute, for the address 1201 and 1202, they have the write attribute, for other addresses, they have W/R attribute, and they can be read or write through Lookout OPC server perfectly. when I used the demo OPC server from other company, it can work well, but it is not convinient for me to use Labview when I use that software. I prefer NI Lookout OPc server. I am using the Lookout 4.5. I am wondering whether the Lookout has some shortcoming when I
use the Modbus driver. Please give me any suggestion, is there any newest version of Lookout OPC sever? Thanks!

Lookout OPC reads A-B PLC Output word bit 15 as negative.

I am using LabVIEW and Lookout OPC driver to read an output word from an Allen-Bradley PLC and display the bit values as booleans. When bit 15 goes to a logic one, the value the opc driver reads goes negative. this causes the Labview Number to boolean array converter to 'mis-read' the bit values. How can I prevent this mis-read?

I dealt with this problem a couple of years ago.
I had to write a VI that decode the bits and fixed it.
THe VI just checked the MSB and acted accordingly.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Storing OPC URL link as String

Hello
I am having trouble with reading OPC URL link in correct format form the System.ini file. (LabView 8.2)
I am able to read the OPC URL link from System.ini file and save it as a string, but in the OPC URL link it contain some back slash and that is where the problem start.
I have old EXE file created in LabView, which read the same OPC URL and able to communicate. I cannot provide this EXE file because it is very big.
Please take a look the System.ini file where OPC URL link are stored, and the OPC test.vi.
I try to add some extra back slash to take care of escape sequence, but I could not communicate with OPC server.
Please help me
Thank you,
Attachments:
OPC test.vi ‏45 KB
System.ini ‏1 KB

Hello Guys
Thank to Rolf, Ravens and GerdW
As Rolf point out that read raw string flag on the Read key.vi takes care of all escape sequence problem. Also do the same thing when you use the Write Key.vi. So if the Value type is String then this flag comes up, but if not careful we can easily miss that.
Here is the some more info.
read raw string? Specifies whether the string was written without escaping unprintable and backslash (\) characters. If FALSE (default), the VI replaces any unprintable characters in the string, such as <ESC>, with a backslash and two Hex characters (\xx). If TRUE, the VI does not convert the unprintable characters in the string.
write raw string? specifies whether to write the string without escaping unprintable and backslash (\) characters. If FALSE (default), the VI converts any backslashes (\) to double backslashes (\\) and replaces any remaining unprintable characters in the string, such as <ESC>, with a backslash and two Hex characters (\xx). If TRUE, the VI does not convert the unprintable characters in the string.
I think this is very important point to keep in mind.
Thank you

"Link Problem" in Incident Form does not seem to work right? How do I do it correctly?

1. The Link Problem tool in the task pane on our Incidents, do not seem to actually link the Incident to the Problem.
2. I can link the two by going to the Problem and adding it on the related items tab, but this is very time consuming in a call center environment, especially during an outage where we are relying a lot more on Problem and root cause analysis.
3. I have tried creating the incident and applying, then doing the Link Problem tool and selecting the problem, then applying again and selecting OK to close the incident. Again it doesn't work for me.
What am I doing wrong, number one?
Can we do this without manually opening the problem for every incident and attaching from there?
3. Can I build an incident template that will automate the Attachment to the problem at creation? (Tried this today to and it wouldn't work, but then again, the Link Problem might again be the culprit) This would be great for real time saving during
an outage. Once outage is found, I could create the template with all the necessary items filled out, and would like to have it automatically attach to the specific problem I choose at template creation, and that way analysts can simply apply template, and
click OK when they get a call related to the outage.

Thanks for the response Thomas!
The functionality seems to work just fine. I use the LINK PROBLEM and it pops up the problem search box, I search for and select a Problem, I then select it and click ok, and I get no error saying the relationship was not created.
The problem is, when I open the problem after that, there is never any relationship showing in related items there, as it says there should be.
Also, to point out, I am talking about newly created Incidents. I tried even using APPLY prior to doing the LINK PROBLEM but it still did not work. I suspect it may be a workflow problem, where the workflow to create the incident has not completed, there
for the relationship is not completed.... and I get no error.
In my work environment, we have analysts during outages taking a call every 30 seconds, and I need a more efficient way for this system to work. As of now, they spend 1-2 minutes doing the ticket, and that is too long.
I have decided to try a newb way, where I created an Incident (GENERIC OUTAGE) that folks can use, and every 15-30 minutes during an outage, I can open the problem and search for open incidents with that title, and attach all that I find from the problem
side. This is assuming that once attached they will not show up in the search to attach the next time lol. Also this assumes that if attached from the problem, they will auto resolve when the problem is resolved.
I am rusty on my programming, and am currently trying to get refreshed. I am sure that would come in handy for this :)
Oh and lastly, one additional tidbit that will make this clearer, with regard to work flow, we re also running our Service Manager in our help desk, virtualized, as they have not upgraded to Win 7 yet :(. So that compiles my time to add ticket issue :(.

InDesign to Adobe Acrobat to Adobe Reader Link problem

Hi - I'm responsible for a long conversation about link problems in creating file links in InDesign that did not work in Acrobat. At the end of that long discussion, I thought I solved the problem, but didn't. Since then, I've been MUCH more observant.
The problem appears to take place in Adobe Reader.
My home computer on Win7 is different than my work Computer (XP), but I have the same software on both.
At work, I discovered that when I clicked on a PDF, it worked fine, that its links opened a new PDF window, but when I clicked on links on the second document, the links failed and Microsoft returned an error message telling me that I was screwed. Because I was screwed, I couldn't see what was in the path of that error.
It turns out that for some unknown reason (which you might clarify for me), my Adobe Readers are attempting to open my documents in Internet Explorer and that just won't work.
What I observed at home is that I made 5 test documents in ID, and ported them to Acrobat. As it turns out, my default for opening PDFs is Adobe Reader, which I saw on the chrome of the first document I opened. When I clicked a link, and I got the error message, I noticed my browser was up.
When I set my default for opening in Acrobat, everything worked like a charm! How about that!
Now then, what that says to me is that Adobe Reader is to be used exclusively with a browser, so if the people who are going to read your internal PDF files with Reader without those files being on a web server of some type, you are totally screwed. The only way you can use Reader is if you click on the file and bring it up directly. Don't rely on linking to other documents.
I mean, that is what it seems to me.
Now, I am creating a big project for an environment without a webserver and obviously my sense of panic is palpable. That said, I believe that all my users can read my files using Acrobat (to be tested tomorrow), which I hope means I can breathe a bit easier.
Do any of you have any thoughts on this subject? If you are really curious, I can make a packet of test files available.

Karen_Little wrote:
The files and the PDFs are all in the same directory.
The tests are on local drives. All indesign files and their related PDFs were in the same directory.
The same for Word and its related PDFs. Note that the PDFs created by Word then read by Adobe Reader worked correctly. They all opened in Adobe Reader.
If the default program for opening PDFs is Acrobat, everything works correctly, with the added benefit of everything opening in a different window, which is what I want (yet to be tested at work). If the default program is Adobe Reader, the second generation of links do NOT work because Reader opens in Internet Explorer.
When I open a Word-created PDF with Acrobat, view the link, and click to the Actions menu, the action is "Open a file"
When I open an InDesign PDF with Acrobat and do the same, the action says "Open a web link"
Big BIG BIG bug.
Are you seeing the link commands by editing them in Acrobat? If not, try, so you can see the exact command and file or URL instruction. It still may be a bug, but you'll have better evidence when you report it here:
Adobe - Feature Request/Bug Report Form
And, you might want to try correcting a link command in Acrobat, to see if can work for both Acrobat and Reader.
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices

Re: Fwd: Link Problems With Borland C++ 4.52

I have seen this problem before in another context, and I'll offer the
cause and solution in the hope that they will apply to the Crystal problem.
Many Windows based applications rely on PASCAL calling conventions, which
change the way parameters are handled in function/method calls. They
indicate this by placing one of the following immediately before the
function name in the prototype declarations:
- pascal_far (or something like that)
- WINAPI
- some other typedef of either of the above
For example:
int WINAPI AddTotal(int valueA, int valueB);
Unfortunately, v2.0 of Forte does not provide any mechanisms for changing
the calling conventions of the prototypes in the generated C++ wrapper
library, so when you compile that code, the linker fails. I think that the
compiler may generate different symbols depending on calling conventions,
so that's why it fails.
To fix this, don't autocompile your code, but generate the distribution, go
into the generated C++ files and look for the function prototypes (I think
you can search for FORTE_NO_PROTOTYPES), add WINAPI to the appropriate
places in the prototype definitions (see above) and use fcompile to build
the library. Instructions for fcompile are in the Interfacing With
External Systems manual.
Hope this helps,
James
At 11:05 AM 5/29/97 PDT, you wrote:
>
We are trying to wrapper Crystal Reports from Forte. I know that there
are a number of other people in this same boat, as I've seen messages
posted here at various points during the past few weeks. We are having
a particular problem with getting the compile to go through, which we
have sent in to Forte Tech Support. I'm forwarding the message I sent
Tech Support to this group in the hopes that someone here may have
already seen and resolved a similar problem.
Thanks in advance for any help you can offer!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc. [email protected]
>
Date: Wed, 28 May 97 13:47:20 PDT
From: dg7077a
To: Forte Technical Support
Cc: Gardner, Steve
Subject: Link Problems With Borland C++ 4.52
Name of requestor: [Dale V. Georg / Alaiah Chandrashekar]
Company: [Indus Consultancy Services]
Phone for callback: [(610) 709-3956]
Customer Site: [Mack Trucks, Inc.]
Product: [Forte]
Version of Forte: [2.0.H.1]
Server OS: [SunOS 5.5.1]
Client OS: [Windows 3.1]
DBMS: [Oracle 7.2.3]
Reproducible?: [Yes]
Brief description: [Link Problems With Borland C++ 4.52]
Complete description of problem or question:
We are attempting to write a C-wrapper interface from Forte to Crystal
Reports' Report Engine. We are using Borland C++ version 4.52.
Unfortunately, we have been unable to get a clean compile after a day
and half of effort. We get as far as the link stage of the
compilation, and
the compiler aborts with an "Unknown symbol" error message for each
of the functions we are trying to wrapper. We have tried a number of
ideas to fix this problem, and are continuing to try to solve it on
our own,
but any help would be greatly appreciated. Please have someone call
Alaiah Chandrashekar at the number above as soon as possible.
Thanks!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc. [email protected]
James Urquhart [email protected]
Product Manager phone: (510) 986-3513
Forte Software, Inc. fax: (510) 869-2092

James,
Thanks for your quick response. Yesterday we had been running down
the path of examining the calling conventions and trying to change them
to PASCAL, but without much success. After receiving your note, we
went back over it again, and this time we were able to finally to piece it
together. In addition to editing the Forte-generated .cc file to declare
the functions as PASCAL, we also had to turn off the compiler's case
sensitivity. (The Crystal .lib file had the function names in mixed case,
but the Borland compiler was generating all uppercase for the names.)
Now I had actually tried this yesterday and it didn't work (in fact it
generated a whole bunch of new errors) - because until we took a
second look at it today, I didn't realize that Borland's linker actually has
TWO flags that control case sensitivity. If you only turn one or the
other off, things can get pretty ugly looking. As soon as we turned
both of them off, the compile and link went beautifully. Again, thanks
for your help; hopefully we are over the worst of it now!
Dale
I have seen this problem before in another context, and I'll offer the
cause and solution in the hope that they will apply to the Crystalproblem.
>
Many Windows based applications rely on PASCAL callingconventions, which
change the way parameters are handled in function/method calls.They
indicate this by placing one of the following immediately before the
function name in the prototype declarations:
- pascal_far (or something like that)
- WINAPI
- some other typedef of either of the above
For example:
int WINAPI AddTotal(int valueA, int valueB);
Unfortunately, v2.0 of Forte does not provide any mechanisms forchanging
the calling conventions of the prototypes in the generated C++wrapper
library, so when you compile that code, the linker fails. I think thatthe
compiler may generate different symbols depending on callingconventions,
so that's why it fails.
To fix this, don't autocompile your code, but generate thedistribution, go
into the generated C++ files and look for the function prototypes (I think
you can search for FORTE_NO_PROTOTYPES), add WINAPI tothe appropriate
places in the prototype definitions (see above) and use fcompile tobuild
the library. Instructions for fcompile are in the Interfacing With
External Systems manual.
Hope this helps,
James
At 11:05 AM 5/29/97 PDT, you wrote:
We are trying to wrapper Crystal Reports from Forte. I know that
there
are a number of other people in this same boat, as I've seenmessages
posted here at various points during the past few weeks. We arehaving
a particular problem with getting the compile to go through, whichwe
have sent in to Forte Tech Support. I'm forwarding the message Isent
Tech Support to this group in the hopes that someone here mayhave
already seen and resolved a similar problem.
Thanks in advance for any help you can offer!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc.
[email protected]
>
>>
Date: Wed, 28 May 97 13:47:20 PDT
From: dg7077a
To: Forte Technical Support
Cc: Gardner, Steve
Subject: Link Problems With Borland C++ 4.52
Name of requestor: [Dale V. Georg / AlaiahChandrashekar
Company: [Indus Consultancy Services]
Phone for callback: [(610) 709-3956]
Customer Site: [Mack Trucks, Inc.]
Product: [Forte]
Version of Forte: [2.0.H.1]
Server OS: [SunOS 5.5.1]
Client OS: [Windows 3.1]
DBMS: [Oracle 7.2.3]
Reproducible?: [Yes]
Brief description: [Link Problems With Borland C++ 4.52]
Complete description of problem or question:
We are attempting to write a C-wrapper interface from Forte to
Crystal
>>
Reports' Report Engine. We are using Borland C++ version 4.52.
Unfortunately, we have been unable to get a clean compile after aday
and half of effort. We get as far as the link stage of the
compilation, and
the compiler aborts with an "Unknown symbol" error message foreach
of the functions we are trying to wrapper. We have tried a numberof
ideas to fix this problem, and are continuing to try to solve it on
our own,
but any help would be greatly appreciated. Please have someonecall
Alaiah Chandrashekar at the number above as soon as possible.
Thanks!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, [email protected]
James Urquhart [email protected]
Product Manager phone: (510) 986-3513
Forte Software, Inc. fax: (510) 869-2092-----------------------------------------------------------------------------------
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc. [email protected]
[email protected]------------------

Oracle 9.2.0.1.0 installation link problems.....HELP !!!!!!

Hi All
During installation of Oracle 9.2.0.1.0 on Linux, I received the following error:
Error:
Error in invoking target install of makefile
/opt/oracle/product/9.2.0.1.0/network/lib/ins_oemagent.mk
I did some research and found that it is executing the "relink" script. So I tried to debug it it. Here is the output:
[oracle@redash oracle]$ cd /opt/oracle/product/9.2.0.1.0/bin/
[oracle@redash bin]$ relink oemagent
chmod 755 /opt/oracle/product/9.2.0.1.0/bin
if [ linux = aix ]; then \
gcc -L/opt/oracle/product/9.2.0.1.0/lib/ -L/opt/oracle/product/9.2.0.1.0/rdbms/lib -L/opt/oracle/product/9.2.0.1.0/network/lib -L/opt/oracle/product/9.2.0.1.0/lib/ -L/opt/oracle/product/9.2.0.1.0/rdbms/lib -L/opt/oracle/product/9.2.0.1.0/network/lib -o dbsnmp /opt/oracle/product/9.2.0.1.0/network/lib/s0nmi.o -lvppdc /opt/oracle/product/9.2.0.1.0/network/lib/libvps.a \
/opt/oracle/product/9.2.0.1.0/network/lib/libnmi.a \
/opt/oracle/product/9.2.0.1.0/network/lib/libnmd.a /opt/oracle/product/9.2.0.1.0/network/lib/libnms.a /opt/oracle/product/9.2.0.1.0/network/lib/libnmt.a /opt/oracle/product/9.2.0.1.0/network/lib/libnml.a \
/opt/oracle/product/9.2.0.1.0/network/lib/libnmi.a /opt/oracle/product/9.2.0.1.0/net[i]Long postings are being truncated to ~1 kB at this time.

Before installing Oracle 9.2 on linux (i'm using redhat 7.2), there are some steps you have to issue.
Those link problems are related to the wrong version of binutils, you need binutils-2.10.0.18-1.i386.rpm
You need also JDK,to set some kernel parameters and so on..
However follow the steps of this link http://www.puschitz.com/OracleOnLinux.shtml
For me it worked.
Hope this helps
Tarek

Pro*C linker problems

System is Linux Mandrake 6.0 with Oracle 8i, with the 8i patch
applied.
What a nightmare that install was! Lots of permission problems,
unreadable directories, programs with no execute permission on
them and so on.
I now have a database up and running, and am trying to get Pro*C
working. The code was written on RedHat 5.2 with Oracle 8.0.5,
and worked fine there, so I know it is not a fundamental code
problem!
I have patched the pcscfg.cfg file as detailed in the patch FAQ
(with modifications for the slightly different paths under
Mandrake Linux).
When I compile the Pro*c file, I get many "undefined reference
to 'dbcon'" and "undefined reference to 'ctx'" errors from the
linker. This occurs whether I use a pre-defined list of specific
libraries in my own Makefile, or if I use the standard
demo_proc.mk makefile. I have used nm(1) on every place I can
think of, to try to find the required library/object, but to no
avail.
I appreciate that Oracle have so far only certified Oracle for
Linux against Redhat 6.0, but surely Mandrake can't be THAT
different ;-)
Does anybody have any ideas, known problems etc? I REALLY HOPE
that I don't have to switch to Redhat as the only solution - no
problem with Redhat, it would just require a tedious and
complicated system rebuild, which I don't have the time to do :-(
TIA
Mike Holden
null

Robert B gin (self) (guest) wrote:
: Robert B gin (guest) wrote:
: : Since I've last posted, I've installed RedHat 5.2 and
ditched
: : Slackware!
: : (btw, what a breeze - Hat's off to RH! very nice install!).
: : I've then installed oracle, have managed to setup
tnsnames.ora
: : so I can connect via sqlplus to my remote database (on
: VAX/VMS).
: : But now I have Pro*C linker problems with:
: : make -f demo_proc.mk build OBJS=test.o exe=test
: : (blah,blah,blah)
: : /usr/lib/crt1.o(.text+0x36): undefined reference to `main'
: : make: *** [build] Error 1
: : Does anybody out there have a similar problem?
: : Rob
: Duh! forget it... (EXE has to be caps... RTFM)
: (cryptic error message though?)
: works great!!!
Could you please tell me where I can get demo_proc.mk file
for Linux (RedHat)?
Thanks
null

OCCI Link Problem

Hi,
I am using Oracle 9.2.0.1.0, Redhat 9, gcc 2.96, glibc 2.3.2-11.9. I continually receive the following link problem:
/usr/bin/ld: warning: libclntsh.so, needed by /opt/ora9/product/9.2//lib/libvdc.so, not found (try using -rpath or -rpath-link)
/opt/ora9/product/9.2//lib/libocci9.a(occiUtil.o)(.text+0x99f): In function `oracle::occi::toUpperCase(basic_string<char, string_char_traits<char>, __default_alloc_template<true, 0> > const &)':
: undefined reference to `__ctype_toupper'
collect2: ld returned 1 exit status
Can anyone assist in resolving this issue?
Thanks
JD

Removed libocci9 and it compiled.
JD

Html link problem...

Hey!
Just wanned to say to those who answered my post on html link problems, that the problems I had were actualy because of the jdk version! I had jdk1.2 and now I have 1.3 and it works just fine.
thanx a lot to everyone who tried to help!!!

hehe i saw the topic "html link problem" posted by amidala and i thought " oh my god is she still struggling!" ;P
Kewl 'twas not a problem!

OCCI Link problem (Error LNK2019: unresolved external symbol) in VS2012

Hi,
I'm having a hard time with this. I'm trying to implement OCCI within my application. Error I'm getting is:
Error     1     error LNK2019: unresolved external symbol "public: static class oracle::occi::Environment * __cdecl oracle::occi::Environment::createEnvironment(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,enum oracle::occi::Environment::Mode,void *,void * (__cdecl*)(void *,unsigned int),void * (__cdecl*)(void *,void *,unsigned int),void (__cdecl*)(void *,void *))" (?createEnvironment@Environment@occi@oracle@@SAPAV123@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@0W4Mode@123@PAXP6APAX2I@ZP6APAX22I@ZP6AX22@Z@Z) referenced in function "private: bool __thiscall ServerDataLoader::getPreSuffixesFromDB(void)" (?getPreSuffixesFromDB@ServerDataLoader@@AAE_NXZ)     P:\code\VizTool\VizPortal\DwgDgnConverter\ServerDataLoader.obj     DwgDgnConverter
Error     2     error LNK1120: 1 unresolved externals     P:\code\VizTool\VizPortal\Debug\DwgDgnConverter.exe     1     1     DwgDgnConverter
Yes, it looks like linking problem,...but for me everything seems set-up.
- Included header files (from instantclient-sdk-windows.x64-11.2.0.3.0.zip)
- Included library path from OCCI download (11.2.0.3.0)
- Added oraocci11d.lib in linker
Please, what am I doing wrong?
Millions of thanks for any kind of feedback ;-)

Have you succeeded? I tried vs2012 and it passed compilation, but gave the run-time error of _crtisvalidheappointer. But the same code runs well with vs2010. I think Oracle needs to publish the new patch for vs2012

Element link problem in datamodel

Hi,
We created 2 datasets in Datamodel, When we tried to put element level links for both the datasets , its showing error when we generate sample xml.
The error is displayed as shown below:
XML Parsing Error: no element found
Location: http://localhost:9704/xmlpserver/servlet/xdo
Line Number 4, Column 1:
Also in bipublisher.log file, i'm getting this error:
*[2012-03-02T10:54:01.438+05:30] [bi_server1] [WARNING] [] [oracle.xdo] [tid: 38] [userId: <anonymous>] [ecid: 4b1d6eaff3f572e1:6d93021e:135c76b9078:-8000-0000000000015be5,0] [APP: bipublisher#11.1.1] java.sql.SQLException: java.io.IOException: prepare query failed[nQSError: 43113] Message returned from OBIS.[[*
*[nQSError: 27002] Near <=>: Syntax error [nQSError: 26012] .*
the column which 'm trying to link is having same datatype as VARCHAR only.
What should be done for this error? can anyone help in this issue?
Thanks & Regards,
Surya

Thanks for the response Thomas!
The functionality seems to work just fine. I use the LINK PROBLEM and it pops up the problem search box, I search for and select a Problem, I then select it and click ok, and I get no error saying the relationship was not created.
The problem is, when I open the problem after that, there is never any relationship showing in related items there, as it says there should be.
Also, to point out, I am talking about newly created Incidents. I tried even using APPLY prior to doing the LINK PROBLEM but it still did not work. I suspect it may be a workflow problem, where the workflow to create the incident has not completed, there
for the relationship is not completed.... and I get no error.
In my work environment, we have analysts during outages taking a call every 30 seconds, and I need a more efficient way for this system to work. As of now, they spend 1-2 minutes doing the ticket, and that is too long.
I have decided to try a newb way, where I created an Incident (GENERIC OUTAGE) that folks can use, and every 15-30 minutes during an outage, I can open the problem and search for open incidents with that title, and attach all that I find from the problem
side. This is assuming that once attached they will not show up in the search to attach the next time lol. Also this assumes that if attached from the problem, they will auto resolve when the problem is resolved.
I am rusty on my programming, and am currently trying to get refreshed. I am sure that would come in handy for this :)
Oh and lastly, one additional tidbit that will make this clearer, with regard to work flow, we re also running our Service Manager in our help desk, virtualized, as they have not upgraded to Win 7 yet :(. So that compiles my time to add ticket issue :(.

Dynamic Link Problem beim Batchencoden???

Habe seit kurzem folgendes Problem: Exportiere ich mehrere Videos über den Media Encoder, habe ich bei fast der Hälfte der Filme "kaputte Videos" entweder nur an den Effekten oder beim kompletten Video. Rechne ich die Filme einzeln raus, ist alles ok. Das stinkt sehr nach Dynamic Link Problem. Ich kennen das z.T. schon in der Zusammenarbeit mit After Effects. Hier rechne ich meine Projekte erst, bevor ich sie in Premiere reinhole. Aber auf das Batchencoden kann ich nicht verzichten, da ich teilweise 30 und mehr Clips in verschiedenen Formaten rausrechnen muss und das wirklich nicht einzeln erledigen will.
Frage: Hat jemand ne Idee (das Problem existiert erst seit kurzer Zeit), ob da irgendwelche caches vollaufen, kann man dynamic link irgendwie "resetten" oder muß ich das ganze Production Premium Paket CS5.5 neu installieren (wollte ich eigentlci vermeiden!!!!!)?
Ach ja, System Windows 7 64Bit mit CS5.5
Gruß
Stefan

Operator error. Answered my own question. I haven't used Dynamic Link much. It works fine. I was momentarily confusing the import of a PP project vs. a Dynamic Linked Sequence.

Lookout opc or link problems

Similar Messages

Maybe you are looking for