Opening Error: Colors could not be properly read

After HD failure, replacement, and HD contents recovery, other iLife applications seem to function correctly, but iWeb (version 1.1.2) opens existing site with some images absent, some incorrect colors, and the following message:
"The following errors occurred while trying to open this document: One or more colors could not be properly read, and may not display correctly on some systems."
This is obviously true, but no further advice is provided.
The website displays correctly as previously published on .Mac, and on a folder restored from the original HD.
Themes display correctly in the chooser, and new pages created from the same theme that does not display correctly in the existing site, display as they should.
I think the problem is with Domain.sites itself, therefore reinstalling iWeb will have no impact (except to replace Domain.sites with a "blank").
Is there a way to use the published sites to recreate a correct Domain.sites file?
PowerBook G4 Mac OS X (10.4.8)

No.
What you can do however is open the original Domain site, highlight the contents of one page and copy it. Close that old Domain site, open the new Domain site - Paste the contents. Repeat until you've found the culprit file(s)

Similar Messages

HELP ME!!!! itunes wont open, error says could not open key......

I attempted to update itunes to the newest upgrade, and the upgrade was unsucceful, and now this error comes up everytime i try to open itunes (it wont open at all). the error says
Could not open key:
HKEYLOCALMACHINE\Software\Classes\.wav\OpenWithList\iTunes.exe.
Verify that you have sufficent access to that key, or contact your support personnel.
This makes no sense since this is on my home PC

