Error message "there was a problem communicating with the server"

for about a week or so now, when I connect to my bank website everything is verrrry slow and when I finally get through the log in steps the error message shows on the site. Sometimes I can complete the task at hand, although it takes forever. Other times the screen just stays with the spinning wheel and I end up closing the browser. I've cleared the history and cache. I've made sure to have only one firewall/ virus protection activeated. I've reset Firefox. The pages populate faster now, but still slower than before. Not sure what's going on.

You might try to disable some or all of your extensions/add-ons or plugins such as content blockers etc., restart FF, then selectively re-activate one by one.
This has helped me a few times finding out what makes FF slow.

Similar Messages

After loading lion, I get an error message "There was a problem connecting with the server. URL's with the type "file" are not supported."

After loading Lion, I have been getting an error message "There was a problem connecting to the server. URLs with the type "file:" are not supported." There does not seem to be any actual problem with internet connectivity, but it is persistent and annoying. Any idea of its cause and treatment?

Take a look at this link, https://discussions.apple.com/message/16156214#16156214

Since installing Lion I keep getting the error message 'there was a problem connecting to the server. URLs with the type 'file:" are not supported"' How can I fix this?

since installing Lion I keep getting the error message 'there was a problem connecting to the server. URLs with the type 'file:" are not supported"' How can I fix this?

A Davey1 wrote:
Not a nice answer!
Posting "Check the 'More like this'" area and not simply providing the answer is a great way to make these groups worthless.
You're ignoring context. On the old Apple Discussion Groups I never posted replies like that, instead giving people relatively detailed answers. The new Apple Support Communities made things worse by introducing certain inefficiencies. Then came Lion. The flood of messages that came with Lion required a painful choice for any of the people who had been helping here: (1) Give quality responses to a few questions and ignore the rest. (2) When applicable, give a brief answer such as the one that you found objectionable. (3) Give up all the other normal activities of life and spend full time trying to answer questions here.
People who needed help with Lion problems seemed to have trouble discovering existing message threads that described how to solve their problems. I never posted the suggestion of "Check the 'More like this' area" without verifying that the help that the poster needed could be found there. Even doing that, what I posted saved me time that I could use to help someone else.
The people helping here are all volunteers. None of them is being paid for the time they spend here. They all have a life outside of Apple Support Communities. It's arrogant of you to demand that people helping here spend more time than they already do.

I upgraded to Lion yesterday. Now I keep getting and error message: there was a problem connecting to the server. URLs with type "file:" are not supported. What server?

I upgraded to Lion yesterday. Now I keep getting and error message: there was a problem connecting to the server. URLs with type "file:" are not supported. What server? How do I get rid of this.

Take a look at this link, https://discussions.apple.com/message/16156214#16156214

Since upgrade to Mac OS 10.7.2L , recurring error message: "There was a problem connecting to the server "servername". The server may not exist...etc."

Since upgrade to Mac OS 10.7.2 Lion, on MacBookPro, recurring (every minute or so) error message: "There was a problem connecting to the server "servername". The server may not exist or it is unavailable at this time. Check the server name or IP address, check your network conneection, and then try again." (The server specified is no longer connected or used). The error message must be clicked twice to continue to work on the computer. Time Machine is switched off. No external disks are connected. Keychain entries for "servername" have been removed since the problem arose. Is there any way to prevent this error message?

I am having the same problem; have tried deleting some of the plist files as others suggested but to no avail. Tried turning off time machine - that didn't fix it either. Very dispappointing.

TS4104 I am receiving the following error message: There was a problem connecting to the server "Diane's Time Capsule" - check the server name or IP address, then try again.

I am receiving the following error message: There was a problem connecting to the server "Diane's Time Capsule" - check the server name or IP address, then try again.

This might just be a typical Mountain Lion network glitch..
Reboot the TC.. that is usually enough to fix it.
Otherwise restart the whole network from off.. Reboot items in correct order.
Modem.. TC.. computer. 2min gap.
Tell us if that doesn't fix it.

