Can you creat a view in CCRC if stream is locked ?
It seems others can create a view but this one guy is getting an error when trying to create the view:
problems performing ClearCase operation
Problems were encountered while retrieving view synchronization information and data
ClearCase CM server: Error: unable to begin update session: unknown error in view server.
ClearCase CM Server: Error: Additional information may be available in the view log on host "hostname".
ClearCase CM Server: Error: operation "view_ws_begin_load_session" failed: unknown error in view server
Any ideas on how to fix or trouble shoot this?
(CCRC is on Windows XP SP3 laptops)
No the stream isn't locked.
Looking at the views log on the server can tell you more, but typically, you can have error due to access rights (like the primary group incorrectly or not set in the CCRC GUI).
Or there is some kind of server error (the CCRC being the view server for all the web views: the view_server process for that particular view could have an issue)
So check the CCRC server logs for views (see getlog):
cleartool getlog -host CCRC_servername -since yesterday view
Related
I'm facing a strange behavior of SQL Server Agent when executing SSIS packages.
I have a job that includes many steps (mainly SSIS packages). Some steps fail mostly every day even the configuration is the same for all the steps.
I tried to delete/create the job, delete/create the SQL Server Agent Proxy but with no sucess.
I can't find any difference between the steps that fail and the ones that succeed.
This is the error returned by SQL Server Agent :
The package failed to load due to error 0xC0011008 "Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information
SQL Server version : 2014
SSIS version : 2014
EDIT :
In the Event Log I found an Information Message from User Profile Service that says :
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards
Process 5924 (\Device\HarddiskVolume2\Program Files\Microsoft SQL Server\120\DTS\Binn\DTExec.exe) has opened key \REGISTRY\USER\S-X-X-XX-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-XXXX\Control Panel\International
Process 5924 (\Device\HarddiskVolume2\Program Files\Microsoft SQL Server\120\DTS\Binn\DTExec.exe) has opened key \REGISTRY\USER\S-X-X-XX-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-XXXX\Software\Microsoft\Windows\CurrentVersion
The SID corresponds to the Proxy User used to execute the SQL Job steps. And the timestamp corresponds is the same when the error occures in SQL Agent.
I think this is what causes the steps to fail.
Could we prevent Windows unloading this registry ?
The error was indeed caused by the fact that the User Profile Service forces the unloading of the Registry.
The solution that worked for me was to change the policy setting Do not forcefully unload the user registry at user logoff from "Not Configured" to Enabled.
Start the Local Group Policy Editor (gpedit.msc)
Go to Computer Configuration > Administrative Templates > System > User Profiles
Set "Do not forcefully unload the user registry at user logoff" to Enabled
Run gpupdate command.
Details can be found here : https://support.microsoft.com/en-us/help/2287297/a-com-application-may-stop-working-on-windows-server-2008-when-a-user
We are working on a task to resurrect a ClearCase server.
During the restoration process, we are stuck with following error as shown in server log.
vobrpc_server.exe(<pid>): Error: See albd or vob error logs on host <host name>
Here is the background.
We were given 2 servers [Registry & view server]
Registry server was in island and view server was in under a domain, which is now currently unavailable.
We created a new group called "ClearCase" and put both these servers under same LAN and created new users under ClearCase group.
While the license & albd service started successfully, it is still unable to create / restore views.
We were able to see VOB information via ClearCase explorer, but while trying to create a new view & while accessing the folder, we are getting error like "Encountered an improper argument". Google around this error, we ended up in seeing above error in ClearCase server logs.
The actual errors are:
view server log error:
view_server.exe(pid): Warning: Unable to open vob
'<host_name>:E:\ClearCase_Storage_e\vobs\AdmitOneIKE.vbs':
unknown error in VOB.
view_server.exe(7876):
Error: Unexpected error in VOB
"<host_name>:E:\ClearCase_Storage_e\vobs\AdmitOneIKE.vbs"
op vob_ob_get_vob_owner_sid:error detected by ClearCase subsystem
See vobrpc_server_log on host <host_name>...
vobrpc_server.exe(1188):
Error: Problem starting vob_server for vob
<host_name>:E:\ClearCase_Storage_e\vobs\esg.vbs. server
Albd(5364):
Error: Server vob_server.exe (pid=7224) on
"E:\ClearCase_Storage_e\vobs\AdmitOneIKE.vbs"
died on startup; marking it as "down".
vob_server.exe(pid):
Error: No group "clearcase" found.
vob_server.exe(7224):
Error: Unknown style protections.
cccredmgr(6388):
Error: Trouble contacting registry on host "<host_name>":
timed out trying to communicate with ClearCase remote
There seems to be an issue with the owner or the groups associated with the Vob.
I would recommend trying using fix_prot for fixing the vob.
And/or cleartool protectvob to change/reset ownership and group membership.
Error encountered while setting a ClearCase dynamic view.
root#clearcase:~ # ct setview cc_dyn_view
ct: Error: Operation "view_ws_is_ws_view" failed: view storage directory or control files unavailable --
additional information may be present in the view server host's view log.
root#kviewsrvr:~ #
View log shows:-
2013-11-20T11:40:21+05:30 view_server(16910): Error: Operation fcntl(F_SETLK), .pid: Input/output error
2013-11-20T11:40:21+05:30 view_server(16910): Warning: Temporary server starting for unusable view at '/net/clearcase/viewstore/root/cc_dyn_view.vws'
Anyone please help to resolve this issue.
It depends on the ClearCase version, and on the view and vob server (Unix, Solaris, windows).
This thread reports a similar error, sugesting a Linux system limitation:
The size of the file table will need to be increased.
Increase the 'nflocks' kernel parameter from 200 to 400.
If it is not that, you need to check:
the server ClearCase logs (not just the view logs),
any permission issue in accessing /net/clearcase/viewstore/root/cc_dyn_view.vws.
I have a package that I'm using to load records from a CSV file into a table. It has three elements in the control flow:
Truncate table
Load File into Table
Verify that there are records on the table after the load or raise an error
The idea is to have a single transaction on the package, so if the load of elements fails or the file was empty then the transaction is rolled back and the table isn't truncated.
To enable the transaction I just go to the package properties and set TransactionOption=Required, then I just try to execute the package and get this error while trying to execute the first element (The SQL task that tries to truncate the table):
[Execute SQL Task] Error: Failed to acquire connection "Database
Connection". Connection may not be configured correctly or you may not
have the right permissions on this connection.
If I just go back and change the TransactionOption property of the package to the default (Supported) then the package executes correctly but if there's an error there's no rollback.
I am using ADO.NET to connect to a SQL Server DB.
Any idea of what am I doing wrong? Is this the correct way to use transactions or am I missing something?
Thanks!
I know this is an old topic, but I had the same problem as you - the package works fine until I set one of the containers transaction's option to TransactionOption=Required
From what I understand, this might be related to Microsoft Distributed Transaction Coordinator (MSDTC) service not being started on the SQL server.
When I had this issue I checked if MSDTC is started on the machine on which I was running the package - it was. Sadly, I couldn't access the SQL server to check the same thing.
But, following these steps on the machine running the package solved the problem:
On Windows Server 2008 and Windows Vista:
Click Start, click Run, and type dcomcnfg to launch the Component Services Management console.
Click to expand Component Services and click to expand Computers.
Click to expand My Computer, click to expand Distributed Transaction Coordinator, right-click Local DTC, and click Properties.
Click the Security tab of the Local DTC Properties dialog.
In that dialog box, I had to enable "Network DTC Access" and also "Allow Inbound" and "Allow Outbound".
Sources:
msdn forum about this
msdn article about troubleshooting Problems with MSDTC
I am using msdeploy (version 2) to transfer a database from machine A to machine B.
On in the database on machine A there are some users that do not exist on machine B, thus the transfer (partially) fails with the message:
Error Code: ERROR_SQL_EXECUTION_FAILURE
More Information: An error occurred during execution of the database script.
The error occurred between the following lines of the script: "3" and "5".
The verbose log might have more information about the error.
The command started with the following: "CREATE USER [someDomain\someUser] FOR LOGIN [someDomain"
Windows NT user or group 'someDomain\someUser' not found.
Check the name again. http://go.microsoft.com/fwlink/?LinkId=178587
The database seems to be transfered, except for the user creation. Does anyone know what state the database is in after this failure?
Is there any way I can transfer the database without the users (or better without specific users) using msdeploy?
Web Deploy uses SMO (SQL Management Objects) to script out and apply the scripts for SQL databases, and exposes most of the SMO settings with the dbfullsql provider (so, most of these options: http://msdn.microsoft.com/en-us/library/microsoft.sqlserver.management.smo.transfer_properties.aspx). If you want to skip the users due to this kind of login-not-exists or user-not-found error, you should be able to do this by adding the scripting option: copyAllUsers=false to the source of the sync. For example:
msdeploy.exe -verb:sync -source:dbfullsql="Data Source=.\SQLExpress;Initial Catalog=MySourceDb;User Id=localUser;Password=LocalPass",copyAllUsers=false -dest:dbfullsql="Data Source=RemoteSQLServer;Initial Catalog=MyDestDb;User Id=remoteUser;Password=RemotePass"
Incidentally, I am surprised you note the db appears to have been sync'd - I would expect this is not actually the case. If you have the permissions for it, Web Deploy will create the database if it did not already exist when it initially tries to make the connection, but your failure occurred very early in the script execution, and I believe Web Deploy dbfullsql syncs are transacted by default (the db creation is separate from the script execution and is not transacted). Thus the db may exist where it did not pre-sync, but I wouldn't expect the data to be present in it.