hmmm. okay, if you're currently just getting the "itunes has encountered an error ..." let's try the following technique.
preliminaries
download and save a fresh copy of the itunes 6.0.1.3 installer to your hard drive. (eventually we're going to run the install from there rather than online.)
iTunes 6.0.1.3 Installer
switch off any antivirus and antispyware applications prior to any uninstalls, installs or repair installs.
uninstall
use the complete uninstall instructions given in the following document to remove your existing itunes and quicktime:
Troubleshooting iTunes, iPod Software, and QuickTime installation on Windows
... and if you run into problems on the uninstall, try using the Installer Cleanup utility:
Description of the Windows Installer CleanUp Utility
reboot after uninstalling.
reinstall
remember to switch off your antivirus and antispyware.
reinstall itunes using the 6.0.1.3 installer you downloaded previously.
if you get the "itunes has encountered a problem ..." error message again after that install, first check to see if your Quicktime will launch. if you get an error message when you try to launch quicktime, try using the following technique:
iTunes 6 for Windows unexpectedly quits when opened
keep us posted on your progress.
love, b

SubVI does not open (error 3 could not open front panel)

For the VI I am working in (trail version of Labview 2011), I have created a subVI. At one time I opened this subVI to adjust the connection terminals -which I have done before- and after saving the file and closing it, the subVI remained unadjusted. In fact, I am not able to open the subVI anymore. And when I want to open the file as a VI (e.g. executing the VI in windows), I receive 'load error code 3: could not open front panel.'
I also cannot preform any tasks such as saving the main program for an older version, because this subVI is present in the program.
Nevertheless, the VI still works as a subVI in the mainprogram I've written -in the way it worked before I adjusted the connection terminals.
Is there any way to resolve my problem, without rewriting the whole subVI? The subVI concerning is attached in this post.
Thank in advance,
ps. after closing Labview, it sends an internal warning report.
Solved!
Go to Solution.
Attachments:
ampweightcenter.vi ‏25 KB

Hello Stag,
My name is David and I am an Applications Engineer at National Instruments UK.
To clarify the problem, when you receive this error are you trying to run the VI as an executable, standalone file in Windows? If this is the case then I think that I know what the problem could be. When using the Application Builder the Front Panels of SubVI's are removed to reduce file size. It is possible to include them so that they may open and the steps to doing so are listed in the attached link:
http://digital.ni.com/public.nsf/allkb/8F68715444302CAB86256DDD0071C140?OpenDocument
This link explains why you are receiving this error and how to overcome it.
I hope that this helps you and do not hesitate to contact me if you require more assistance.
Regards
David B
Applications Engineer
National Instruments UK

Premier elements won't open:"error 4960:could not load the disk image"*

the download completed but on clicking the .dmg file the error 4960 was displayed as written above. what is the next step?

Which version of Premier Elements are we downloading?
Create a new Admin account and login to the new account. If you are downloading version 10 from www.adobe.com. Redownlaod it.

VSTS loadtest error while running Loadtest with Runsettings as No of test iterations , ERROR is : could not read result repository: unknown transaction id in results:

Subject: VSTS loadtest error while running Loadtest with Runsettings as No of test iterations , ERROR is : could not read result repository: unknown transaction
id in results:
Hello All,
I am facing the following error while running a loadtest (when i choose the scenario to be executed for No of test iterations). But the same loadtest with the Run duration for X minutes is running fine without any issues.
Any suggestions on the issue i am facing
error is :
could not read result repository: unknown transaction id in results:
or
could not read result repository: unknown request id in results:
Thanks
Satish

Hi Kotapati,
>>Subject: VSTS loadtest error while running Loadtest with Runsettings as No of test iterations , ERROR is : could not read result repository: unknown transaction
id in results:
According to your description, you mean that when you run your load test using the Test Iterations way and then get the error message, am I right?
If yes, please you try to close the VS, and then open this VS again. Then clean your load test project/solution and then re-build it, run your load test again check this issue again.
In addition, I suggest you could try to create a new load test and then run it using Test Iterations way check if you get the issue for the specified load test or all load tests.
If possible, I suggest you could share me simple load test for us so that we will further help you.
You could upload your load test to OneDrive and then copy link here.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Saving a Photoshop CC project from a Mac (in .PSD format) to a thumb drive and trying to transfer it to a Dell laptop with Photoshop CS6. Will not open...Error message: could not complete your request because it is not a valid photoshop document.

Saving a Photoshop CC project from a Mac (in .PSD format) to a thumb drive and trying to transfer it to a Dell laptop with Photoshop CS6. Will not open...Error message: could not complete your request because it is not a valid photoshop document.

The file was corrupted somewhere along the way (assuming it was still readable on the Macintosh).
The platforms don't matter, but you still need file transfer that doesn't corrupt files...

Named Pipes provider, error:40 could not open a connection to sql server. Only happens on one of the front end SRS servers

when testing a datasource connection I get the following error.
Named Pipes provider, error:40 could not open a connection to sql server.
I've read all the posts on this and nothing works. This is a scale out deployment and the connection
works from the other server I have setup with SRS that is connected to the same backend SRS databases. It just doesn't work from one of the SRS front ends. I'm at a loss.. please help

Enable both named pipe and TCP communications.
Make sure client is using the same (named) pipe name as server for connection.
Kalman Toth Database & OLAP Architect
Free T-SQL Scripts
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

I've been getting an error message lately that says "Web Sync could not initialize properly". What do I do?

I've been getting an error message lately which states the following:
Web Sync could not initialize properly. Check that Polar Daemon is running and start Web Sync again. To restart Polar Daemon you need to run 2 commands in Terminal Start Applications>Utilities>Terminal. To stop Polar Daemon which is already running, write a command”sudo launchctl unload/library/launch daemon/fi.polar.polard.plist.” and press enter. Enter your password when required. If Polar Daemon is not running, “error unloading” message appears. Ignore this error message. Write “sudo launchclt load/library/launch daemons/fi.polar.polard. plist” and press enter to run Polar Daemon.
Is this something I should be concerned about, and if so, what do I do about it?
Thanks

That error message comes from third-party software that you installed. If it isn't working, either remove it according to the developer's instructions, reinstall it, or refer to the developer for support. Back up all data before making any changes.

Reporting Services 2008 R2 configuration error: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

Hi, I am using SQL Server 2008 R2 and on one of our dev boxes I am trying to setup ReportServer using ReportingServices Configuration manager. This is was installed longtime back and during installation they created a service account for reporting services.
When I try to configure the service account I do not get the service account created during the installation in the pull down and if I were to use something different I get this "Named Pipes Provider, error: 40 - Could not open a connection to SQL Server"
error.
Thanks in advance...........
Ione

Hi,
Take a look at this blog - http://blogs.msdn.com/b/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx
I hope it will help.

Error message: "Could not open key..." trying to install iTunes 7.6.1.9

I'm trying to install iTunes and keep receiving error msg: "Could not open key: HKEYLOCALMACHINES\Software\Classes\.cdda\OpenWithProgIds. Verify that you have sufficient access to that key, or contact your support personnel."
I have tried to un-install and re-install to no avail. Please help! I have i-Tune gift cards that are rendendered worthless at this point.

Are you logged on as a Windows administrator?

Re: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

Hi,
I'm encountering an issue with "Named Pipes Provider, error: 40 windows" and am having problems determining how to fix it due to the environment I'm using. I have two SQL Servers installed on two separate Win2K3 Server boxes, one is SQL Server 2000 and the other is SQL Server 2005. The SQL Server 2000 contains the actual application data. The 2005 database is used only for Reporting Services. I've set up the reports on SSRS such that their datasources hit the 2000 server. This is using SQL Server authentication.
When testing the reports via SSRS (in Visual Studio 2005), the connection to the data works and the reports are generated fine. When I deploy them to the reporting server and launch IE to test locally (still on the 2005 box), I get this "Named Pipes Provider, error 40" issue. I made sure that Named Pipes and TCP were enabled and the port set at 1433 (to match that on the 2000 box).
Now I changed the datasource's authentication from SQL Server to Windows authentication. I tested this in SSRS and this works too. When I redeployed the reports with this authentication change, testing the reports via IE locally (on the 2005 box) worked. Great. Now when I open IE on an external box, i.e. on the 2000 box, and try to test the reports, I get this same error 40 issue. I've been through a few threads describing the error 40, fiddling around with the SQL Server configuration as well as SSRS, to no avail. I have a feeling this error 40 issue has to due with permissions/authentication between the SQL Server boxes but I can't really be sure. Anyone have any ideas on how to troubleshoot my situation. Thanks.
larry

Named Pipes Provider, error: 40 - Could not open a connection to SQL Server :
I. Incorrect connection string, such as using SqlExpress.
Check out: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=558456&SiteID=17
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1245564&SiteID=1
The typical error when dealing with Express includes:
a. User is not aware of SqlExpress was installed as a named instance, consequently, in his/her connection string, he/she only specify ".","localhost" etc instead of ".\SqlExpress" or "<machinename>\Sqlexpress".
b. Np was disabld by default after installing SqlExpress.
c. If Sqlexpress was installed on the remote box, you need to enable remote connection for Express.
Please read the following blog for best practice of connecting to SqlExpress.
http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx
II. Named Pipes(NP) was not enabled on the SQL instance.
Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=136253&SiteID=1
Oppose to SQL 2000 which turn on all protocols, SQL 2005 SKUs turn off NP by default. So, when you see this error, please check:
1) Go to SQL Server Configuration Manager, See Server has NP enabled.
2) %windir%\program files\microsoft sql server\mssql.1\mssql\log, notepad ERRORLOG, see whether Server is listening on NP. You should see "Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ] or [\\.\pipe\mssql$<InstanceName>\sql\query]"
3) Notice that "sql\query" is the default pipe name, so you need to know server is listening on which pipe name. eg: if you specify server pipe name is "sql\query1", then you would see in the errorlog that server listening on [ \\.\pipe\sql\query1 ], and go to SQL Server Configuration Manager, click client Named Pipe properties, see whether the pipe name is same with the one server listening on.
4) If you are using SQL Native Client ODBC/OLEDB provider({SQL Native Client} or SQLNCLI), go to SQL Configuration Manager, click client protocols, make sure NP and TCP are both enabled. Right click properties of NP, make sure client is using the same pipe name as server for connection.
5) If you are using MDAC ODBC/OLEDB({SQL Server} or SQLOLEDB) provider, in command line, launch "cliconfg.exe" and make sure NP enabled and right pipe name specified.
III. Remote connection was not enabled.
Check out: when you right click on the Server in SQL Server Management Studio, in Connections, the Remote server connections part, you have enabled the "Allow remote connections to this server" check box
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=322792&SiteID=1
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=763875&SiteID=1
If you are making a remote connection, namely, your target SQL Server is on the different box as client application, you might need to check whether:
a. "File and Printer Sharing" was opened in Firewall exception list.
b. Please see the blog for enabling remote connection for express and troubleshooting tips of remote connection.
http://blogs.msdn.com/sql_protocols/archive/2005/11/14/492616.aspx
http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
IV. Server not started, or point to not a real server in your connection string.
Check out: Open SQL Server Surface Area Configuration and ensure all the required services are started, Remote Connections are configured.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=348662&SiteID=1
a. use "sc query mssqlserver" for default instance or "sc query mssql$<instancename>" to make sure SQL Server was started. Sometimes, reseason behind the broken of your client application w/ this error:40 might be SQL server restarted and failed, so, it'd better for you to double check.
b. User specified wrong server in their connection string, as described in the forum discussion, "MSSQLSERVER" is an invalid instance name. Remember, when you connect to default instance, <machinename> could be best representitive for the instance, when you connect to a named instance such as sqlexpress, you should specify <machinename>\<instancename> as data source in your connection string.
V. Other reasons such as incorrect security context.
Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=192622&SiteID=1
Such error also occured during user operation such as moving database or db mirroring or cluster, any DB OP that might invovle different sql instances, namely, the destination database is located in another sql instance and user is not aware of the state of the destination. I recommend you first isolate whether this fail is during connection stage or data operation stage.
a. During data operation, you are normally asked to type in the destination server name whether it is default to "(local)" or another server "<remotemachinename>". So, remember the exact string that represent the target instance, then when the error repros, open command line, use "sqlcmd -S<representitive> -E" ,see what happens, if the connection fail, please follow up above I - IV troubleshooting lists. otherwise continue.
b. If you can make basic conection, but still face the error, then there must be something that server reject the connection or client close the connection for some reason.
VI. Please try basic connectivity tests between the two mahcines you are working on. One simple way to verifty connectivity is to use command line tools, such as osql.exe. For example, osql -E -Stcpervername\instancename. If it connects cross-machine successfully, please also verify that your connection string in your scenario is correct.
Here are some blogs which could be helpful: just follow the basic connectivity troubleshooting guidelines on the SQL Protocols blog, see:
SQL Server 2005 Connectivity Issue Troubleshoot - Part I
http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx
and
SQL Server 2005 Connectivity Issue Troubleshoot - Part II
http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx
Hope this helps.

