Extensions not working in CC 2014

I have just installed DW CC 2014 which is so far a disaster. I opened a site in the old CC version created and saved a page and then attempted to insert a P7 photo gallery. The P7 extensions are showing up in the old DW CC menu, but will not insert with a click like they normally do.
Then I open the file in the new CC2014 and no extensions show up. So I go to the extension manager and see that all of my extensions are installed in the old version and one (not the one I need). So I attempt to install the extension I need and get the following error message: "The extension your are about to install conflicts with the following extensions. Do you want to remove the follwoing extensions and continue installation: The extension 'PVII Image Gallery Magic 2I installed in the product Dreamweaver CC, Dreamweaver CC 2014
I click yes and you guessed it, here comes he next error message: Failed to parse XML file: 'C\Users\Joe Dempsey\AppData\Roaming\Adobe\DreamweaverCC\en_US\Configuration\objects\insertbar.xml. The extension will not be installed.
If I attempt to remove the extension from old CC I get approximately the same messaage but it tells me it cannot remove it.
I'm not certain what I am missing here, but I have a client who expects his photo gallery in the morning and I am at this point: I cannot use the old program to insert the gallery. I cannot use the new program to insert the gallery. Everything worked fine before the installation.
Does anyone have any ideas on what to do / or alternatively, the DWCC 2014 product manager's personal cell number?
Thanks,
Joe

I also had problems with my extensions.
I followed the following steps.
1. Closed Dreamweaver
2. Updated Extension Manager CC using the Creative Cloud desktop app.
3. Renamed C\Users\Joe Dempsey\AppData\Roaming\Adobe\DreamweaverCC\en_US\Configuration to C\Users\Joe Dempsey\AppData\Roaming\Adobe\DreamweaverCC\en_US\Configuration-backup
4.Deleted and re-installed the extensions using the Extension Manager.
5. Started Dreamweaver.
There may be a more efficient method; the above worked for me.

Similar Messages

Why do my panels not work in CC 2014

I made my own panels in CC but they don't work in CC 2014. I miss them.

It's the latter. Thank you for answering my question.
Op 21 jun. 2014, om 09:42 heeft Trevor Dennis <[email protected]> het volgende geschreven:
Why do my panels not work in CC 2014
created by Trevor Dennis in Photoshop General Discussion - View the full discussion
Are you talking about a custom workspace, or actual panels made with Configurator? If the former, then go Preferences > Sync settings. If the latter, then those Flash panels no longer work in CC 2014. Check out any of the multiple threads about Extensions being greyed out.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at https://forums.adobe.com/message/6481073#6481073
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
To unsubscribe from this thread, please visit the message page at . In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Photoshop General Discussion by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

Perspective Warp not working in Photoshop 2014? Anyone else having this problem?

Perspective Warp not working in Photoshop 2014? Anyone else having this problem?

I cannot use Perspective Warp. | Mylenium's Error Code Database
Mylenium

I would like to create the a swatch, add it to the library and import to the swatch panel. The help pages available relate to earlier versions of Muse, which does not work with the 2014.2 release version that I have. I have created a library folder, imp

I would like to create the a swatch, add it to the library and import to the swatch panel. The help pages available relate to earlier versions of Muse, which does not work with the 2014.2 release version that I have. I have created a library folder, imported the colour swatch as just 4 colours as a mulib file. I drag the four colours on to the muse page in design view but that is as far as I get. Can anyone help? Thanks

I don't know since I don't share anything. You'll have to peruse the help files and check the permissions and ACLs on the Shared folder. According to the permissions on the Shared folder everyone can R&W. If you want those to be inherited by everything dropped into the folder, add an ACL for
everyone allow read, write
Details in the manpage for chmod. The actual steps are left as an exercise.

3rd party extensions not working in 2014.1 -seeming disaster!

When I updated to 2014.1 my 3rd party extensions will not activate in Live view. Yes I am using fluid grid layouts. Does anyone know a quick work around? I could not have imagined this happening!!

