Error C1033 Visual Studio
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings fatal error c1033: cannot open program database '' visual studio 2003 and policies of this site About Us Learn more about Stack Overflow
Fatal Error C1074: 'idb' Is Illegal Extension For Pdb File
the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags please use /fs Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only cannot open program database qt takes a minute: Sign up Compilation fails randomly: “cannot open program database” up vote 31 down vote favorite 9 During a long compilation with Visual Studio 2005 (version 8.0.50727.762), I sometimes get the following error in several files in some project: fatal error C1033: cannot open program database 'v:\temp\apprtctest\win32\release\vc80.pdb' (The file mentioned is either vc80.pdb or vc80.idb in the project's
Visual Studio /fs
temp dir.) The next build of the same project succeeds. There is no other Visual Studio open that might access the same files. This is a serious problem because it makes nightly compilation impossible. c++ visual-studio visual-studio-2005 compiler-errors nightly-build share|improve this question edited May 23 '11 at 21:02 Mateen Ulhaq 6,71483572 asked Sep 24 '08 at 12:15 Lev 2,77651926 Could also be you have your project in Dropbox\Google Drive or similar product. –Viktor Sehr Sep 8 '15 at 15:42 add a comment| 11 Answers 11 active oldest votes up vote 20 down vote accepted It is possible that an antivirus or a similar program is touching the pdb file on write - an antivirus is the most likely suspect in this scenario. I'm afraid that I can only give you some general pointers, based on my past experience in setting nightly builds in our shop. Some of these may sound trivial, but I'm including them for the sake of completion. First and foremost: make sure you start up with a clean slate. That is, force-delete the output
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev cannot update program database centers Retired content Samples We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. C/C++ Building Reference C/C++ Build Errors Compiler Fatal Errors C999 through C1999 Compiler Fatal Errors C999 through C1999 Fatal Error C1033 Fatal Error C1033 Fatal Error C1033 Fatal Error C999 Fatal Error C1001 Fatal Error C1002 Fatal Error C1003 Fatal Error C1004 Fatal http://stackoverflow.com/questions/126751/compilation-fails-randomly-cannot-open-program-database Error C1005 Fatal Error C1007 Fatal Error C1008 Fatal Error C1009 Fatal Error C1010 Fatal Error C1012 Fatal Error C1013 Fatal Error C1014 Fatal Error C1016 Fatal Error C1017 Fatal Error C1018 Fatal Error C1019 Fatal Error C1020 Fatal Error C1021 Fatal Error C1022 Fatal Error C1023 Fatal Error C1026 Fatal Error C1033 Fatal Error C1035 Fatal Error C1037 Fatal Error C1038 Fatal https://msdn.microsoft.com/en-us/library/4ks5fw35.aspx Error C1045 Fatal Error C1046 Fatal Error C1047 Fatal Error C1051 Fatal Error C1053 Fatal Error C1054 Fatal Error C1055 Fatal Error C1057 Fatal Error C1060 Fatal Error C1061 Fatal Error C1064 Fatal Error C1065 Fatal Error C1067 Fatal Error C1068 Fatal Error C1070 Fatal Error C1071 Fatal Error C1073 Fatal Error C1074 Fatal Error C1075 Fatal Error C1076 Fatal Error C1077 Fatal Error C1079 Fatal Error C1080 Fatal Error C1081 Fatal Error C1082 Fatal Error C1083 Fatal Error C1084 Fatal Error C1085 Fatal Error C1086 Fatal Error C1087 Fatal Error C1088 Fatal Error C1089 Fatal Error C1091 Fatal Error C1092 Fatal Error C1093 Fatal Error C1094 Fatal Error C1098 Fatal Error C1099 Fatal Error C1100 Fatal Error C1103 Fatal Error C1104 Fatal Error C1107 Fatal Error C1108 Fatal Error C1109 Fatal Error C1113 Fatal Error C1120 Fatal Error C1121 Fatal Error C1126 Fatal Error C1128 Fatal Error C1189 Fatal Error C1190 Fatal Error C1191 Fatal Error C1192 Fatal Error C1196 Fatal Error C1197 Fatal Error C1201 Fatal Error C1202 Fatal Error C1205 Fatal Error C1206 Fatal Error C1207 Fatal Error C1208 Fatal Error C1209 Fatal E
based>Fixing "fatal error C1033: cannot open program database … vc60.pdb" with make and Visual Studio Fixing "fatal error C1033: cannot open program database … vc60.pdb" with make and Visual Studio By http://www.thinkplexx.com/learn/howto/build-chain/make-based/fixing-fatal-error-c1033-cannot-open-program-database-vc60-pdb-with-make-and-visual-studio neokrates, written on February 24, 2011 howto Join date: 11-30-99Posts:224 View Counter: 966 views Rate it Ad Poll In your own projects, what computer language(s) do you usually use? Java C C++ PHP Ruby Perl Python Scala Scripting language(like Groovy) Shell dialect (like Bash) Other View Results Loading ... Feeds: Both vc60.pch and vc60.pdb may become locked visual studio by Visual Studio, so that Visual Studio cannot write them any more:) Good thing, it seems that this files will be unlocked soon. Here is the logic implemented in GNU Make which allows to retry the compilation if that specific type of error happens. Woks for: ✔ GNU make 3.7x ✔ windows XP Should also work for: ✔ cannot open program most windows and unix versions ✔ older or newer GNU make versions Basically, I can chain commands inside of GNU make. I can execute the second command only if the first has failed or if the first was successful. That gives me an option to do something like: $(COMPILE) || $(VALIDATE_ERROR) && $(WAIT_ON_PDB_ERROR) && \ $(COMPILE_AGAIN) ... etc And in GNU make syntax, it will be something like $(MAKE) -f makecommand.mk --no-print-directory all > error.log || $(MAKE) -f grepcommand.mk --no-print-directory all && $(ECHO) pdb/ pch problem, wll wait for 180 sec and retry && $(SLEEP) 180 && \ $(MAKE) -f makecommand.mk --no-print-directory all > error.log || $(MAKE) -f grepcommand.mk --no-print-directory all && $(ECHO) pdb/ pch problem, wll wait for 180 sec and retry && $(SLEEP) 180 && \ $(MAKE) -f makecommand.mk --no-print-directory all > error.log || $(MAKE) -f grepcommand.mk --no-print-directory all && $(ECHO) pdb/ pch problem, wll wait for 180 sec and retry && $(SLEEP) 180 && \ $(MAKE) -f makecommand.mk --no-print-directory all where: >less grepcommand.mk .PHONY all: grep "vc60\.pch\|vc60\.pd