Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.6K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 395 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
Oracle Client Pro*C Compile Error PCC-F-02104 - Unable to Connect

Hello,
My current environment
Win10 64bit
Visual Studio 2015 with update 3
Oracle 12.2 64bit client with Pro*C
I'm compiling some Pro*C files and get inconsistent results
1st Build: I can compile the VS 2015 successfully and compile all 10 *.pc files.
2nd Build: I'll get the PCC-F-02104 - Unable to Connect even though I just ran build #1 literally 30 seconds ago and everything built O.K.
No files have been modified, so I'm not sure why I can't repeat the same build many times in a row without getting the unable to connect to Oracle even though the DB is up and nothing has changed in the *.pc files
Thanks!
Best Answer
-
If running VS 2015 as admin, try to run as non-admin user to see if the error still occurs
Check Tools->Options->Projects and Solutions->Build and Run then set maximum number of parallel project builds to 1
Answers
-
If running VS 2015 as admin, try to run as non-admin user to see if the error still occurs
Check Tools->Options->Projects and Solutions->Build and Run then set maximum number of parallel project builds to 1