Hi Ben, I am using project seven ....
Image Gallery Magic 2
Accordion Panel Magic 3
Horizontal Mega Menu Magic
Previously I was able to create a template with a fluid grid layout, use the extensions to create a menu, etc. and then click on the extension item (in the menu pull down) and make updates from the third party screen. Not having design view, I cannot access the extensions in live view. Regrettably, I have built many sites using these extensions and now it is very cumbersome to edit and create new menu items. The extensions do work fine in sites that are not fluid grid layout, but most of the sites I have created are FGL.

Hyperlinks not working in cc 2014

I'm on CC 2014 and I'm curious if text hyperlinks are still not working. I've read that they didn't in a previous version, but I'm updated and still having trouble. I've tried both internal hyperlinks and hyperlinks to outside URLs. I'm pretty familiar with the process and can get them to work with frames and images, but no luck with text.
Thanks for any help or resources.
All the best,

I also had problems with my extensions.
I followed the following steps.
1. Closed Dreamweaver
2. Updated Extension Manager CC using the Creative Cloud desktop app.
3. Renamed C\Users\Joe Dempsey\AppData\Roaming\Adobe\DreamweaverCC\en_US\Configuration to C\Users\Joe Dempsey\AppData\Roaming\Adobe\DreamweaverCC\en_US\Configuration-backup
4.Deleted and re-installed the extensions using the Extension Manager.
5. Started Dreamweaver.
There may be a more efficient method; the above worked for me.

[SOLVED] Cinnamon 2.2.8: Extensions not working

1. -- Configuring Cinnamon extensions
NOTE! This problem has been solved. See message #13 for details.
The first problem I have is that I'm not able to configure any extensions in the recent Cinnamon 2.2.8 in Arch Linux.
http://s29.postimg.org/v2ierpco7/cinnam … onsbug.png
When clicking Configure button (either one showed in the picture above or the other on bottom of the main window), I get the following terminal output. On this example, I clicked the button twice:
Loading Extensions module
Could not find any instance settings data for this extension - are you sure it is loaded, and supports settings?
Traceback (most recent call last):
File "/usr/lib/cinnamon-settings/bin/ExtensionCore.py", line 475, in <lambda>
item.connect('activate', lambda x: self._configure_extension())
File "/usr/lib/cinnamon-settings/bin/ExtensionCore.py", line 1009, in _configure_extension
settingContainer = XletSettings.XletSetting(uuid, self, self.collection_type)
File "/usr/lib/cinnamon-settings/bin/XletSettings.py", line 53, in __init__
self.build_single()
File "/usr/lib/cinnamon-settings/bin/XletSettings.py", line 145, in build_single
self.current_id = instance_key
UnboundLocalError: local variable 'instance_key' referenced before assignment
Could not find any instance settings data for this extension - are you sure it is loaded, and supports settings?
Traceback (most recent call last):
File "/usr/lib/cinnamon-settings/bin/ExtensionCore.py", line 475, in <lambda>
item.connect('activate', lambda x: self._configure_extension())
File "/usr/lib/cinnamon-settings/bin/ExtensionCore.py", line 1009, in _configure_extension
settingContainer = XletSettings.XletSetting(uuid, self, self.collection_type)
File "/usr/lib/cinnamon-settings/bin/XletSettings.py", line 53, in __init__
self.build_single()
File "/usr/lib/cinnamon-settings/bin/XletSettings.py", line 145, in build_single
self.current_id = instance_key
UnboundLocalError: local variable 'instance_key' referenced before assignment
Traceback (most recent call last):
File "/usr/lib/cinnamon-settings/bin/XletSettings.py", line 71, in on_hide
self.content.hide()
AttributeError: XletSetting instance has no attribute 'content'
My gcc version is:
gcc (GCC) 4.9.0 20140507 (prerelease)
and python version:
Python 3.4.0
I installed a fresh Arch Linux two days ago so there should not be old configurations etc. in the system.
2. -- Missing several Cinnamon modules
NOTE! This problem has been fixed by loqs & clfarron4. It was caused by a missing mintlocale package. Thank you for your attention!
The second problem I have is lack of the following Cinnamon settings in GUI (cinnamon-settings):
- region (Regional Settings)
- Languages
Output when trying to load, for example, region module:
[fincer@fincer-laptop ~]$ cinnamon-settings region
Unknown module region, using cinnamon-control-center
I already checked folders
/usr/lib/cinnamon-settings/modules/
/usr/lib64/cinnamon-settings/modules/
/usr/lib/cinnamon-control-center-1/panels/
/usr/lib64/cinnamon-control-center-1/panels/
I have libregion.so in panels folder but I couldn't find more relevant information related to the problem.
Any help is appreciated. Thank you!
Last edited by Fincer (2014-05-22 20:54:24)