Error 40 , could not open a sql connection

I have recently bought Kaspersky Internet Security 2014. Before the installation of Kaspersky, SqlServer 2008 R2 express edition was working without any error. But after it's installation I got error saying:
" A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)".
Please help me to get out of this. I have checked all the ports, TCP/IP enabled, SqlServer borwser services.

Ya, Kaspersky was not the problem. I was connecting to wrong instance. Before, i used to connect with
"Data Source=MANCHANA123\SQLEXPRESS;Initial Catalog=Musicworld;Integrated Security=True".
And it was working fine.
Currently, it is not working with same command, I need to make change like this..
Data Source=MANCHANA123\\SQLEXPRESS;Initial Catalog=Musicworld;Integrated Security=True
Use of "\\" instead of "\" .AND now i have no problem here.
Thank you so much Shanky_621 for answering me..

Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

This was originally posted in the SSIS Forum, but a member of the IS team suggested it be moved here. "Most recently I got this error (Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) so does this mean that SQL Server is still trying to use named pipes even if I only have TCP/IP enabled in SQL Server Configuration Manager?"
I'm having the same issue, and here's our scenario:
Installed SQL Server 2005 Developer Edition on a machine with WinXP SP2 and enabled remote connections over TCP/IP
Installed SQL Server 2005 Standard Edition on a machine with Win2003 SP1 (remote connections over TCP/IP enabled by default)
Attempted to 'Copy Database' from Developer Edition TO Standard Edition using 'Detach and Attach' method and recieved the error on the Win2003 machine: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
Attempted to 'Copy Database' from Developer Edition TO Standard Edition using 'SQL Management Objects' method and recieved the error on the Win2003 machine: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
Reinstalled Standard Edition on the Win2003 SP1 machine
Checked all the settings on both machines several times, restarted services etc., and read every post I could find referencing the error.
Same error
Lost my last hair
Thanks in advance,
Steve

