While installing bugzilla,I have got the error message like
Can't use an undefined value as a HASH reference at Bugzilla/Install/DB.pm line 2083
Could anyone please help me out? Below is my cmd prompt(windows 7) running screenshot preview
Reading ./localconfig...
OPTIONAL NOTE: If you want to be able to use the 'difference between two
patches' feature of Bugzilla (which requires the PatchReader Perl module
as well), you should install patchutils from:
http://cyberelk.net/tim/patchutils/
Checking for DBD-mysql (v4.00) ok: found v4.022
Checking for MySQL (v4.1.2) ok: found v5.1.59-community
WARNING: You need to set the max_allowed_packet parameter in your MySQL
configuration to at least 3276750. Currently it is set to 1048576.
You can set this parameter in the [mysqld] section of your MySQL
configuration file.
Removing existing compiled templates...
Precompiling templates...done.
Checking for GraphViz (any) ok
Migrating old chart data into database...
TestProduct:
Can't use an undefined value as a HASH reference at Bugzilla/Install/DB.pm line
2083.
C:\Bugzilla>
Delete the contents of c:\Bugzilla\data\mining - for some reason on Windows it has a problem overwriting those files.
Related
I already installed OpenPBS previously. I wanted try to configure with different command this time and install it.
command :
./configure --prefix=/opt/pbs --enable-alps
and I get this error :
I followed this article previously and it works but with different configuration it shows this error. I want to configure OpenPBS on node(client) and looks like i have to user this command so i tried it. Thanks in advance ^^
Try it without "--enable-alps" in the config file. enable-alps has nothing to do with commands.
This question is independent of the programming language used.
Tested in Windows 7 SP1 and Windows 10 version 1803.
Symptomps
RegSaveKey() fails with an error code 5 (access is denied) if the key to be saved is HKEY_LOCAL_MACHINE.
This error does not occur if a subkey is specified, e.g. HKEY_LOCAL_MACHINE\SYSTEM.
This error also does not occur if the key is HKEY_CURRENT_USER.
First Sample
Here, I use AutoIt to rapidly write a sample code that reproduce the error. I have also compiled the sample code to .EXE to make people easily look at the problem.
Second sample
REG.EXE, which is a built-in Windows tool written using Visual C++ (that's why the tags include C), have exactly the same problem as mentioned above. This is not surprising since according to my investigation, REG.EXE SAVE command actually use the undocumented NtSaveKey(). By the way, RegSaveKey() is internally make a call to NtSaveKey().
REG.EXE SAVE "HKLM" "HKLM.hiv" /Y
The above command fails with an error "Access is denied". Note that I run the command as Administrator.
Question
What is the cause of this error? Is there a way to make RegSaveKey() works for HKEY_LOCAL_MACHINE (without specifying a subkey)?
Update
My further test shows that regedit.exe have the same problem as mentioned above.
Exporting HKEY_LOCAL_MACHINE to a .HIV file fails; however, exporting it to a .REG file succeeds.
Exporting HKEY_LOCAL_MACHINE\<subkey> to a .HIV file succeeds.
Exporting HKEY_CURRENT_USER to a .HIV file succeeds.
Exporting HKEY_CURRENT_USER\<subkey> to a .HIV file succeeds.
All APIs that save a registry key internally call CmSaveKey. In the source code for this function, we see the following block of code at the beginning:
//
// Disallow attempts to "save" the master hive
//
Hive = KeyControlBlock->KeyHive;
if (Hive == &CmpMasterHive->Hive) {
return STATUS_ACCESS_DENIED;
}
HKEY_LOCAL_MACHINE (i.e. "\Registry\Machine") is in the master hive, so CmSaveKey returns STATUS_ACCESS_DENIED (0xc0000022) to the caller. The Windows subsystem translates this status code to ERROR_ACCESS_DENIED (5).
In a software I have to tweak, the man file is located under doc/ along with a simple Makefile.am file:
man_MANS = software.1
EXTRA_DIST = $(man_MANS)
Upon installation, I expect make install to copy the manual under /usr/local/share/man/, but the script - instead - will try to install the man under /usr/local/share/man/man1 - which does not exist - throwing an error and stopping the process.
I would expect a similar behavior if I assigned software.1 to man1_MANS, though.
What is going on ? How is this possible that automake does not create non-existing folders ?
man_MANS will try to figure out in which section to put the manual depending on the extension you gave it, so it is correct in this case that it would install into ${mandir}/man1.
Since you say that MKDIR_P is empty in your output, try to ensure that AC_PROG_MKDIR_P is being called in your configure.ac (it should be automatically called by AM_INIT_AUTOMAKE but since you said it's old it might have some issues).
I recently have built truecrypt source code for windows on Visual 2012. I got 6 files succed, no failed, no skips. But.. there are no output files in "relese" directory which is said there should be in readme file.
ANy idea what's the problem?
edit
Yeah, I am using files from official truecrypt site.
This is message:
6> Generating Code...
6>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppBuild.targets(1137,5): warning MSB8012: TargetPath(C:\Users\Artur\Desktop\tcc\Setup\Debug\Setup.exe) does not match the Linker's OutputFile property value (C:\Users\Artur\Desktop\tcc\Setup\Debug\TrueCryptSetup.exe). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).
6>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppBuild.targets(1139,5): warning MSB8012: TargetName(Setup) does not match the Linker's OutputFile property value (TrueCryptSetup). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile).
6>ComSetup.obj : warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/SAFESEH' specification
6> Setup.vcxproj -> C:\Users\Artur\Desktop\tcc\Setup\Debug\Setup.exe
========== Rebuild All: 6 succeeded, 0 failed, 0 skipped ==========
You are using Debug configuration, your file is C:\Users\Artur\Desktop\tcc\Setup\Debug\Setup.exe
I am facing this error while trying to debug C code in Visual Studio 2010. When searched in google all i could find something related is as below
http://connect.microsoft.com/VisualStudio/feedback/details/615793/badly-formed-debugger-command-causes-error-parameter-basepath-cannot-have-zero-length.
Any suggestions to overcome this is really appreciated . Thanks
Same problem, I was building a function library to load on demand, but got this message. It is a matter of don't quote the VSDebugger options.
Remove the double quotes from
the full path of the executable
the command arguments
the working directory
embedded spaces can be passed to the command line by single quotes, if really required.
I had the same error message with only the name of the executable in the command (so no full path). It used to work pefectly, but suddenly it didn't. I checked the path variable and somehow there were two consecutive ';' in there. I fixed that and the problem disappeared.
In my case the command line did not have .exe extension at the end (Properties->ConfigurationProperties->Debugging->Command). Adding the extension fixed the problem.
For me "Parameter "basePath" cannot have zero length" was caused when I set my configuration properties->debugging->command to "regsvr32.exe $(TargetPath)" to debug my project registration. I fixed this by setting the command to "regsvr32.exe" and command arguments to "$(TargetPath)"
If you set up a makefile project (I guess it's the case), be sure that the file you put in Configuration Properties -> Debugging -> Command exists.
(and I think it doesn't accept batch files, but I'm not 100% sure)
check your path in: Configuration Properties -> Debugging -> Working Directory.
check that this path is a valid path in your machine.
I've solved this problem with setting value of Properties->Debugging->Command to another, and after it set back to my default.
Also make sure Visual Studio is running "As Administrator". This fix it for me.