Thanks clfarron4. I voted for the package.
I needed to re-open this topic since it seems that issue number 1 is still alive.
To be more detailed, I can currently access extension configurations via configure button in cinnamon-settings. However, I noticed that I'm not able to actually change any extension settings and thus, these extensions are not working. In my Linux Mint installation (Cinnamon 2.0.6), they are working perfectly fine.
So, I still have GUI access to extension configurations but the settings affect nothing, no matter of my customizations. They simply do not run.
I get this terminal output while running cinnamon-settings and entering to configuration tab:
Opacify plugin:
__init__ took 236.561 ms
Loading Extensions module
Could not find tooltip for key 'opacity' in xlet '[email protected]'
Could not find tooltip for key 'beginTime' in xlet '[email protected]'
Could not find tooltip for key 'beginEffect' in xlet '[email protected]'
Could not find tooltip for key 'endTime' in xlet '[email protected]'
Could not find tooltip for key 'endEffect' in xlet '[email protected]'
Backgrounds plugin:
__init__ took 309.628 ms
Loading Extensions module
Could not find tooltip for key 'path' in xlet 'backgrounds@mohammad-sn'
Could not find tooltip for key 'time' in xlet 'backgrounds@mohammad-sn'
My basic question is: what in Earth could I miss here? I have correct extension files & subfolders in both ./.local/share/cinnamon/extensions and ./.cinnamon/configs/.
Last edited by Fincer (2014-05-22 07:56:53)

Business Catalyst extension not working since upgrade

I have installed the CC 2014.1 upgrade and now can't get my BC extension too work.
I click on Site->Manage Sites->Import Business Catalyst Site to add a BC site to DW and a dialog comes up saying BC is available as an add-on.
That then takes me to the Adobe Add-ons page which says it is already installed. If I go to Windows->Extensions it says there are no extensions available.
If I go to the Business Catalyst window in DW it shows a video link and a button that says 'Get Started' which does nothing.
What has happened?

I've installed the Business Catalyst add-on for Dreamweaver CC and I'm having a similar issue to the initial post above but I'm also receiving the error showing in the first (Dreamweaver) screen grab below. When I view applications through CC App, it shows that the Business Catalyst add-on is installed. Likewise, when I use the Adobe Extension Manager, it also shows the Business Catalyst add-on is installed. I've followed your instructions for cleaning up the Preferences. I've also tried uninstalling and re-installing the Business Catalyst add-on several times. I noticed one of the troubleshooting steps for Business Catalyst add-on states:
a. Check the version of Adobe Extension Manager CC installed on your machine.
b. If the version is not 7.3.3.39 or later, update your Adobe Extension Manager CC using the Creative Cloud app.
I checked my version of Extension Manager and it's only at ver. 7.3.2.39 even though I followed the update procedure through the Creative Cloud app. I've closed all apps and re-started my computer. I've followed all the troubleshooting procedures I can find on the Add-ons website and the forums and I'm stuck.
Dreamweaver screen grab:
Extension Manager screen grab:
My versions:
Dreamweaver CC 2014.1
Extension Manager CC ver. 7.3.2.39
Business Catalyst ver. 1.0.0
Creative Cloud Desktop Manager ver. 1.9.0.465
64 bit Mac OS X (10.10.2)
I appreciate any assistance.

