Exchange 2007 OWA sends attachments Outlook connector clients cannot send attachments.

Exchange Server 2007 SP1 + Rollup ***Problem with sending email attachments from Outlook 2007***
* Inbound mail arrives in OWA and Outlook normally with and without attachments.
* OWA email to external email account with attachment goes thru successfully.
* Outlook 2007 sends to an external email address with attachments the message does not arrive at the external mailbox.   The messages leave Outbox but are never delivered. The messages appear in Sent Items also.
* Outlook sends non attachment emails to external addresses successfully.
* Outlook sends email attachments to local domain accounts fine.
#1 Exchange Server on Server 2013 fully patched problem commences. Exchange Server on version less than first RTM release of Exchange 2007.
#2 Outlook profiles were changed to see if that is the problem.
#3 Upgraded Exchange to SP1 and Rollup 10(Rollup was autodownloaded by MSUpdate)
#4 Ran EXBPA nothing of any interest in the report.
--Unified Messaging not configed (Done nothing)
--SenderID (Re-enabled) I had shut all of the antispam to eliminate these.
-- Junk Store threshold not configed (No change)
Any suggestions to get Outlook clients capable of sending attachments configured.
Thx,
-Scot

Hi Scot,
Providing some information on Poison Queue:
The poison message queue is a special queue that's used to isolate messages that are determined to be harmful to the Exchange system after a transport server or service failure.
The messages may be genuinely harmful in their content and format.
Alternatively, they may be the results of a poorly written agent that has caused the Exchange server to fail when it processed the supposedly bad messages.
The poison message queue is typically empty. If the poison message queue contains no messages it doesn't appear in Queue Viewer or
Get-Queue results. The messages in the poison message queue are never automatically resumed or expired. Messages remain in the poison message queue until they're manually resumed or removed by an administrator.
According to the description above, I suspect Outlook 2007 changed the email's format when send email with attachment. The reason as below:
If the original email's (with attachment) content or format is harmful to the Exchange 2007 server, it will go to the Poison Queue when sending via OWA. However it didn't, sending via OWA is perfect. So I suspect it is an issue on the Outlook 2007
client side.
Please using Pipeline Tracing to verify whether there is something changed during transmission.
More details in the following article:
Using Pipeline Tracing to Diagnose Transport Agent Problems
http://technet.microsoft.com/en-us/library/bb125198(v=exchg.80).aspx
If it is convenient, I suggest doing following tests to narrow down this issue:
Note: Same content, same attachment, same format.
1. Please using Outlook 2010/2013 or others' Outlook clients for testing.
2. Please change to another format for testing. More details in the following article:
Change the message format to HTML, Rich Text, or plain text
http://office.microsoft.com/en-001/outlook-help/change-the-message-format-to-html-rich-text-or-plain-text-HP001232996.aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

  • Exchange 2007 to 2013 Migration Outlook Anywhere keeps asking password

    Hi all, 
    i'm migrating an Exchange 2007 Server with all roles installed on a Windows Server 2008 R2 to 2 Exchange 2013 SP1 Servers (1 Cas and 1 Mailbox) installed on Windows Server 2012 R2.
    I installed Exchange 2007 SP3 RU13 for coexistance and everything was ok until i switched to the new 2013 CAS. 
    After that the client using Outlook Anywhere started asking for password. 
    I configured the Outlook Anywhere with these settings:
    Exchange 2007:
    OA Hostname mail.domain.com
    Client Authentication NTLM
    IISAuthenticathion Basic, NTLM
    SSL Required True
    Exchange 2013
    OA Hostname mail.domain.com
    Client Authentication NTLM (Both internal and external)
    IISAuthentication Basic, NTLM
    SSL Required True (both internal and external)
    Before switching to 2013 Cas everything works smoothly and the Outlook clients receive NTLM as HTTP Proxy authentication.
    After switching to 2013 Cas, test users migrated on 2013 Mailbox Server are ok, but Outlook users on Exchange 2007 Server get Basic as HTTP Proxy authentication and continue asking for credentials. 
    In the Exchange 2007 server i configured the host file to resolve servername and servername.domain.local with the ipv4 address to avoid issues regarding IPv6 with OA in Exchange 2007. 
    Using Microsoft Connectivity Test i receive the error "RPC Proxy can't be pinged - The remote server returned an error:
    (500) Internal Server Error"
    Any Ideas?
    Thanks for your Help

    Run this and post the result
    https://testconnectivity.microsoft.com/
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Unable to insert hyperlinks in Exchange 2007 OWA messages

    Hi, we have recently moved to Exchange 2007 OWA and users are unable to insert links to shared files on the network.  I was wondering if there might be something in our Windows 7 GPO that is preventing this from happening?

    do you mean they cannot see the network path or that they are not able to type
    \\networkshare\share ?
    If first one,please check Outlook Web app policy and enable/customize Direct file Access.
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

  • How to get current user in Exchange 2007 OWA customization page?

    Hi,all
    I customize an ASPX page(smsconfig.aspx) in Exchange 2007 OWA( this file in ..\Exchange\ClientAccess\OWA\smsconfig.aspx, I don't modify registry.xml & web.config).
    My Exchange 2007 OWA has been configurated with Forms-Based Auth.
    https://mail.myexchange.com/owa/smsconfig.aspx The page works fine, but it cannot get current logon user with HttpContext.Current.User.Identity or
    UserContext.MailboxIdentity or UserContext.LogonIdentity
    <%@ Page language="c#" AutoEventWireup="false" Inherits="Microsoft.Exchange.Clients.Owa.Core.OwaPage" %>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <%@ Import namespace="Microsoft.Exchange.Clients"%>
    <%@ Import namespace="Microsoft.Exchange.Clients.Owa.Core"%>
    <%@ Import namespace="Microsoft.Exchange.Clients.Owa.Premium"%>
    <%@ Import Namespace="System" %>
    <%@ Import Namespace="System.Data" %>
    <%@ Import Namespace="System.Data.SqlClient" %>
    <%@ Import Namespace="System.Xml" %>
    <%@ Import Namespace="System.Collections.Generic" %>
    <%@ Import Namespace="System.Text" %>
    <script runat="server">
    。。。(my codes in here)
    </script>
    thanks for your help.
    Your Passion.My Potential.

    Microsoft.Exchange.Clients.Owa.Core.OwaContext.Current.UserContext.LogonIdentity.PrimarySmtpAddress
    Высказанное мною здесь - мои личные взгляды, а не позиции корпорации Microsoft. Вся информация предоставляется "как есть" без каких-либо гарантий.

  • I have 2 hotmail accounts. They worked fine the first month or so, now about 20 seconds after I sign on, it goes to an send message screen but I cannot send. When I go back to inbox, it resets to the send screen again. HELP.

    I have 2 hotmail accounts. They worked fine the first month or so, now about 20 seconds after I sign on, it goes to an send message screen but I cannot send. When I go back to inbox, it resets to the send screen again. HELP.

    Here you can see how you can setup your Hotmail accounts in the Mail App on the iPad; http://convert-dvd-ipad.com/dvdipad/setup-hotmail-microsoft-exchange-ipad-2/

  • Exchange 2007: attachment missing in Outlook 2013 / owa but it was already opened

    Hi folks,
    We are experiencing a problem with some emails that have attachment.
    We have already opened that Excel attachment in the past weeks. Now, Outlook and also owa displays the icon of the attachment (paperclip) but when we open the email there isn’t the file.
    It seems that something has removed the attachment from the Exchange server also if Outlook has already downloaded the file.
    We are using Outlook 2013 and Exchange 2007.
    Today also the paperclip has disappeared...that's very strange!
    Any ideas?
    Many thanks
    Diego

    Hi Diego,
    From your description, I would like to verify if there are any tips when you open this problematic email. Such as "Outlook blocked access to the following potentially unsafe attachments:". If yes, please post the detailed information for my further
    research.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2007 OWA Error after installing Service Pack 3 (MSExchange OWA event 65)

    Hi everyone, I have multiple servers in Exchange 2007 SP1, Windows Server 2003 SP2 64bit.
    I installed SP3 and RU15 a CAS / HUB server and now I access OWA, showing the below error:
    Outlook Web Access did not initialize. There has been an event for the system administrator can resolve the problem. Contact the support of the organization.
    Object reference not set to an instance of an object.
    Request
    URL: https: // mailserver01: 443 / owa / auth / error.aspx url = https: // mailserver01 / owa / & reason = 0
    Exception
    Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
    Exception message: Object reference not set to an instance of an object.
    Call stack
    in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager () in Microsoft.Exchange.Clients.Owa.Core.Globals.InitializeApplication () in Microsoft.Exchange.Clients.Owa.Core.Global.ExecuteApplicationStart (Object sender,
    EventArgs e)
    Inner Exception
    Exception type: System.NullReferenceException
    Exception message: Object reference not set to an instance of an object.
    Call stack
    in Microsoft.Exchange.Clients.Owa.Core.Configuration.CheckPublicFolders (ADSystemConfigurationSession session, ADObjectID [] pfdbIds, Boolean & allLegacy, Boolean & allLater) in Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor (ADSystemConfigurationSession
    session, String virtualDirectory , String WebSiteName, ADObjectID distinguishedName, Boolean isPhoneticSupportEnabled) in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.LoadConfiguration () in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager
    In server events next event is logged
    Event Type: Error
    Event Source: MSExchange OWA
    Event Category: ADNotifications
    Event ID:. 65
    Date: 12/27/2014
    Time: 7:20:54
    User: Not available
    Team: mailserver01
    Description:
    There was an error loading the configuration parameters of Outlook Web Access. Virtual directory "owa". Website: "Default Web Site".
    Error message:
    "Object reference not set to an instance of an object."
    HOW CAN I SOLVE THIS?
    thank you very much
    Microsoft Certified IT Professional Server Administrator

    Hello
    everyone,
    thank you
    for
    answering,
    finally
    opened
    with
    Microsoft
    support
    case
    and
    showed
    me
    that
    delete
    servers
    from
    ADSEDIT.
    I deleted
    the
    servers
    that
    should
    not
    be
    and
    immediately
    everything
    started
    to
    work
    properly
    Many
    thanks to
    all
    for
    the
    help
    Microsoft Certified IT Professional Server Administrator

  • Microsoft Exchange 2007 owa data storage exception

    Good morning,
    we have MS Exchange 2007 server. I have a problem with the owa service and particularly with one user account. From outlook I can see and navigate in all folders. From owa when I try to navigate in few folders I receive the following exception: Exception type:
    Microsoft.Exchange.Data.Storage.CorruptedDataException Exception message: The configuration object data is corrupted. Field=UserConfigurationType.
    Call Stack: Microsoft.Exchange.Data.Storage.UserConfiguration.BuildConfigurationFromQueryItem(Folder, folder, Object[] row) Microsoft.Exchange.Data.Storage.UserConfiguration.GetIgnoringCache(UserConfigurationManager manager, Folder folder, String configurationName,
    UserConfigurationTypes freefetchType) Microsoft.Exchange.Clients.Owa.Core.UserConfigurationUtilities.GetFolderConfiguration(String configurationName, UserContext userContext, StoreId folderId) Microsoft.Exchange.Clients.Owa.Basic.ListViewPage.OnLoad(EventArgs
    e) Microsoft.Exchange.Clients.Owa.Basic.MessageView.OnLoad(EventArgs e) System.Web.UI.Control.LoadRecursive() System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    Any help will be appreciated.
    Thanks in advance,
    Carlo 

    Hi,
    There are corruptions on the specific mailbox. The cause of my last case for your reference:
    The below property can be missing from the mailbox:
    Tag: 0x7C060003
    Type: PT_LONG
    Property Name(s): PR_ROAMING_DATATYPES, PidTagRoamingDatatypes
    DASL: http://schemas.microsoft.com/mapi/proptag/0x7C060003
    To get to the property of the mailbox, we used MFCMAPI application.
    • Launch MFCMAPI.exe by double clicking it (on client machine where we have logged in as the user).
    • Click on SessionLOGON in the menu bar
    • Double click on the mailbox under the display name column, you will get another window.
    • Expand ROOT CONTAINERTOP OF INFORMATION STORE
    Find the corrupted folders’ properties.
    Thanks,
    Simon Wu
    TechNet Community Support

  • Outlook 2003 clients cannot connect to shared diaries on Exchange 2010

    Having recently upgraded to Exchange 2010 from 2003, I am now receiving calls from users regarding the above.
    I am due to move to Office 2013 later this year but there are some third party app incompatibilities I need to get resolved first.
    So I came across the following article
    https://support.microsoft.com/en-us/kb/2299468?wa=wsignin1.0
    and have changed the default RCAMaxConcurrency from 20 to a very high value of 214783647 and have restarted the Throttling services.
    However, my Outlook 2003 users are still having issues when they have less then 16 calendars open.
    I have ran Get-ThrottlingPolicy to confirm my changes which is correct.
    As another approach, I have got users to run the /resetnavpane switch when lauching Outlook to clear down any orphaned references.
    Can anyone suggest what else I could try?

    Hi,
    As per the information and details provided by you, to solve this issue, please follow these steps: -
    To resolve this problem, create a custom throttling policy by using an increased value for
    RCAMaxConcurrency. Then, associate this custom throttling policy to the mailboxes that require Outlook 2003 clients to open multiple shared calendars.
    After you make this change, wait for the
    Active Directory replication to finish. By default, the throttling policy should be applied after
    15 minutes. To apply it immediately, restart the Microsoft Exchange RPC Client Access service on the
    Client Access Server (CAS).
    Note: - An
    RCAMaxConcurrency value of 100 is suffient in typical cases in which Outlook 2003 has to open
    29 shared calendars. This value may have to be increased, depending on which
    Outlook add-ins is installed.
    Important: - The original release of Exchange Server 2010
    allows a maximum parameters value for RCAMaxConcurrency of 100. Exchange server 2010 service pack 1 increase the maximum value for
    RCAMaxConcurrency to 2147483647.
    I hope this information will be helpful for you.
    Thanks and regards
    Shweta@G 

  • Exchange 2007 OWA with S/MIME installed Context Menu Disspear

    Hi Guys,
    We are experiencing the following issue with Exchange 2007 SP3 OWA when S/MIME control is installed:
    Context Menu and Email Format are grey out
    Does anyone know if this behavior is by design??
    Best Regards
    Federico Giampietri
    Federico Giampietri Latamsupport IT Infrastructure Services

    Hi,
    I tested in my lab, Exchange 2007 SP3. The result is the same with you.
    Without the S/MIME
    control, Cut, Copy, and Paste from the Context Menu worked as expected and I could change email format . When I installed the
    S/MIME
    Control, the behavior with the Context Menu was reproducible, and email format is greyed out, but I could use Ctrl +X/C/V to cut, copy and paste.
    I searched through internal channel and found this behavior is by design. However, as a workaround for choosing Cut, Copy, or Paste from the Context Menu, we can use Ctrl +X/C/V to cut, copy and paste.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Exchange 2010 co-existence with Exchange 2007 issue NDR size Four Times then we send

    Hi All,
    I am facing some strange issues of NDR size four times then we send like if I send 1 MB message to internal OR external recipient then we receive 4 MB NDR.
    Even we send one black mail with subject Test mail of 4 kb then we receive 16 kb NDR is it due to architecture change or something else.
    Everything was fine with Exchange 2007 but facing this issues after we change the mail flow to Ex2010.
    Any help really appreciated
    Regards
    Anand S
    Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

    Hi Anand,
    From your description, the NDR size is four times than original message size. I would like to verify the following thing for troubleshooting:
    How many people has this issue, only one or all the people?
    If only one user has this issue, I recommend you move the user's mailbox to another mailbox database and check the result.
    If all the people have this issue, please enable Pipeline tracing and see if there is any hint. If the issue persists, please install the latest Service Pack and Rollup and check the result.
    Here is an article for your reference.
    Enable Pipeline Tracing
    http://technet.microsoft.com/en-us/library/bb125018(v=exchg.141).aspx
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • How to export an exchange 2007 owa certificate from production to lab environment

    I'm setting up an Exchange 2007 Lab but I have a trouble regarding exchange's certificate
    Note: My lab environment is not conected to internet
    I've followed the next link but it doesn't work
    https://www.digicert.com/ssl-support/pfx-import-export-exchange-2007.htm
    Once I finished all the steps if I run the next powershell command get-excahangecertificate I see that my exchange certificate has the status as unknown
    I'm not sure if the problem is related with the server is not conected to internet, so exchange is not be able to check the status of the certificate.
    I've tried to turn off the Check for publisher’s certificate revocation option on the server
    To do this, follow these steps.
    Start Internet Explorer.
    On the Tools menu, click Internet Options.
    Click the Advanced tab, and then locate the Security section.
    Click to clear the Check for publisher’s certificate revocation check box, and then click OK.
    After the update rollup installation is complete, turn on the Check for publisher’s certificate revocation option.
    But it still not working
    Could anyone help me?
    Thanks in advance

    Hi Pardo,
    According to your description, I understand that the exchange certificate cannot work and display unknown status after import it.
    If I misunderstand your concern, please do not hesitate to let me know.
    Depending on the results of “Get-ExchangeCertificate | FL”, please pay attention to following points:
    1. RootCAType: Registry
    “An internal, private PKI root CA that has been manually installed in the certificate store.”
    2. Status: Unknown
    “This status generally indicates that the status of the certificate cannot be verified because the certificate revocation list (CRL) is unavailable or this server cannot connect to it.”
    The reason why it failed is that internal Exchange server cannot connect to CRL. As you mentioned, exchange can’t be able to check the status of the certificate.
    More information about Certificate Use in Exchange Server 2007, please refer to
    Certificate Fields and Configuring Access to the Certificate Revocation List
    section in below link:
    http://technet.microsoft.com/en-us/library/bb851505(v=exchg.80).aspx
    However, we can renew a certicate from local CA:
    http://technet.microsoft.com/en-us/library/bb310781(v=exchg.80).aspx
    Best Regards,
    Allen Wang

  • Publish Exchange 2013 OWA + Active Sync + Outlook Anywhere using TMG 2010

    We plan to publish our new Exchange 2013 SP1 servers (3 in DAG) outside corporate network using TMG 2010. I am looking for some guide how to do it in the proper way. What I found is little old and does not take into consideration Exchange 2013
    SP1
    http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
    Any advice how to publish Exchange 2013 OWA using form-based authentication and how to use Kerberos Constrained Delegation?

    Hi,
    The blog below describes some scenarios about publishing Exchange. You could have a look the Scenario 2.
    Exchange publishing after TMG/UAG
    http://dizdarevic.ba/ddamirblog/?p=168
    Note: Microsoft provides third-party contact information to help you find technical support. This contact
    information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information
    Best Regards,
    Joyce
    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.

  • Rmi client cannot send message

    Hi
    I'm running the rmiregistry server at port 8000.
    My application uses an API which reads a file for its configuration. I've set the RMI PORT to 8000 in the config file.
    Its possible to telnet "IP:8000" from the remote machine but when the remote application tries to send a message (using the api) it gets an error "cannot send message". The remote application also uses a config file to determine the IP and PORT it'll connect to. IP is set to the address where server program is running and port is set to 8000.
    The server api generates a log (showing each message processed) : Log generated indicates that API starts successfully but there are no entries for any messages received. Seems the messages are not arriving at all.
    Is any more configuration required?
    Regards,

    Here goes:
    The application communicates with an MMSC. Has two threads one for sending and another for receiving messages.
    The sending Thread is working just fine. Both Threads use an API for communicating with the MMSC.
    I start the RMIregistry Server with the following:
    java -cp path/ApiName.jar sun.rmi.registry.RegistryImpl 8000
    One needs to implement an Listener interface to receive messages.
    Here's my class for the same
    public class ReceiveMMS extends Thread implements MsgListener {
    public void run(){
              while(true){
                   try{
                        Thread.sleep(1000);
                   catch (Exception e) {
                        e.printStackTrace();
    public ReceiveMMS() {
              try {
              System.out.println("Registering application to receive messages...");
              APIClassInstance.registerToReceiveMessages(this);
              System.out.println("Application Now Listening for messages.");
              catch (ApiNotYetStartedException anyse) {
                   System.out.println("Exception caught while Registering Application: " + anyse);
    public Result processThisMessage(MessageArrivedEvent mae) {
    Result _result = new Result(ResultCodes.SUCCESS,"Receive Message Successful");
    try {
    System.out.println("New Multimedia Message Arrived. Fetching it...");
    // call fetchMessage() to fetch message from queue
    MimeBodyPart _receivedMessage = APIClassInstance.fetchMessage();
         //MESSAGE PROCESSING LOGIC
    catch (ApiNotYetStartedException anyse) {
    System.out.println("");
    _result.setResultCode(ResultCodes.FAILURE);
    _result.setResultText(": "+anyse);
    catch (NoMessagePresentException nmpe) {
    System.out.println(" : "+nmpe);
    _result.setResultCode(ResultCodes.FAILURE);
    _result.setResultText("No Message Present : "+nmpe);
    catch (CannotFetchMessageException cfme) {
    System.out.println("Cannot Fetch Message - Check RECEIVE property :"+cfme);
    _result.setResultCode(ResultCodes.FAILURE);
    _result.setResultText("Cannot Fetch Message. Check RECEIVE property :"+cfme);
    catch (Exception e) {
    System.out.println("Error Handling Message : "+e);
    _result.setResultCode(ResultCodes.FAILURE);
    _result.setResultText("Error Handling Message : "+e);
    return _result;
    processThisMessage() METHOD is called when a message arrives. This notification is not taking place.
    Is there a special way for making this notification happen
    what i can figure is, some configuration is missing, and the remote app is not able to notify the MessageHandler.
    The API starts successfully and is able to connect to remote system (sure, as it can send messages). The api uses RMi internally--when dont start the registry server i get the 'Class not found for the STUB Class'
    Regards

  • Outlook 2010 clients cannot access their Online Archive mailbox in Exchange 2013??

    Hello,
    I have an issue where my Outlook 2010user cannot see/access their Archive mailbox when they are migrated from Exchange 2010 to Exchange 2013.
    Both the live and archive mailbox is in Exchange 2013, the user can launch Outlook but if they click on their Archive mailbox it is unavailable.
    Once the user is upgraded to SP2 or Outlook 2013 they have no issues accessing their archive mailbox.
    These users have the minimum required Outlook version (14.0.6126.5000),
    they are running 14.0.6129.5000.
    Is there a different requirement on the Outlook client if the user has an archive mailbox in Exchange 2013 as well?
    Thank you.

    Hi,
    Is there any update on this thread?
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If
    you have feedback for TechNet Subscriber Support, contact [email protected]
    Simon Wu
    TechNet Community Support

Maybe you are looking for

  • Printing to Windows HP Color Laserjet 1500L

    I have just set up my macbook to print to my Lexmark E232 over my widows network. It works great. So I followed a similar approach for my HP Color Lasejet 1500L. However when I get to the final step where you choose the actual printer Model (after sl

  • A question about archive and install

    Recently my system crashed due to a faulty OS instal. So, I hauled my G4 to the mac store and they resoved the problem for me and told me to do a archive and instal, and even gave me instructions. Everything was going fine untill it came the time to

  • I have music on my iMac and more on an external hard drive . How can I amalgamate all on my iMac?

    Have an iMac  21.5 in late 2012 running iOS 10.10.2 Yosemite I have 25.74 GB of music on the iMac and 109.27 GB on an iOmega hard drive (500GB) and I Want to transfer all of this to the iMac. How do I do this?

  • JSP cannot be found in IBM WebSphere 5.1

    Hi, I'm getting the following error in my websphere when I try to execute my index.jsp page: SRVE0026E: [Servlet Error]-[/index.jsp(2,0) /SkinProperties.jsp(0,0) Impossible to read file: /includes/initSkin.jsp sun.io.MalformedInputException]: org.apa

  • GetURL:: works for all but my client!

    I have a two buttons at the end of a movie that should go to next page when clicked. Works great for me on PC with XP or Vista and IE 6 & 7, FF 2 and Netscape 7. Works on Mac OS 10.2 with Safari. Works on my friend's Mac with OS 10.3.9 and IE 5.2. Do