Nan,
Before I get on with this post - thank you for your reply.
The XPSP2 machine actually had the firewall disabled, and I verified that it could accept connections on the the associated ports with the Shields Up utility. I tested this on both machines.
I can connect to the server from the XPSP2 machine, Import / Export, manage, view logs, and do everything EXCEPT get the Copy Database package to run. SQL Server Agent always fails on the last step with the following error:
Event Type: Error
Event Source: SQLISPackage
Event Category: None
Event ID: 12550
Date:  1/10/2006
Time:  1:34:15 PM
User:  NT AUTHORITY\SYSTEM
Computer: 401SERVER
Description:
Event Name: OnError
Message: Failed to connect to server BETHESDA.
StackTrace:    at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
   at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.OpenConnection(Server& server, ServerProperty serverProp)
InnerException-->An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
StackTrace:    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnect(WindowsIdentity impersonatedIdentity)
   at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
Operator: NT AUTHORITY\SYSTEM
Source Name: BETHESDA_401SERVER_Transfer Objects Task
Source ID: {86F355AD-3B74-4D7B-8D2D-C743C790A269}
Execution ID: {91B7C32C-C439-4EDB-8A0F-9F8BF207BC06}
Start Time: 1/10/2006 1:34:15 PM
End Time: 1/10/2006 1:34:15 PM
Data Code: 0
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Have you (or anyone else) successfully executed a Copy Databse task?
Steve