Telephone extensions not working after Openreach u...

My 91 year old mother's phone has not been working for three and a half weeks while lines in her neighbourhood were upgraded to support broadband.
The good news is that an Openreach engineer has now fixed her master socket and one phone in her house is now working.
The bad news is that the handsets on two extension sockets stopped working, when the master socket was fixed.
The Openreach engineer told my mother that the handsets attached to the extensions were old and should not be used and need to be replaced. That may well be true, but I brought one handset home and it works fine plugged into an extension at our own house - we use BT Infinity with one master socket (for the broadband router) and three extension sockets (with ordinary handsets)
The two extension sockets in my mother's house seem to be dead. (If you plug a normal handset into them nothing happens). It looks to me as if it's not the equipment that is the problem, but the sockets, which, as far as I can tell, appear to have been disconnected.
From what I can see, the telephone line comes into an (old) junction box in the house. One (new) line then goes down to the (working) master socket, and another (old) line goes directly from the junction box to the (not working) extension sockets.
My question is: who is responsibile for fixing this mess? I understand that the homeowner is responsible for the equipment and internal telephone wiring in their house, but I don't want to meddle with the wiring and sockets myself. Also, my mother (like many elderly people) has an emergency red button machine (supplied by the local authority) connected to the main phone in her house. Fortunately that now seems to be working, but I don't want to do anything that could affect the red button machine or stop the main phone working again.
We don't necessarily want to replace the system back to exactly what it was before, but my mother would like at least one extra phone in the house. The main phone is in the living room. She is hard of hearing and can't hear the phone ringing when she is in her bedroom. She doesn't like using a handsfree phone - she fiinds it much easier just to lift the handset to get dialling tone, and replace the handset when she has finished - as you could in the good old days! So an extension socket and handset in (or near) the bedroom seems to be the ideal solution, if only we could get the extension sockets working again!
My mother does not want broadband. She just wants her ordinary landline to work and to be able to plug an extra handset into an extension socket.
Can anyone help please?

Hi cwmk,
Welcome to the community and thanks for posting!
Sorry that your Mum's extension sockets were disconnected when the engineer fixed the master socket. Send us over the details and we'll look into this from here.
Click on my username and under the "about me" section you'll see the link to get in touch with us.
Cheers
Robbie
BTCare Community Mod
If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
We are sorry that we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

Polygonal lasso not working in PS 2014 with OS X 10.10

The polygonal lasso is not working when using Photoshop CC 2014 with the new Mac OS X 10.10 Beta. Anyone else notice this problem? It still works fine in regular Photoshop CC.

You are right about taking my chances with the beta. So far it's working pretty well. They've made a lot of cool visual improvements. A lot of other people who are not using the 10.10 beta seem to be having trouble with the polygonal lasso as well so I wonder if it might be an Adobe problem. I have sent in a report to Apple about the issue.

Custom rendering extensions not working in SSRS Report Designer (rsreportdesigner.config)

