Can't open aspx

Can't open aspx file

Unless the aspx file refers to an ActiveX, or newer Java App version than Java engine installed.  Mac OS X is not compatible with ActiveX.  See my FAQ*:
http://www.macmaps.com/browser.html

Similar Messages

  • Can Not Open ASPX Files In Dreamweaver CC ?

    I just upgraded from Dreamweaver CS6 to Dreamweaver CC and now can no longer double click to open ASPX files.
    Is this something that was removed from Dreamweaver CC?
    Or, is there something I need to install or edit in order for it to work again?
    I tried adding it to the Extensions.txt file, but doesn't seem to be working unless I entered it into incorrectly.
    My Extensions.txt File...
    <<
    ASP,ASPX,HTM,HTML,SHTM,SHTML,XHTML,STM,SSI,JS,JSON,APPCACHE,XML,XSL,XSD,DTD,RSS,RDF,LBI,DW T,CONFIG,CSS,SCSS,LESS,SASS,TLD,TXT,PHP,PHP3,PHP4,PHP5,PHP-DIST,PHTML,TPL,INC,SQL,SVG,PRO: All Documents
    ASP,ASPX
    HTM,HTML,HTA,HTC,XHTML:HTML Documents
    SHTM,SHTML,STM,SSI,INC:Server-Side Includes
    JS,JSON:JavaScript Documents
    XML,DTD,XSD,XSL,XSLT,RSS,RDF:XML Files
    LBI:Library Files
    DWT:Template Files
    CSS,SCSS,LESS,SASS:Style Sheets
    APPCACHE:Manifest
    HTACCESS:Directory Configuration File
    TXT:Text Files
    PHP,PHP3,PHP4,PHP5,TPL,PHP-DIST,PHTML:PHP Files
    TLD:Tag Library Descriptor Files
    SQL:SQL Files
    VTM,VTML:VTML Files
    SVG:Scalable Vector Graphics Files
    PRO:Adobe Proto Files
    >>
    Any help or direction would be greatly appreciated.

    You can apply the default file association in windows. Follow http://windows.microsoft.com/en-in/windows-vista/change-which-programs-windows-uses-by-def ault
    Also, you can try adding it in DW preferences.
    1) Go to Preferences < File Types/Editors.
    2) Click on the "+" icon on left Column and add the extension you need.
    3)  Click on the "+" icon on right column and add the Editor as Dreamweaver. Locate the Dreamweaver.exe file installed at "C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC".
    4) Click on Make Primary Button and Click OK.
    5) Close DW and re-launch.
    I hope this helps
    Thanks
    Bhawna Gupta

  • "Open In Excel" button inside the Xlviewer.aspx page return Error and I can not open excel using local office

    Inside the xlviewer.aspx page when I click on "Open In Excel" at first I receive this Error: 
    Some files contain viruses that can be harmful to your computer. it is important to be certain that this file is from a trustworthy sourceDo you want to open this file?
    Then, When I click on Yes, the second error message(below) shows and I can not open Excel using my local Excel Application.
    This action couldn't be performed because office doesn't recognize the command it was given.
    I should notice that the application is published under the HTTPS protocol.
    It is just working with IE 9.0. Neither Chrome nor IE after 9.0.

    Sure. I posted here since I suspect that the lastest upgrade may have a bearing on it.
    What do I need to move it over to Number and Lion?

  • Can't open this website ending with aspx

    I'm unable to open http://forums.uship.com/Default.aspx.
    I thought it was a conflict with Safari and the aspx extension, so I called the site's customer service. The rep said she opened it in Safari, and it loaded fine. When I try, it never finishes loading, doesn't even get started, then finally gives me the +Safari can’t open the page+ message.
    I searched Google and these forums, but didn't find an answer. Did find comments saying aspx can't be opened in Safari, but that's not true because this site opens fine http://www.usairways.com/default.aspx.
    Are you able to open http://forums.uship.com/Default.aspx?

    No that's how I got to the other link.
    Clicking http://forums.uship.com opens (or tries to open) the http://forums.uship.com/Default.aspx page.
    Thanks for trying, though. Maybe someone knowledgable in web design will submit an answer, although from what I saw in other threads, there hasn't been a definitive answer yet.

  • Firefox will not open .aspx files. I can open them with IE. What's up?

    I updated Java, uninstalled and then re-installed Firefox. It will not open .aspx files. Internet explorer opens them just fine. .pdf files open fine also. Don't know?

    How would I change the aspx to pdf? As far as going to the menu/applications, I don't see an aspx in the list? Sorry, but I'm pretty rank in this department. Maybe it is the website and not Firefox, although as stated, IE opens them fine.

  • Sharepoint foundation 2013: office docs can be opened in browser using IE but not in firefox or chrome?

    Hi
    Sharepoint foundation 2013:
    why when we open an excel or word  using chrome and firefox browser it wants to download the file.
    It can be opened in browser using IE but not in firefox or chrome?
    Any issues?
    Thanks

    Hello MGerio,
    Can you check what your Browser File Handling settings are of the web application (of the excel/word files)?
    http://social.technet.microsoft.com/wiki/contents/articles/8073.sharepoint-browser-file-handling-deep-dive.aspx
    - Dennis | Netherlands | Blog |
    Twitter

  • I can't open mail on Hotmail from Firefox. I can from Safari. I can open the Hotmail account page and it is complete w/ my new messages, but when I go to open them I get this messeage..."Please refresh your browser window. When you access your Windows Liv

    I can't open mail on Hotmail from Firefox. I can from Safari. I can open the Hotmail account page and it is complete w/ my new messages, but when I go to open them I get this messeage..."Please refresh your browser window. When you access your Windows Live Hotmail account from more than one computer, we ask you to sign in again to help keep your account private and secure. " when I sign in again there is no change. in English
    == URL of affected sites ==
    http://http://sn135w.snt135.mail.live.com/default.aspx?n=2087215863
    == User Agent ==
    Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_8; en-us) AppleWebKit/531.22.7 (KHTML, like Gecko) Version/4.0.5 Safari/531.22.7

    "Clear the Cache": Firefox > Preferences > Advanced > Network > Offline Storage (Cache): "Clear Now"
    "Remove the Cookies" from sites causing problems: Firefox > Preferences > Privacy > Cookies: "Show Cookies"
    See http://kb.mozillazine.org/Clearing_the_cache and http://kb.mozillazine.org/Cookies

  • Can't open Project 2010 file in Project 2007

    I am trying to open a Project 2010 file in Project 2007, I get an error that asks if I would like to download the converter and I say yes and get a generic product page for Project 2010. I can't locate the file that I need, how do I find it?

    Addressed here:
    http://office.microsoft.com/en-us/project-help/opening-project-mpp-files-from-different-versions-HA001045020.aspx
    You have reached this page because the Project MPP file that you are trying to open was created in a later version of Microsoft Project. Check below to determine if a converter for opening later files is available to you.
    Which Project version are you using?
    Which file version are you trying to open?
    Notes
    Project 2007
    Project 2010
    No converter is available. If you received a Project 2010 file that you want to open using Project 2007, ask the person who sent the file to first save it to the Project 2007 file format.
    Alternately, you can install the free
    trial version of Project 2010, and then view the file, or save it to the Project 2007 file.
    Note Once the trial version of Project 2010 has expired, it can continue to open and view project files, but it won’t be able to save them.
    Project 2003
    Project 2007
    There are two possibilities here.
    If you are using Project 2003 with SP3, project files from Project 2007 can be opened read-only.
    Download Microsoft Office Project 2003 Service Pack 3.
    If you are using Project 2003 without SP3, there is no converter available. Upgrade to Project 2003 with SP3, or ask the person who sent the Project 2007 or later file to save the file first in the Project 2000-2003 file format.
    Project 2003
    Project 2010
    No converter is available. Ask the person who sent the Project 2010 file to save the file first in the Project 2000-2003 file format.
    Project 2000 or Project 2002
    Project 2007 or Project 2010
    No converter is available. Ask the person who sent the Project 2007 or later file to save the file first in the Project 2000-2003 file format.
    Project 98
    Project 2000 and later versions
    No converter is available. Consider upgrading to the latest version of Project, or install the free
    trial version of Project 2010 to try out Project’s enhanced functionality.
    Alternately, ask the person who sent the Project 2000-2003 file to save the file first in the Project 98 file format.
    Note Project 2007 and later versions of Project do not have the ability to save to the Project 98 file format.”

  • Corrupted .docx file. Word 2007. Can't open the document. Tags mismatch. Help?

    The Office Open XML file *.docx cannot be opened because there are problems with the contents.
    Details: The name at the end tag of the element must match the element type in the start tag.
    Location: Part: /word/document.xml, Line: 2, Column: 3487212
    Hmm, I guess I should give some background info and what I've tried so far, right?
    The document is in word 2007, Windows 7. Last night, I was in a hurry, and got a lot of things open. I was opening the document to do a few quick spontaneous revisions, but it was so laggy and I was late for an appointment, so I was feeling panicky
    and frustrated. In hindsight, it probably wasn't the best option to just force shut the PC down cause word stopped responding in the middle of opening the document. Still, while I'm no Sherlock, I knew stopping it while it's in the middle of saving the document
    would bebad, I didn't think stopping it while opening the document (and not really modifying the document at all, at least that was what I thought before), could have drastic consequences! The document's quite
    large, a few hundred words, and about 500 or so pages. It's this really big project I was doing at work, for months now really, and because it's somewhat business confidential in nature, I can't exactly share it freely, or I would've uploaded a copy, sorry.
    Anyway, I woke up this morning and opened it, and the error came up. By the way, the document was saved in a 2TB external hard with a few disk errors in the past, if that helps, even if I'm pretty much sure its not a problem with the hard. The error
    came up... and yeah. I first made a copy, which I've been trying everything on, in case I do end up making things worse. I have no previous versions of it, just a relatively very old backup. Anything less than 80% recovery would set me back weeks with a wage
    cut. The good news is that I was able to open the document in WordPad, managing to recover the first 287 pages (131,543 words), with no errors or data loss, and saved it in a separate file. Apparently, according to information I obtained later, MSWord tends
    to not open at all when it encounters an error, but Wordpad tends to stop reading the rest of the code once it encounters an error. So, naturally, I assumed (so correct me if I'm wrong), that behind a few sentences I might lose due to the error, the rest could
    also be salvageable. I then looked up the problem all over the internet. Read a microsoft article on troubleshooting/recovering corrupted documents (Open & Repair, Draft Mode, Creating Link, Recover text from any file converter, etc). No dice.
    I first saw a similar question on answers.microsoft, and tried to use Tony Jollan's Rebuilder, macros enabled and all. Sadly, no luck.
    I managed to make my first breakthrough when I found out that .docx was just a .zip file, and could be renamed as such, with the document.xml extracted and manually fixed using an XML editor (not that I knew how to do that, but I was desperate and
    willing to learn). So, made another copy, changed extensions, and tried to specifically extract the document.xml. I believe that it is the main body text, right? That is the only thing really necessary for me, since everything I've done so far is entirely
    spartan, with no fancy fonts, formatting, header/footer/notes, media objects, formulas, tables, bullet points, numbered lists, etc. All pure sans-serif text, with some Japanese Kanji thrown in. 500 pages of pure text.
    I then hit a snag, when WinRAR encountered an error on extracting document.xml, stating that "CRC failed in word\document.xml. The file is corrupt". So I tried to fix this using several ZIP repair programs and stuff. Nothing worked. At
    least not so far. Managed to extract an incomplete version of document.xml using WinRAR's 'Keep Broken Files' option when extracting. The extracted
    document.xml came up to 3.31 MB while the original in archive is 7.53 MB. Viewed it in the Windows XML Editor which opened up the text in Internet Explorer, a jumble of text with no line breaks or paragraphs. Still, it actually extracted a few pages less than
    the open-using-Wordpad method tried earlier. So trying to fix the archive again...
    So I decided to give up the manual route for the meantime and focus on readymade solutions. I came across yet another microsoft article, but this one was at least more relevant than the last. It had this auto FixMe thing. I ran it, didn't
    work. Apparently, as I found out later, "This fix will work for one specific tag error where there are equations and graphics in the same paragraph AND Office 2010 SP1 has not been applied."
    Tried several (read: dozens) corrupt Word recovery software, from freeware to pro trials, to varying degrees of effect, although unsuccessful
    in goal. Some failed to read it, saying it was too corrupted for them to handle, the best managed to recover about three-pages-worth less data compared to the Wordpad method. So yeah, anybody with a similar problem, always open it with wordpad first and recover
    what you can. That doesn't mean I'm giving up though.
    So here I am, tearing my hair out in frustration. Whew, I feel like I told you guys my life story. I guess worst case scenario, I report this to my boss, so I personally or from the company, I/we'll hire a team of professionals to deal with it.
    But that's not an ideal scenario. It's gonna be out of my salary either way (the company has a firm policy of 'You reap what you sow'), along with a wage cut for making such an amateurish mistake even with continuous reminders to back it up every two sentences,
    so I'd rather avoid that.
    I'm currently looking to see whether there's a way to recover a previous version of an overwritten document somehow using a third-party software or something. (I didn't have Windows Backup enabled, so no previous version on Windows). So far, no
    autosaved documents on MSWord AutoRecover, even though I have it enabled set to every 3 mins (or maybe I'm just not seeing it since I'm trying to look for it manually?). Or are the temporary files wiped on shutdown? I don't have 'Always save backup copy' option
    enabled on word either.
    So yeah, an auto fix, or a lengthy answer detailing what exactly I should do (from the very very basics), or a link to a site with such info, would be much appreciated. Seriously :D
    Please. Thanks for at least making an effort :)

    When a Word document file is corrupted, then you can try several methods to recover it:
    1. First of all, you can try the recovery function integrated with Microsoft Word, as follows:
    1) On the File menu, click Open.
    2) In the Look in list, click the drive, folder, or Internet location that contains the file that you want to open.
    3) In the folder list, locate and open the folder that contains the file.
    4) Select the file that you want to recover.
    5) Click the arrow next to the Open button, and then click Open and Repair.
    You may find more information about this at:
    http://office.microsoft.com/en-us/word-help/recover-the-text-from-a-damaged-document-HP005189610.aspx (for Word 2003)
    http://support.microsoft.com/kb/893672/en-us (for Word 2007/2010/2013)
    2. If you have multiple corrupt Word documents, then you can use the VBA macro provided in article
    http://support.microsoft.com/kb/893672/en-us so that all the files will be opened in "Open and Repair" option automatically.
    3. There are also free tools from third-parties that can open and read Microsoft Word documents, for example,
    3.1 OpenOffice at http://www.openoffice.org. This is a very famous open source project that is designed to support Office file formats, including Word documents. The software can run under Windows.
    3.2 LibreOffice at http://www.LibreOffice.org. Another free office suite.
    3.3 AbiWord at http://www.abisource.com. This is a cross-platform tool that works under Unix and Windows.
    3.4 Google Drive at https://drive.google.com/ also support to load Word document files.
    Sometimes when Word fails to open your document, these tools may be able to open it successfully. If that is the case, then after the document is opened, you can just save it as a new document which will be error-free.
    4. For docx files, they are actually a group of files compressed in Zip file format. Therefore, sometimes, if the corruption is only caused by the Zip file, then you can use Zip repair tools such as WinRAR at
    http://www.rarlab.com to repair the file, as follows:
    4.1 Assuming the corrupt document is a.docx, then you need to rename it to a.zip
    4.2 Start WinRAR, go to "Tools > Repair Archive" to repair a.zip and generated a fixed file a_fixed.zip.
    4.3 Rename a_fixed.zip back to a_fixed.doc
    4.4 Using Word to open a_fixed.doc.
    There may still be some warnings when opening the fixed file in Word, just let ignore it and Word will try to open and repair the fixed file. If the file can be opened successfully, then you can just save the contents into another error-free file.
    5. If all above methods does not work, then you may try third-party tools such as DataNumen Word Repair at
    http://www.datanumen.com/word-repair/
    I have used it to repair some word documents successfully. It provides a free demo version so that you can try to see if the data you want can be recovered or not.
    Good luck!

  • Office Web Apps 2013 - Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word

    Hello
    I had configured Office Web Apps for SharePoint 2013 which was working fine for about 2 months until this morning.
    The error message I get for WORD, PDF and Excel files is:
    The ULS logs on the WFE give me this:
    WOPI (CheckFile) Proof Data: AccessToken Hash '1572676699' [1054 bytes], URL
    01/08/2014 11:01:58.01*    w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              afk59    Monitorable   
    WOPI                              agxqc    Medium      WOPI Signature verification
    attempt failed with public key 01/08/2014
    11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              agxqc    Medium      WOPI
    Signature verification attempt failed with public key
    01/08/2014 11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              agxqb    Medium      WOPI
    Signature verification attempt failed - no public key    e75ead18-af27-4d44-ba50-b38b408011e8
    01/08/2014 11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              ahdzz    Monitorable    WOPI
    Proof: All WOPI Signature verification attempts failed    e75ead18-af27-4d44-ba50-b38b408011e8
    01/08/2014 11:01:58.01     w3wp.exe (0x1368)                           0x09B4    SharePoint Foundation       
         WOPI                              ag7pj    Unexpected    WOPI
    (CheckFile) - Invalid Proof Signature for file Letterhead Template.docx  url: http://site.contoso.com/_vti_bin/wopi.ashx/files/9c5d0d7077aa43e9a9538c02deb57580?access_token=eyJ0eXAiOiJKV1QiLCJhbGciOi
    The ULS Logs on my Office Web Apps server gives me this:
    Error message from host: Verifying signature failed, host correlation:     d197d187-ef9d-42f6-ae4f-c4b8199c1078
    WOPICheckFile,WACSERVER FileNotFound
    WOPI CheckFile: Catch-All Failure [exception:Microsoft.Office.Web.Common.EnvironmentAdapters.FileUnknownException: WOPI 404
    Any idea what may have caused this issue all of a sudden?
    Thank you.
    Yoshi

    Hi Waqas
    Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.
    Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.
    Issue #3 in the above blog link does not reflect the same error I see on my servers.
    I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
    Problem: You receive a "Sorry, there was a problem and we can't open this document" error when you try to view an Office document in Office Web Apps.
    If you added domains to the Allow List by using the
    New-OfficeWebAppsHost cmdlet, make sure you’re accessing Office Web Apps from a host domain that’s in the Allow List. To view the host domains in the Allow List, on the Office Web Apps Server open the Windows PowerShell prompt as an administrator and run
    the Get-OfficeWebAppsHost cmdlet. To add a domain to the Allow List, use the
    New-OfficeWebAppsHost cmdlet.
    I have not added any domains to the Allow list so this did not help either. Should I add the domain?
    Any further help with this is much appreciated.
    Thanks again.
    Yoshi

  • Can't open SharePoint site in SharePoint Designer 2013 32Bit but can open Office 365.

    Hello.  I am running Windows 8.1 SharePoint Designer 2013 32Bit (15.0.4615.1000).
    I am unable to open any sites from our SharePoint 2013 OnPremise farm. I can however open sites from our Office 365 environment.
    I get the following error.
    "An error occurred accessing your Microsoft SharePoint Foundation site files.  Authors - if authoring against a Web server, please contact the Webmaster for this servers's Web site.  WebMasters - please see the server's application event log
    for more details."
    I have looked in the event log but can't see anything relative.
    I have cleared all caches, uninstalled and reinstalled and followed recommendations in this post.
    http://community.office365.com/en-us/f/154/t/149314.aspx?PageIndex=2
    My colleague with the same setup also has this issue but another doesn't and is able to access the site. I have a Windows 7 Hyper-V VM on my machine and this can open the OnPremise sites.
    I really don't know what else to try short of rebuilding my machine which I would rather not do at the moment.
    Any help would be greatly appreciated.
    Thanks.
    Steev.

    Try changing security token service application pool password if its expired.
    Security token service application pool should be up and running to fix this issue.
    Please check :
    http://social.msdn.microsoft.com/Forums/en-US/7cf7ae15-1f58-402b-a93b-7f6a6d583169/sharepoint-designer-throwing-error-while-open-my-sharepoint-web-applicaiton?forum=sharepointcustomizationprevious
    http://www.fmsinc.com/free/NewTips/Office/frontpage.asp

  • I am getting error when hovering on document in sharepoint online "sorry there was a problem and we can't open this document.If this happens again, try opening the document in Microsoft Word"

     I am getting error when hovering on document in sharepoint online "sorry there was a problem and we can't open this document.If this happens again, try opening the document in Microsoft Word".I am sure that document is not corrupted and
    all. something it showing the preview and sometimes it throwing this error. I hope this error is intermident. When clicking on the link also it throws this error but on refreshing it working fine. I dont know why it is happening. Please helpme  to resolve
    this issue. 

    Hi Waqas
    Thanks for your help with this. I had a look at both posts, the URL works fine from the WAC server and I am not using a System account to test docs.
    Also, this is a production site that is accessible over the Internet, so we are using https therefore the WOPIZone is external-https.
    Issue #3 in the above blog link does not reflect the same error I see on my servers.
    I also had a look at the information in this link: http://technet.microsoft.com/en-us/library/ff431687.aspx#oauth
    Problem: You receive a "Sorry, there was a problem and we can't open this document" error when you try to view an Office document in Office Web Apps.
    If you added domains to the Allow List by using the
    New-OfficeWebAppsHost cmdlet, make sure you’re accessing Office Web Apps from a host domain that’s in the Allow List. To view the host domains in the Allow List, on the Office Web Apps Server open the Windows PowerShell prompt as an administrator and run
    the Get-OfficeWebAppsHost cmdlet. To add a domain to the Allow List, use the
    New-OfficeWebAppsHost cmdlet.
    I have not added any domains to the Allow list so this did not help either. Should I add the domain?
    Any further help with this is much appreciated.
    Thanks again.
    Yoshi

  • How to open aspx. files in OS 10.8?

    is this the right place to ask how to open aspx. files in OS 10.8.2?

    Unfortunately aspx is a generic extender - it is a report generated by a server running Windows .net - it isn't an extender that actually tells what kind of file it is or what kind of data it holds. That's something you either have to know before hand so you can force the proper program to open it (or change the aspx extender to its real extender) or you have to find out what the file is.
    At work our system's report generator gives everything an aspx extender. When I generate a report I decide whether it should be a PDF, Excel file, etc. After downloading the file I change its extender appropriately.

  • Can't open Adobe Reader XI (MSVCP100.dll) - Impossible d'ouvrir Adobe Reader XI (Erreur .dll).

    Hi, i installed adobe reader xi, but i can't open it , i have a message error with this "MSVCP100.dll" and "Acrobat failed to load its Core DLL", i'm in windows 7, tell me what to do to fix this problem, thanks.
    Bonjour, j'ai installé adobe reader xi, mais impossible de l'ouvrir , j'ai un message d'erreur "MSVCP100.dll" qui me vient sur l'écran,  merci de m'aider, cordialement.

    I would suggest that you try reinstalling Adobe Reader; download and run the cleaner tool http://labs.adobe.com/downloads/acrobatcleaner.html then reinstall the latest Reader version from http://get.adobe.com/reader/enterprise/
    This should fix the MSVCP100.dll error.  If it does not, you should manually reinstall the Visual C++ 2010 redistributable
    32-bit Windows: http://www.microsoft.com/en-us/download/details.aspx?id=5555
    64-bit Windows: http://www.microsoft.com/en-us/download/details.aspx?id=14632

  • RMS stopped. Users told "only documents created in a signed application can be opened in a signed application"

    Hi
    I hope you can help and that this is the right forum.
    We have a RMS 1.0 sp1 server which has stopped working.
    Users get "only documents  created in a signed application can be opened in a signed application" when trying to protect a document in word or Outlook, and are unable to open previously protected documents.
    C:\Users\username\Local Settings\Application Data\Microsoft\DRM - only has the one file in it which is DRM-Machine. the .eul .CLC and .Gic files are missing from this folder.
    The server running the rms has an event id 82. " the callers machine certificate has a certificate chain that is not valid"
    I ran an irmcheck on the local machine which showed " No user Certificate"
    I can connect to the rms server urls , both licensing and certificate with no errors and IE shows the zone to be local intranet.
    Can anyone see what my problem might be and suggest why the workstations are not getting their certs and allowed protection? What else should I be checking?
    Best Regards
    Steen

    Hi
    Here is the answer which resolved my situation, I hope it helps yours.
    Guybrush-Threepwood I've marked your post as helpful as we had installed SP2 but it was not installed correctly and installing correctly was part of the solution.
    PROBLEM:
    Client began seeing the error:
    “Only documents created in a signed application can be opened in a signed application”
    On the server we were getting events:
    “The callers machine certificate has a certificate chain that is not valid”
    CAUSE:  
    Servers running RMS before SP2 can no longer get a valid Server Licensor Certificate.
    RESOLUTION:
    1. Install RMS v1 SP2 from:
    http://www.microsoft.com/en-us/download/details.aspx?id=14329
    2. Locate and then click the following key in the registry.
    For the enrollment URL on x86 versions of Windows Server 2003:
    HKEY_LOCAL_MACHINE\Software\Microsoft\DRMS\1.0\
    For the enrollment URL on x64 versions of Windows Server 2003:
    HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\DRMS\1.0\
    3. On the Edit menu, point to New, and then click String value.
    4. Type EnrollmentURL, and then press Enter.
     5. On the Edit menu, click Modify.
     6. Type
    https://activation.drm.microsoft.com/enrollment/enrollservice.asmx, and then click OK.
     7. On the Edit menu, point to New, and then click String value.
    8. Type CloudGicURL, and then press Enter.
     9. On the Edit menu, click Modify.
     10. Type
    https://certification.drm.microsoft.com/certification/certification.asmx, and then click OK.
    11. Go into the RMS Web interface and renew the SLC
    HTH

Maybe you are looking for