Since updating to mountain line, error message "There was a problem connecting to the server. URLs with the type "file:" are not supported" keeps popping up

Since updating to Mountain Lion in the last week, an error message keeps popping up. The graphic is the button with 3 stick men holding hands and the message is "There was a problem connecting to the server. URLs with the type "file:" are not supported". Any solutions found?

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

I have my i Pad connected to my computer and I still get error message there was a problem connecting to the server

I was having problems connecting to my app store and safari, any games or anything that required going out to a server. I rebooted my wireless several times it is working and it shows a signal on my iPad so it was suggested I go into settings and do a reset. I have done this and it still is not working. the error message when I try to sign in with an Apple ID is "there was a problem connecting to the server". I even get this when I am connected directly to my computer through Itunes
Any suggestions?

Sounds more like you have a problem with your apple id. For starters go to that page click manage my apple id and singn in. If you can't sign in reset password.
https://appleid.apple.com
if you can sign in there, try to sign in to itunes on your computer.

Recurrent error message "There was a problem connecting to the server"

Keep getting a recurrent error message.
"There was a problem connecting to the server" URLs with the type 'file:' are not supported.
I've heard others with this issue, but does anyone know what is going on or how th o fix it?
Thanks

Make a temporary, backup copy (if you don't already have a backup copy) of the library and try the following:
1 - delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your
User/Home()/Library/ Preferences folder.
2 - delete iPhoto's cache file, Cache.db, that is located in your
User/Home()/Library/Caches/com.apple.iPhoto folder.
Click to view full size
3 - launch iPhoto/iWeb and try again.
NOTE: If you're moved your library from its default location in your Home/Pictures folder you will have to point iPhoto to its new location when you next open iPhoto by holding down the Option key when launching iPhoto. You'll also have to reset the iPhoto's various preferences.

Error message there was a problem connecting to the server URLs with the type "file" are not supported

A message displays frequently on the screen with the above error. Any ideas?

Open the Time Machine pane in System Preferences. If it shows that Time Machine is ON, click the padlock icon in the lower left corner, if necessary, to unlock it. Scroll to the bottom of the list of backup drives and click Add or Remove Backup Disk. Remove all the disks, then add them back. Quit System Preferences. Test.

Repeated error message "There was a problem connecting to the server 10.0.1.2"

Hello - for the past few months I have been plagued with a pop-up error message box noting the above message. I have run the disk utility from within the OS and upon start up but to no avail. The frequency of the error message varies from once after first usage with no repeat to how it is not - every 30 seconds.
Has anyone seen this before and if so how was the matter resolved?
Thx
Matthew

There are many possible causes for this issue, and it may be very hard to resolve without wiping your account clean of everything except documents as a last resort. Please take each of the following steps that you haven't already tried. Back up all data before making any changes.
If you get the alert in the login screen before you log in, stop here and ask for instructions.
Step 1
If you get the alert as soon as you log in, it's probably caused by one of your login items or by software that otherwise loads at startup or login. Ask if you need help identifying it. Known offenders are "1Password" and "Adobe Resource Synchronizer."
Step 2
If there's an icon representing the server in the sidebar of a Finder window, hold down the command key and drag it out.
Step 3
In the Finder, press the key combination command-K or select
          Go ▹ Go to Server...
from the menu bar. In the upper right corner of the window that opens is a Recent Servers popup menu represented by a clock icon. From that menu, select
          Clear Recent Servers…
and confirm. Test.
Step 4
Open the Printers & Scanners pane in System Preferences and delete any network devices you no longer use. If in doubt, delete them all and add back the ones you want.
Step 5
Triple-click anywhere in the line below on this page to select it, then copy the text to the Clipboard by pressing command-C:
~/Library/PDF Services
In the Finder, select
          Go ▹ Go to Folder...
from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return. A folder may open. If it does, move the contents to the Desktop, or to a new folder on the Desktop. Log out and log back in. Test. If there's no change, put the items you moved back where they were and continue.
Step 6
Open the folder
~/Library/Preferences
as in Step 5 and move the file named "loginwindow.plist" items in that folder to the Trash, if it exists (it may not.)
Log out and back in again, and test.
Step 7
Other possible causes are references in the iPhoto, iTunes, or iMovie library pointing to the server, bookmarks in the Preview application, and PDF files created by Adobe Acrobat with embedded scripts.
Try rebuilding the iPhoto library, if applicable.
Step 8
Resources such as images or sounds stored on the server may have been added to various applications. Examples would be pictures added to Contacts and custom sounds added to Mail. The range of possibilites here is practically infinite, so I can't be more specific. You might get a hint by launching the Console application and looking for error messages that appear at the same time as the alerts.
Step 9
Disconnect all wired peripherals except those needed to start up. Start up in safe mode. Test. After testing, restart as usual (not in safe mode) and verify that you still have the problem.
Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Step 10
Triple-click the line below to select it:
/System/Library/CoreServices/Directory Utility.app
Rght-click or control-click the highlighted text and select
          Services ▹ Open
from the contextual menu.* The application Directory Utility will open.
In the Directory Utility window, select the Directory Editor tool in the toolbar. Select Mounts from the Viewing menu in the toolbar, and/Local/Default from the node menu, if not already selected. On the right is a list of names and values. By default, the list is empty. If it's not empty, post a screenshot of the window and stop here.
*If you don't see the contextual menu item, copy the selected text to the Clipboard (command-C). Open a TextEdit window and paste into it (command-V). Select the line you just pasted and continue as above.
Step 11
Open the following file as you did in the last step:
/etc/auto_master
It will open in a TextEdit window. The contents should be exactly this:
# Automounter master map
+auto_master          # Use directory service
/net               -hosts          -nobrowse,hidefromfinder,nosuid
/home               auto_home     -nobrowse,hidefromfinder
/Network/Servers     -fstab
/-               -static
If there are any other lines in the window, post them. Otherwise, close the window.

Safari cannot open the page ~ The error was: "There was a problem communicating with the web proxy server (HTTP)

Help! I was cruzing along just fine and went out tonight only to receive the message above:
Cannot open Page
Safari cannot open the page
The error was: "There was a problem communicating with the web proxy server (HTTP)."
I have had all the Apple iPhone phone. Have never encountered anything like this.
All systems are GO as soon as I log on to wifi.
Can anyone help, please.

I am also fixed. I also loaded Onavo, but that was the other day ... this is what I did with the help of online chat with AT&T ...
I went to:
Settings
Wifi
I selected the network I was working on by hitting the blue arrow located on right side
At the detail page of that network I scolled down to the bottom to find HTTP Proxy boxes
I was on Off and changed it to Auto and it worked!
I was soo jazzed!!
Instructions said if it was already on AUTO, to change it to Manual and make your Port = 80 but I didn't have to do that!
YIPPIE!! I'm a new man!!
Go to settings -----> WI-FI -----> select the network you're using ------> hit the blue arrow located on the right-side of the network name (ie: show details of that network), this takes you to another page.
--------> at the bottom of the page you'll see "HTTP Proxy" boxes (located below the "renew lease" button) ---------------> change the proxy to AUTO. Note: if you're already at AUTO, change it to "Manual" and make your Port = 80.

Lync 2013 Error 31055 ,31059 LS Call Park Service, The database being used by Group Pickup is not the appropriate version and There was a problem communicating with the Group Pickup backend database.

Hello
I have Lync 2013 and 2010 , still i didn't finish my migration completely from 2010 to 2013 .this is coexistence environment that contains both Lync Server 2010 and Lync Server 2013 .
There was no error's in my lync 2013 front end and back end server's and every thing was fine, yesterday I installed windows updated AND CU for my lync 2013 front end and backend server's .
later on after restarting both the front end and the back end server's i start having hundred's of these error's related to "LS Call Park Service".
so any advice for these issue ? and what is the effect for these error .
below is the error I got .
The database being used by Group Pickup is not the appropriate version.
The database is not the correct version:
Connection: Data Source=HQ-LYNC2013-BE.aaaaaaaaaaaaaaaaaaaaaaaaaaa\rtc;Initial Catalog=cpsdyn;Integrated Security=True
Expected... SchemaVersion: 1, SprocVersion: 1, UpgradeVersion: 2
Actual... SchemaVersion: 0, SprocVersion: 0, UpgradeVersion: 0
Cause: The database has not been upgraded.
Resolution:
Upgrade the database to CU1.
==============================================================
There was a problem communicating with the Group Pickup backend database.
There were problems accessing SQL server:
Connection: Data Source=HQ-LYNC2013-BE.aaaaaaaaaaaaaaaaaaaaaaaaaa\rtc;Initial Catalog=cpsdyn;Integrated Security=True
Message: The EXECUTE permission was denied on the object 'DbpGetVersionSchema', database 'cpsdyn', schema 'dbo'.
Error code: -2146232060
Error number: 229
Cause: This may be caused by connectivity issues with the backend database.
Resolution:
Check if SQL backend is running and accepts connections from Group Pickup.
=============================================================================
Kind Regards
MK

Hello
thanks Holger for u r replay .
due to the Microsoft article about the cu :
I run only :
Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose
Note In a coexistence environment that contains both Lync Server 2010 and Lync Server 2013 and in which the Central Management Service is located on a Lync Server 2010 pool, do not run the
Install-CsDatabase -CentralManagementDatabase command. If you later move the Central Management Service to a Lync Server 2013 pool, you have to run the
Install-CsDatabase -CentralManagementDatabase command to apply the changes.
here is what I get on my power shell after i run the command : "WARNING: Warning: Failed to execute batch --"
PS C:\Users\MK> Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn HQ-LYNC2013-BE.MyDomain -Verbose
VERBOSE: Creating new log file
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.xml".
VERBOSE: Install databases required by Lync Server role(s).
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcxds.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.AbsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcab.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsConfigDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsconfig.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsdyn.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.CpsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database cpsdyn.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.ArchivingDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\arc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsLog.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.MonitoringDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsCDR.
VERBOSE: Assigning "BackendStore:BlobStore:LogPath" to F:\CsData
VERBOSE: Assigning "BackendStore:RtcSharedDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ArchivingStore:ArchivingDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:MonitoringDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:QoEMetricsDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ArchivingStore:ArchivingDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:MonitoringDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:QoEMetricsDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ABSStore:AbsDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsConfigDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsDynDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:CpsDynDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "BackendStore:BlobStore:DbPath" to F:\CsData
VERBOSE: Assigning "BackendStore:RtcSharedDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ABSStore:AbsDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsConfigDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsDynDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:CpsDynDatabase:DbPath" to F:\CsData
VERBOSE: Installing "BackendStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcxds.
Checking state for database rtcxds.
State of database rtcxds is DbState_RequiresMinorUpgrade.
Database rtcxds set to mode Restricted.
Dropping all procedures, functions and views from database rtcxds.
Executing RtcDb.sql...
Adding master role...
Setting owner for database rtcxds to sa.
Creating login MyDomain\RTCHSUniversalServices.
Creating user MyDomain\RTCHSUniversalServices.
Creating Schema MyDomain\RTCHSUniversalServices.
Creating login MyDomain\RTCUniversalReadOnlyAdmins.
Creating user MyDomain\RTCUniversalReadOnlyAdmins.
Creating Schema MyDomain\RTCUniversalReadOnlyAdmins.
Creating login MyDomain\RTCUniversalServerAdmins.
Creating user MyDomain\RTCUniversalServerAdmins.
Creating Schema MyDomain\RTCUniversalServerAdmins.
Adding account MyDomain\RTCHSUniversalServices to role ConsumerRole.
Adding account MyDomain\RTCUniversalReadOnlyAdmins to role ConsumerRole.
Adding account MyDomain\RTCHSUniversalServices to role ReplicatorRole.
Adding account MyDomain\RTCHSUniversalServices to role PublisherRole.
Adding account MyDomain\RTCUniversalServerAdmins to role PublisherRole.
Setting database version: Schema Version 15, Sproc Version 13, Update Version 2.
Setting the database rtcxds to multi user mode.
Database rtcxds is set to multi user mode.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RtcSharedDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcshared.
Database created by script "RtcSharedDatabase" already exists and is current.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-BackendStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_01].log"
VERBOSE: Installing "ABSStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.AbsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcab.
Checking state for database rtcab.
State of database rtcab is DbState_RequiresMinorUpgrade.
Database rtcab set to mode Restricted.
Dropping all procedures, functions and views from database rtcab.
Executing RtcAbTypes.sql...
WARNING: Warning: Failed to execute batch --
-- Copyright (c) Microsoft Corporation. All rights reserved.
exec sp_addrole N'ServerRole'.
Executing RtcAbDb.sql...
Setting owner for database rtcab to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Setting database version: Schema Version 62, Sproc Version 42, Update Version 3.
Setting the database rtcab to multi user mode.
Database rtcab is set to multi user mode.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ABSStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_20].log"
VERBOSE: Installing "ApplicationStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsConfigDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsconfig.
Database created by script "RgsConfigDatabase" already exists and is current.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsdyn.
Database created by script "RgsDynDatabase" already exists and is current.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.CpsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database cpsdyn.
Checking state for database cpsdyn.
State of database cpsdyn is DbState_RequiresMinorUpgrade.
Database cpsdyn set to mode Restricted.
Dropping all procedures, functions and views from database cpsdyn.
Executing CpsDyn.sql...
Setting owner for database cpsdyn to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Creating login MyDomain\RTCUniversalReadOnlyAdmins.
Creating user MyDomain\RTCUniversalReadOnlyAdmins.
Creating Schema MyDomain\RTCUniversalReadOnlyAdmins.
Creating login MyDomain\RTCUniversalServerAdmins.
Creating user MyDomain\RTCUniversalServerAdmins.
Creating Schema MyDomain\RTCUniversalServerAdmins.
Adding account MyDomain\RTCComponentUniversalServices to role ReadWriteRole.
Adding account MyDomain\RTCUniversalServerAdmins to role ReadWriteRole.
Adding account MyDomain\RTCUniversalReadOnlyAdmins to role ReadOnlyRole.
Setting database version: Schema Version 1, Sproc Version 1, Update Version 2.
Setting the database cpsdyn to multi user mode.
Database cpsdyn is set to multi user mode.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ApplicationStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_37].log"
VERBOSE: Installing "ArchivingStore" on HQ-LYNC2013-BE.MyDomain\arc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.ArchivingDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\arc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsLog.
Database created by script "ArchivingDatabase" already exists and is current.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ArchivingStore-HQ-LYNC2013-BE.MyDomain_arc-[2014_11_13][14_35_51].log"
VERBOSE: Installing "MonitoringStore" on HQ-LYNC2013-BE.MyDomain\mon, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.MonitoringDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsCDR.
Checking state for database LcsCDR.
Checking state for database LcsCDR.
State of database LcsCDR is DbState_RequiresMinorUpgrade.
WARNING: The database LcsCDR being updated has data file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\DbPath\LcsCDR.mdf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\DbPath\LcsCDR.mdf. Supplied path will be ignored.
WARNING: The database LcsCDR being updated has log file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\LogPath\LcsCDR.ldf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\LogPath\LcsCDR.ldf. Supplied path will be ignored.
Database LcsCDR set to mode Restricted.
Dropping all procedures, functions and views from database LcsCDR.
Executing CdrDb.sql...
Setting owner for database LcsCDR to sa.
Creating login MyDomain\CSAdministrator.
Creating user MyDomain\CSAdministrator.
Creating Schema MyDomain\CSAdministrator.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Adding account MyDomain\RTCComponentUniversalServices to role ReportsReadOnlyRole.
Adding account MyDomain\CSAdministrator to role ReportsReadOnlyRole.
Setting database version: Schema Version 39, Sproc Version 82, Update Version 2.
Setting the database LcsCDR to multi user mode.
Database LcsCDR is set to multi user mode.
SQL Server Agent is running and its start mode was detected as Auto.
Executing CdrJobs.sql...
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.QoEMetricsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database QoEMetrics.
Checking state for database QoEMetrics.
Checking state for database QoEMetrics.
State of database QoEMetrics is DbState_RequiresMinorUpgrade.
WARNING: The database QoEMetrics being updated has data file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\DbPath\QoEMetrics.mdf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\DbPath\QoEMetrics.mdf. Supplied path will be ignored.
WARNING: The database QoEMetrics being updated has log file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\LogPath\QoEMetrics.ldf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\LogPath\QoEMetrics.ldf. Supplied path will be ignored.
Database QoEMetrics set to mode Restricted.
Dropping all procedures, functions and views from database QoEMetrics.
Executing QoEDb.sql...
Setting owner for database QoEMetrics to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Setting database version: Schema Version 62, Sproc Version 90, Update Version 1.
Setting the database QoEMetrics to multi user mode.
Database QoEMetrics is set to multi user mode.
SQL Server Agent is running and its start mode was detected as Auto.
Executing QoEJobs.sql...
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-MonitoringStore-HQ-LYNC2013-BE.MyDomain_mon-[2014_11_13][14_35_51].log"
VERBOSE: No changes were made to the Central Management Store.
VERBOSE: Creating new log file
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.html".
WARNING: "Install-CsDatabase" processing has completed with warnings. "5" warnings were recorded during this run.
WARNING: Detailed results can be found at
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.html".
PS C:\Users\MK>
I hope some one can confirm no issue with what I did ??
Kind Regards
MK