My custom rendering extension is working in Report Builder (in RSReportServer.config), but not in Report Designer (in RSReportDesigner.config): instead of adding a "TXT" export option, it's just adding a duplicate "CSV" option.
SUMMARY:
Is there a way to get these features working, with Report Designer?
DETAILS:
We are running SSRS (Reporting Services) under SQL Server 2008 R2.
Here's my rendering section:
    <Render>
      <Extension Name="XML" Type="Microsoft.ReportingServices.Rendering.DataRenderer.XmlDataReport,Microsoft.ReportingServices.DataRendering" />
      <Extension Name="CSV" Type="Microsoft.ReportingServices.Rendering.DataRenderer.CsvReport,Microsoft.ReportingServices.DataRendering" />
      
      <Extension Name="TXT" Type="Microsoft.ReportingServices.Rendering.DataRenderer.CsvReport,Microsoft.ReportingServices.DataRendering">
       <OverrideNames>
           <Name Language="en-US">TXT(ASCII,NoColHds)</Name>
       </OverrideNames>
       <Configuration>
          <DeviceInfo>
              <FileExtension>txt</FileExtension>
               <FieldDelimiter>,</FieldDelimiter>
               <Encoding>ASCII</Encoding>
               <NoHeader>true</NoHeader>
           </DeviceInfo>
       </Configuration>
      </Extension>
      <Extension Name="IMAGE" Type="Microsoft.ReportingServices.Rendering.ImageRenderer.ImageRenderer,Microsoft.ReportingServices.ImageRendering" />
      <Extension Name="PDF" Type="Microsoft.ReportingServices.Rendering.ImageRenderer.PDFRenderer,Microsoft.ReportingServices.ImageRendering" />
      <Extension Name="HTML4.0" Type="Microsoft.ReportingServices.Rendering.HtmlRenderer.Html40RenderingExtension,Microsoft.ReportingServices.HtmlRendering" Visible="false" />
      <Extension Name="MHTML" Type="Microsoft.ReportingServices.Rendering.HtmlRenderer.MHtmlRenderingExtension,Microsoft.ReportingServices.HtmlRendering" />
      <Extension Name="RPL" Type="Microsoft.ReportingServices.Rendering.RPLRendering.RPLRenderer,Microsoft.ReportingServices.RPLRendering" Visible="false" />
      <Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering" />
      <Extension Name="WORD" Type="Microsoft.ReportingServices.Rendering.WordRenderer.WordDocumentRenderer,Microsoft.ReportingServices.WordRendering" />
    </Render>
When I add the above "TXT" section to RSReportServer.config, then Report Builder (and production) both show an export option "TXT(ASCII,NoColHds)".
But when I add this "TXT" section to RSReportDesigner.config, and then (in Report Designer / BIDS) attempt to export from a "Preview" of the report, the export drop-down does not show a "CSV" option followed by a "TXT"
option, but instead shows the "CSV" option twice.
This simply limits testing of the export option, to Report Builder... or requires any reports be published from Report Designer before they can be tested with
this export option.
(FYI, why this export option: compliance in our industry requires sending data to government agencies, in text files, with fixed-length columns, and ASCII encoding. Also, we're attempting to give the production of these files to the *users* managing
communication with those agencies... so we're putting them into SSRS.
I worked around the fixed length columns (and no delimiters -- no commas), by writing a version of the report where all string columns are padded, and all columns are concatenated, to form ONE LONG COLUMN... but Reporting Services' CSV export format produces
a Unicode file (UTF-8, which the agency rejected, because it had a leading "ï»¿", or "EF BB BF" in hex), whereas the agency requires an ASCII file.)

Hi Doug_atMidway,
According to your description, you want to enable your custom render extension. Right?
In Reporting Services, if you want to deploy the custom extension, you just need to add the extension into rsreportserver.config file. The
RSReportDesigner.config file stores settings about the rendering extensions available to Report Designer. Since you still use the csv rendering extension in your assembly, we don't need to do any modification in rsreportdesigner.config file. Pleaes
refer to the links below:
Thanks for attempting to help, Simon.
As my question states, I've *already done* both the above: changed (1) rsreportserver.config and (2) rsreportdesigner.config. I added the same code, shown above, to both files. I did that so I could see the new "txt" extension
both (1) when exporting in production and Report Builder, and (2) when exporting in Report Designer's "preview".
The change in (2) is not working: I do not see the "TXT" extension in Report Designer, when I try to export from a preview. Instead, Report Designer shows the CSV extension repeated.
Thanks for the docs. I consulted them (well, I consulted the EQUIVALENT pages, for SQL Server 2008 R2), when creating my block of code above.
Do you see anything to correct, in my code?
Are the features I'm using actually working, with rsreportdesigner.config?
Thanks again,
-- Doug