Error 1402.could not open key:UNKNOWN\MPAPI.WAPCON...

im getting this error message when i install pc suite v6.82 on windows XP. any ideas
error 1402.could not open key:UNKNOWN\MPAPI.WAPCONNServerMP.4\CLSID. Verify that you have sufficient access to that key, or contact support personel....
thanks in adv..

It sounds that there is some permission problems in your register.
Anyway, if you ignore that error message, does installation continue?

Cannot open pfd files error 1606 could not access network location %APPDATA%/

Error 1606 could not access network location %APPDATA%/
I have adobe reader 8.1.3 installed and cannot uninstall it as i get the same error message as when i try to open files or download the new version. When I type %appdata% into run nothing comes up. I have been through lots of other threads and cannot find a solution so ive made my own please help!

You can download the Windows Installer Cleanup Utility from here http://support.microsoft.com/kb/290301/ - run the downloaded installer, then start the
program from Start | Programs | Windows Install Clean Up. Select Adobe Reader, then click 'Remove'.
N.B. I've heard that this program can cause problems if Office 2007 is installed; don't use it if you have Office 2007!
The above tool helps you to uninstall Adobe Reader, but it will not fix the basic problem with the corrupt %APPDATA% environment variable. You can try to fix it with http://fixitcenter.support.microsoft.com/
P.S. this software is still beta; I strongly recommend to make a System Restore Point before proceeding. Let us know if you need any help with this (and please state your Windows version if you do).

Opening Error: Colors could not be properly read

Similar Messages

Maybe you are looking for