Merge Error occurred while Deliver Baselines to Alternative Target - windows-10

We are having some problems while trying to deliver some files in Clearcase .
3 out of 4 files fail with this error:
Error Messages:
An error occurred during the Deliver operation.
An error occurred while merging file elements in the target view.
Unable to perform merge.
Unable to do integration.
This happens after a windows workstation upgrade from Windows 7 to Windows 10, but we are not sure that it's related . We are using a version 8.0.1 CC client. We tried to update the view but this didn't solve the issue.

You need at least to do a cleartool status in the merge destination view, in the parent folder of those failed files.
Either the status can give you a clue, or there is another OS-related reason, like typically a Windows process keeping an handle on the file which should be modified by the merge, preventing (locking) said modification.
Also, check your environment variable, like CLEARCASE_PRIMARY_GROUP to ensure that was not lost during the workstation OS upgrade.
That would be reflected in the properties of the view:
cd /path/to/view/used/for/merge
cleartool lsview -l -full -pro -cview
We tried to update the view but this didn't solve the issue.
"update" means snapshot view.
Nothing prevent to reset/retry your merge using a brand new dynamic view: that would avoid any OS-lock issue.

Related

SSIS + Excel Vs_needsnewmetadata error

I'm working in a project to load data from sqls erver into an excel file.
When working in my local machine, the package I'm working on is working perfectly.
However when I do a deployment I'm getting the error : failed validation and returned validation status "vs_neednewmetadata"
I'm using SSIS 2012 and Excel 2016
Any help will be appreciated
Thank you
This issues is always very complex to figure out.
Still when you have like this issue try to find if your sources or destinations have changed but not your deployed package. Indeed, when you update your connection tables DB or files please be sure that you deploy again
Also, you have to be carefull when you work with script component do not copy/past this component from others packages otherwise you will get the metadata error and you cannot resolve it.
In my case, the issue I had was related to destination Excel file. I have changed this file like erasing some lines, but I do not change its structure and I missed to copie this one in the server.
That mean event the changes are minor and do not affect the structure of the destination file, you have to update your server version file with the one you use in dev.

"Invalid or nonexistent document" error occurs when opening design element in domino designer

I have a local replica. From domino designer, when I open any design element, I get this error "Invalid or nonexistent document".
But this error didn't occur on server copy. Now you can ask you don't you work directly on server copy. the point is, it's very large db and have serveral xpages and custom control, etc.,. so building the db on remote server copy is painful for me. so work on local copy, save, build, and replicate to server copy.
what I have tried so far.
deleted local replica and created new replica. still error
replaced with my latest template. still error
felt some design elements have corrupted. so replaced both server & local replica with blank template to remove all design elements. and again replaced with latest app template. still error.
ran load fixup on server copy and replicated in local. still error
do anybody have a clue on this issue or any workaround to resolve this?
Thanks in advance for your help.
This may sound strange but I have solved weird things before doing this.
Close Notes and designer. Load Task Manager and make sure all Notes Tasks are ended.
Try to following:
from the notesprogram folder run ncompact -c path\dbname
delete \notesprogram\data\Cache.ndk
delete \notesprogram\data\log.nsf
rename \notesprogram\data\workspace folder to workspace.sav
rename desktop8.ndk *.sav
rename bookmarks.nsf *.sav
Launch notes and designer then test. If it works then great. If not rename everything back. Note, renaming the above will lose your preferences etc.

Puppet agent fails to retrieve catalog until a file is touched

I have a very strange issue with Puppet agent v3.8.6 on Windows (also seen the issue on Linux).
Every time I run 'puppet agent -t' to do a test run I get a Error: "
Could not retrieve catalog from remote server: Error 400 on SERVER: Error: Could not find data item users in any Hiera data file and no default supplied"
Here is the weirdness:
1.) No where in my hiera config or default modules etc am I using the users module it complains about.
2.) To temporarily resolve this issue, all I have to do is touch the module manifest. i.e. touch /etc/puppet/environments/.../modules/users/manifests/init.pp. Then when I re-run the agent it works. It then works 3-4 time after that then fails again.
2a.) turns out I can touch almost any file in my modules directory to temporarily fix the issue.
This seems like some sort of caching issue, but I am now banging my head against a wall to find the root cause of the problem and how to resolve it.
I have already picked through the debug output and removed everything I can from my hiera config. Nothing seems to remove this strange issue.
Has anyone else seen behavior like this? Any hints / clues as to where I should look to solve this?
Some additional config details:
In my current setup I have 1 class that gets applied via a single level hiera hierarchy which does nothing but output some logging.
I have gone through the users module (the one named in the error) with a fine tooth comb but in any case it still complains even when it is not included in ANY config.
I suspect puppet is walking the modules directory (for caching purposes?) and the 'users' module is the first one it hits and the error is not specific to users. I plan to test this by moving the users module out of the modules directory
I haven't got any top level declarations outside of the site manifest. As I say above, the strange thing is that I can touch any file in the modules path and the problem disappears for 3-4 cycles of the agent.
Thanks,
James

ClearCase: Unable to create directory when trying use 'startview' on Linux

I am really stuck in ClearCase startview on Linux. I tried the below:
ct startview <viewtag>
And met an issue like below:
cleartool: Error: Unable to create directory "": error detected by ClearCase subsystem.
I am sure the view is OK, and I can start it in other host. So perhaps my OS met some issue. Is there some good solution?
And I have restarted my Linux system.
If this is about a dynamic view, you can check technote swg21449500 "Create and startview errors: Cannot start dynamic view and Unable to create directory":
Cause
The client or view-server installation is corrupted. The symptoms would typically be seen immediately after applying a Fix Pack of iFix.
Diagnosing the problem
A cleartool -verall showing a mismatch between the MVFS and the other modules is a clear indication of corruption.
Resolving the problem
An uninstall and re-install on the machine will be necessary to resolve the issue.
On Windows, you can see a similar error when a Windows client attempts to start a dynamic view on a Linux or UNIX server running Samba.
See swg21295394.

Jenkins Creating HTML Reports But Link Broken

When using Jenkins, it helpfully auto-generates a colorful report filled with all of your results from testing. The issue I'm having, however, is accessing that report.
I have all of my configuration set up the same as all of my other nodes. (I'm using master-slave configuration on Jenkins, with 4 slave node VMs running Win 7 x64.) When I open up Group 5, however, and open the HTML report page, I pick up the below error.
As always, any help is appreciated.
While I apologize for not being able to share any specifics of the error (configuration, etc. I'm under an NDA for that type of thing), I was able to solve my problem.
If you have everything set up for nodes, and are copying files back and forth between the Master and Slave (there's a plugin that allows you to copy files into the workspace before building instead of using an SCM) just don't have the post-build action of "Publish HTML Reports'" option of "Keep past HTML reports" checked. Otherwise you'll end up with file conflicts and you'll have the same 404 status code that I picked up.

Resources