Wrap not working in Muse 2014

Wrap function not working at all. I have a text box, with text, and a picture picture, with picture. The picture is arranged to the front and all the items are on the same layer, but when I go to the Wrap box everything is greyed out. I've tried multiple boxes and even created a new site to test whether this is an issue with older sites in the 2014 update. Nothing works, there is no combination of boxes that allow me set a Wrap.
Any ideas?
Thanks,
Jen

Zak Williamson (Adobe) wrote:
Hi Jen, I'm frankly not sure what additional instructions to provide. Both mac_heibu and agm 123 have made valiant attempts to describe how to enable text wrap in Muse.
1) Create a text frame and populated it with text.
2) Draw a rectangle.
3) Cut the rectangle.
4) With the Text Tool click and insertion point in the text.
5) Paste
6) Select the rectangle (which is now inline in the text flow).
7) Select the Wrap settings you want via the Wrap panel.
Text wrap capabilities are limited on the Web. Wrap is only available for items pasted within the text flow that will be wrapping around the graphic. Basically the rectangle (or other objects) can be aligned to the left or right in the text frame with the text flowing around only one side of the wrapped object. And only rectangular text wrap is supported.
Thank you Zak, and thank you to mac_heibu and agm 123 for their efforts. While I understand the positive intent of their posts, it is immensely frustrating to be told the same thing over and over without anyone acknowledging the fact that I have clearly stated that I have followed those steps and I STILL get the results I pictured above.
So I will say it for the fifth time, thank for the instructions on the textbook method on how it is suppose to work. Textbook "suppose to" doesn't seem to be the issue. As with other bugs in Muse 2014 (Source San Pro preference problem), I am hoping someone has a workaround beyond the way it is "suppose to work" I need someone who has some trouble shooting suggestions. I've cleared prefs. and reinstalled Muse to no avail. I created a new site to test if it was an issue with files created by older versions of Muse, but brand new site does the same thing.
Thanks,
Jen

Clip name effect not working correctly in 2014/2014.1

I'm referring to these notes from the latest bug fixes here...
Bugs fixed in Premiere Pro 2014.1 Release | Premiere Pro work area
"Clip name effect doesn’t work correctly if Source Track is set to a different track."
"The Clip Name effect does not work when applied to a transparent video track item, with Source Track set to a video clip."
I've just updated Premiere (2014.1) to specifically fix these two bugs. The Clip name effect isn't using the correct file names. It uses something close but not quite e.g. clip 100 shows as 100B which is down the timeline.
The effect is applied to a transparent layer (have also tried it in a black video layer) and the clip name drawn from a different video track (video/PNGs in track 1, transparent video and effect is in track 3). This problem only appears when videos are in the timeline. When used with stills (PNGs) it works fine.
Any idea of a fix or workaround that isn't using some kind of titling filter? I'm looking to automate the shot naming process for a pipeline in creating animation animatics and this would be perfect. If to actually worked properly.
Using Premiere on a Mac Book Pro with 10.9.5.

Anyone from Adobe care to offer some insight as it's something that is reportedly fixed?

Caller display not worked since June 2014

