Your server administrator has limited the number of items you can open simultaneously
Users are getting te following msg: Your server administrator has limited the number of items you can open simultaneously. Try closing messages you have opened or removing attachments and images from unsent messages you are composing and in exchange events I see : MAPI session (user) exceeded the maximum of 250 objects of type "objmessage". I found this https://www-secure.symantec.com/connect/forums/your-server-administrastor-has-limited-number-items-you-can-open-simultaneously but the links are broken and they are saying that there is a fix for 9.0.1. We have version 10.0.4 (clean installation, not upgrade) Any ideas? SarahSolved59KViews0likes3Comments
NBU status: 2074, EMM status: Disk volume is down
Environment: Master Server: Windows Server 2008 R2 Media Server: Windows Server 2008 R2 EMC DataDomain All the backup jobs including catalog backup jobs are running successfully. I tried to cleanup all expired images with bpimage -cleanup –allclients due to increase in size of image catalog and got error. The media server mentioned in the below job details has two storage units, one local drive as basic disk storage unit stu-03 and other one is data domain network drive \\dd670\backup Both storage units are accessible and backup jobs are running fine on them. What could be the cause and possible solutions of this error? Ran bpimage -cleanup –allclients and got the following error from the job details: 1/24/2014 12:49:40 AM - Info nbdelete(pid=7024) deleting expired images. Media Server: enp-en01.xxx.com Media: @aaaaJ 1/24/2014 12:49:40 AM - Error nbdelete(pid=7024) Cannot obtain resources for this job : error [2074] the requested operation was partially successful(1) The job was successfully completed, but some files may have been busy or unaccessible. See the problems report or the client's logs for more details. 1/24/2014 12:49:40 AM - requesting resource @aaaaJ 1/24/2014 12:49:40 AM - Error nbjm(pid=5692) NBU status: 2074, EMM status: Disk volume is down 1/24/2014 12:49:40 AM - Error nbjm(pid=5692) NBU status: 2074, EMM status: Disk volume is downSolved30KViews1like4Comments
VSS timeout issues, restart not suitable solution
Hello I have had continual issues with vss writers time outs on one of our machines we are backing up. Running Windows Server 2008R2 SP1, using BE2010 R3 SP1 The vss writers continue to cause the backup to fail due to timeout. They restart fixes the error status on the writers, but they will time out almost each and every time i run the job. The tech's say i have the job setup correctly, with aofo selected, ms volume shadow copy service(windows 2003 and later) selected and System-use microsoft software shadow copy provider selected. And backup files following junction points. I have selected "Process logical volumes for backup one at a time" too see if this helps. Any suggestions on fixes, besides contanct MS? We don't have support with MS, and as we are suggested to use their system writers by symantec, i would hope that Symantec would provide better aid in fixing VSS issues. Thanks for the help vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2005 Microsoft Corp. Writer name: 'Task Scheduler Writer' Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b} State: [1] Stable Last error: No error Writer name: 'VSS Metadata Store Writer' Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93} State: [1] Stable Last error: No error Writer name: 'Performance Counters Writer' Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381} State: [1] Stable Last error: No error Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {bcedc94e-0c21-4212-8bbf-b65083123138} State: [9] Failed Last error: Timed out Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {fe09e27a-4aef-4e90-bbd3-2308b5d8c6ae} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {e6368e5a-147a-4561-bf1e-d46989773b71} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {47a3c30f-0074-4427-9937-749e88f3e5b0} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {f054ffeb-46ea-4d21-b9b3-b4c040a31214} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {3e2f6dc9-6533-4fad-9658-ece31839d8bf} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {f28b57b4-4222-497d-b54f-e75269db970e} State: [9] Failed Last error: Timed out Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {d50d5687-717b-4535-b70f-bee3ecb3f177} State: [9] Failed Last error: Timed outSolved30KViews2likes9CommentsYour session has expired, please log in again
Dear community, I have a weird issue here. I have just setup a brand new BE 3600 R2 appliance just yesterday. When I am accessing the web UI with IE9 on windows 7, and IE8 on another machine (XP), whenever i click on the "hardware" or "Remote Launch" I will have this error message "Your session has expired, please login again" I do not have any issues at all when I am using Mozilla Firefox. I have added the URL in the trusted sites, clear cache, enable cookies. Nothing worked. Is this a bug? Edit: Tried with compatibility mode too but still no go. BE appliance is patched to latest update. Appliance Summary Model: Backup Exec 3600 R2 Serial Number: S13041019 Software Version: 3.0.419.0 EPS Manufacturer: Symantec30KViews1like3Comments
Ready; No idle devices are available
I'm new to Symantec Backup Exec as I've taken over the duties of someone else that left the company. The problem that I'm having is I can't get Backup Exec to backup anything, not to tape, not to a shared drive, etc.. Logically I would have thought the issue was that the previous employee had used his account for all Symantec functions, I was able to change his account information for all the services and the connection to the server. Everything appears to be fine, I'm able to do a Test Run without any problems but when I go to do a backup I don't receive any alerts I just get a message that says "Ready; No Idle devices are available". Same result no matter where I try to backup to. Anyone seen this before, have any suggestions of how I can fix it? We're using Backup Exec 2012 S1a. Thanks28KViews1like11Commentsunable to log into Netbackup GUI (Status 526)
Hi all i'm having trobule with a box running redhat 5 and netbackup 7.1, i cant connect to the GUI, i get unbale to log in, status 526 From the log, i get the below - Connecting to vnetd service over PBX port = 1556 ServerInterface:Logon:Exception encountered null ServerInterface:Logon - Initial host:null, Current host:valorum, PBX port:1556 Can not connect to the NB-Java authentication service on valorum on port 1556. Exception: vrts.common.server.CantConnectToAuthServViaVNETDException Any ideas what can cause this? ThanksSolved22KViews3likes7Comments
Backup exec management services could not be started
I am facing issue in Backup exec 2014. When i started backup exec console then it first ask for credentials and then gave an error "Backup exec management services could not be started. Backup exec database is offline, turn it online then restart backup exec services" i re install the backup exec 2014 but still have the same issue. Platform consist of Windows server 2008 R2 standard and also it consist of SQL 2008 which is running by client but Backup exec database use its built in database.Solved22KViews1like14Comments
Missing Index Items
I wonder if anyone has a fix for missing index items on EV 10 SP4 archiving email and files,having just one EV server. When I run Verify on the indexes I get a small list of mailboxes and File System that have missing items. The Verify process gets completed with warning and unsuccessful and looking at the subtask and the log file it shows that most tests completed successfully except verifying indexed items with the following errors and reasons: 27/01/2014 14:39:31 Verifying Indexed items SeqNoSSIDAttach IDURLReason 112925201401038775847~201312031642270000~Z~C0F8E132943863E0EA5991CEC595F201N/Ahttp://evaultsrv01.iprod.local/enterprisevault/download.asp?VaultID=173225416F8C73B41ADE8C0254DCDB65F1110000evault&SavesetID=201401038775847~201312031642270000~Z~C0F8E132943863E0EA5991CEC595F201&Request=NativeItemNo index entry for this document No failed indexes comes up and I could not find any articles for this. Thank you ALL.Solved19KViews0likes6CommentsUnable to connect to the selected NetBackup host "masterserver.xxx.com"
Hi All, Windows 2000 (Service Pack 4) X86 Family 6 Model 10 Sepping NBU Master server version 6.5.6 NetBackup console is not opening, giving below error. Unable to connect to the selected NetBackup host "masterserver.xxx.com" 1. Make sure the user "admin" has privileges on the host. 2. Make sure the local host is...... and some more points, can be find in attached screen shot. Below is what I tried..... 1) Restart the services, Console opens...but after some time getting same error. 2) During bpdown, failed to stop some demon. Killed them manually. 3) Not able to stop bpdbm, getting permission issue. 4) Name resolution ok (nslookup, reverse nslookup) 5) Checked in registery, name is defined accurately. 6) Put the entry in HOSTS file. Please assist if anyone has faced such issue earlier. I know that 6.5.6 is EOL, but cant upgrade to 7.x as server is windows2000. But still the things are in progress to upgrade the hardware first then the NBU.Solved19KViews2likes11Commentsbphdb exit status = 6: the backup failed to back up the requested files
Hello, we are getting error on Below RMAN Backup.. please suggest what is the issue with it and what can be done to resolve it..Thanks Master Serve is Windows 2008, Netbackup 7.5 client is Windows Windows 2003 Oracle 10G R1 below is Netbackup error.. 06/08/2014 16:55:46 - connecting 06/08/2014 16:55:49 - Info bpbrm (pid=13560) starting bphdb on client 06/08/2014 16:55:49 - connected; connect time: 0:00:00 06/08/2014 16:55:52 - Info bphdb (pid=5448) Backup started 06/08/2014 16:55:54 - Error bpbrm (pid=13560) from client tmgsdhypprddb: ERR - Script <"C:\Program Files\Veritas\NetBackup\scripts\hot_database_backup_hypp.cmd"> failed with status: <1> 06/08/2014 16:55:56 - Error bpbrm (pid=13560) from client tmgsdhypprddb: ERR - Script <"C:\Program Files\Veritas\NetBackup\scripts\hot_database_backup_hypdb.cmd"> failed with status: <1> 06/08/2014 16:55:56 - Error bpbrm (pid=13560) from client tmgsdhypprddb: ERR - bphdb exit status = 6: the backup failed to back up the requested files 06/08/2014 16:55:59 - Info bphdb (pid=5448) done. status: 6: the backup failed to back up the requested files 06/08/2014 16:55:59 - end writing the backup failed to back up the requested files (6)Solved18KViews1like8Comments
Ready; No idle devices are available
I'm new to Symantec Backup Exec as I've taken over the duties of someone else that left the company. The problem that I'm having is I can't get Backup Exec to backup anything, not to tape, not to a shared drive, etc.. Logically I would have thought the issue was that the previous employee had used his account for all Symantec functions, I was able to change his account information for all the services and the connection to the server. Everything appears to be fine, I'm able to do a Test Run without any problems but when I go to do a backup I don't receive any alerts I just get a message that says "Ready; No Idle devices are available". Same result no matter where I try to backup to. Anyone seen this before, have any suggestions of how I can fix it? We're using Backup Exec 2012 S1a. Thanks