Error : There was a problem communicating with the Group Pickup backend database.

Hi ,
I found this error in Event viewer for Every 2 min on lync server 2013 :
There was a problem communicating with the Group Pickup backend database.
There were problems accessing SQL server:
Connection: Data Source=(local)\rtc;Initial Catalog=cpsdyn;Integrated Security=True
Message: The EXECUTE permission was denied on the object 'DbpGetVersionSchema', database 'cpsdyn', schema 'dbo'.
Error code: -2146232060
Error number: 229
Cause: This may be caused by connectivity issues with the backend database.
Resolution:
Check if SQL backend is running and accepts connections from Group Pickup.
what can i do ?

Hi,
Did you solve the issue with the help of the suggest Anthony provided above?
If the issue persists, please check if you update the latest vesion of Lync Server 2013. If not, please update it, make sure after install the update for all FE Servers,
then make sure to update BE Server as well. Then rerun Step 2 Setup or remove Lync Server Components.
Here is a similar case may help you:
https://social.technet.microsoft.com/Forums/lync/en-US/3b616e51-93ad-430a-aa93-57c2fd19e0f6/call-pickup-db-issue-after-cu1-update-to-lync-2013-enterprise?forum=lyncdeploy
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

There was a problem communicating with the screenshot service, please try again later.

I've used browser lab for months without issues until late last month it keeps showing me this error:
There was a problem communicating with the screenshot service, please try again later.
I have to retry 3-5 times before I can get it to load the page.
I'm accessing browser lab through firefox 13.0.1 Mac OS X 10.7.4

Hi,
We've had some problems with some of the backend systems we use and have had some accounts get into bad states. Can you please try it again until you see the problem, then respond with:
The AdobeID you use to login to BrowserLab with (don't post your password).
The date, time, and timezone of when you saw this error message.
Thanks, that will let us dig into the logs, see what they tell us and look into your issue further.
Mark

Error message "there was a problem communicating with the server"

Similar Messages

Maybe you are looking for