On 26/06/14 I reported a fault (VOL-**********) that the caller display function had stopped working following a thunderstorm in the area. According to the fault status this fault is showing as being corrected and closed on 02/07/14 when in fact the fault still exists. I tested the line using the BT test socket with a new BT2000 phone and this displayed ‘incoming call’ therefore my internal wiring is not part of the problem. I have also dialled the test code *#234# to check if the caller display service is available and confirmed that it is. I then tested the new BT2000 phone on the neighbour’s telephone line and this showed the caller ID for incoming calls, as did my other telephone as well; therefore none of the telephone handsets are at fault. Three times BT have informed me that the fault has been fixed and yet I still have no caller display. Reading through the forums it would appear that other people have encountered similar issues and that the problem is at the exchange, “An Openreach engineer discovered that the RS232 burst transferring the CLI number up the line was too weak and he then went down to the exchange to investigate. He then discovered that the fault lay in the ADSL device which lies between the analogue exchange equipment and the outgoing line”.
I’m surprised to see that BT are taking so long to trace a fault in their system last raised 5/8/2014 (VOL012-**********) and that they haven’t sent an engineer to the property or to the exchange to check the problem.
My patience is wearing thin over this problem with my Caller Display not working as it started in mid June. I’m also becoming less enthusiastic about BT and find it harder to recommend them to others.
My last message from BT, tells me that it should be back to normal on the 8 August. However, it is still not working. Their message that my phone should be back to normal now and if it isn’t report this to BT, is ridiculous. If an engineer had investigated what was causing the fault and found it, then he would have fixed it. However, either an engineer has not investigated the fault or BT is not competent in fixing their own service faults and makes these statements with crossed fingers?

An engineer called yesterday and told me that he had been asked to test the line for a voice fault not a Caller Display fault. However, his testing revealed there is no line fault, CLI signal is strong and he was happy that the new BT2000 phone (bought after the lightning strike) is working properly. (This phone had also been tested on a neighbour’s phone line where it displayed the callers number). He also found that this same BT2000 phone on my line was not displaying the Caller’s number (CLI), but couldn’t offer any reason why.
I conjectured with him that these tests must bring the problem down to a corrupted CLI signal which does not allow the phone to understand the phone number being sent.
When the lightning struck the phone line back in June, it blew the telephone connection in the back of the Sky Box with a flash and bang (telephone cable now removed from the Sky box). It shorted the Openreach Faceplate (now replaced) so that the phones and broadband stopped working and it caused the phone to light up and react as it does when a call comes through.
Now isn’t it possible that the lightning also travelled along the copper wire to the green cabinet just outside the house and damaged something there which is corrupting the CLI signal, but which does not not show up when the voice line is tested? If not, then there must be a problem further back in the infrastructure, possibly in the Exchange, that is causing a corrupted signal to be sent to my phone?
He told me that another team would have to investigate the Caller Display fault as he was instructed to look into a voice issue and as a field engineer he was not able to investigate any problem that might be in the Exchange. I don’t know whether this Exchange Team would be able to investigate a problem in the Cabinet if nothing is found in the Exchange or can that only be done by a field engineer? He told me to contact BT again as he’d done all that he had been instructed to do and they would have to instigate a fault team to further investigate the problem.
When all this is considered we have the basic problem that BT are unable to provide me with a Privacy and Caller Display Service that I have been paying for, because of a fault in their infrastructure. How much longer is it going to take before they correct the problem that’s been going on since June 2014?

JDeveloper and Team System Extension not working

I am using JDeveloper 11g (11.1.1.1) and latest VSTS extension. The Team System extension does not work.
Here are what I have done:
1) Install JDev, JDev team system extension, TFS team explorer.
2) Workspace created in Team Explorer.
3) JDev Versioning control set for Team system. Select workspace, refresh it.
4) Create a new application/project under team explorer workspace. In Application explorer, The application and project showed up with a "X" mark - not in source control.
5) Add the application/project into source control. Succeeded.
6) But - the application and project still show up with "X" mark. Trying to add again, JDev pop up error message: "file already exists in source control". Files still show up in pending changes window.
I am using windows XP SP2 for development.
Any ideas? Please, this is urgent.
Edited by: user8658859 on 2009/9/24 上午 2:55

I am betting you are running 4.3? I just upgraded my GS3 to 4.3 and now I can't get the GMail smart extension to work. Previously, I was able to on the same phone (but running 4.1.2) but couldn't use WatchIt. Now I can use WatchIt, but can't use Gmail. How frustrating!!

Extensions not working in CC 2014

Similar Messages

Maybe you are looking for