Exchange 5.5 portlets problems

I am having a number of problems. I have portal installed on NT4. We are running exchange 5.5 and IIS4 and they are in the same domain. I can add the inbox portlet and I can view my email. But when I try to open a message, it comes up with a login screen and I login and then I get a browser window with "Page cannot be displayed" error. I also get the same message when I click on the "New Message" link.
The next problem I get is when I add the contacts portlet and the calendar portlet, either the inbox, the contact, or the calendar portlet will time out. They won't all show up together. If I do a refresh, sometimes they will switch. For example if the inbox was showing and the other 2 were timed out and I do a refresh, then the calendar will show up and the inbox and the contacts will be timed out. And then sometimes when I do a refresh I will get all three portlets showing up with this in them:
Collaboration Data Objects error '0000043f'
[Collaboration Data Objects - [E_INVALIDARG(80070057)]]
/exchange/inbox.asp, line 38
Collaboration Data Objects error '0000043f'
[Collaboration Data Objects - [E_INVALIDARG(80070057)]]
/exchange/calendar.asp, line 36
Collaboration Data Objects error '0000043f'
[Collaboration Data Objects - [E_INVALIDARG(80070057)]]
/exchange/contacts.asp, line 35
Then in order for it to get at least one of them to work again I have to reboot the IIS server.
This stuff is driving me crazy. Can someone please help.
Thanks for any assistance.
Randy

Randy,
Please specify whether or not you are using the latest version of the Exchange portlets that became available in PDK-March. This version is fundamentally different from prior versions and may resolve some of the issues you are seeing.
Regarding the "Page could not be displayed" error upon clicking the message links, this may be an issue with your Outlook Web Access configuration. Do you have Outlook Web Access installed? If so, you need to make sure that the links in the portlet point to your instance of Outlook Web Access. By default they should point to the host on which the portlet ASPs are installed, but if this is not where Outlook Web Access is installed, you may not see anything when you click on a link.
Regarding the refresh error and the "E_INVALIDARG" message, this may be something with the parameters you are providing to the provider (server, etc.). Also check this thread: Re: FRM-92090 : An unexpected error occurred Simon Joll apparently had the same error and resolved it by configuring his Outlook Web Access correctly. You may want to follow up with him.
James

Similar Messages

Exchange 5.5 Portlet, versions, and CDO Error

I am unable to get the Exchange 5.5 Portlets to work. I am
running Portal 3.0.9.8.0, Exchange Server 5.5 SP3 (does it need
to be SP4?), and IIS 5.0 on Win2K. The Exchange Server is
running on another box (WinNT SP5).
When running the test.asp file I get the following:
CDO Version: 1.21
Collaboration Data Objects error '000043ed'
[ - [(80004005)]]
/ExchangePortlets/test.asp, line 33
I added the line reporting the CDO version this machine is using
(it came from the MS Outlook XP install) Would this cause
problems seeing it is slightly newer then the CDO library on the
Exchange server?
Anyway, I continued through the instructions despite the above
error and added the portlet, however it simply reports the "User
authentication failed. Please..." message all the time,
regardless of the credentials entered.
Another note, when attempting Stage 5 step 2 of the
instructions, Login to the Exchange External Application, after
I enter the details I get a plain looking form with all the
field boxes again, empty. I had seen someone else mention this
behaviour but there was no solution.
Any help out there?

I've found out what's causing
[Collaboration Data Objects - [MAPI_E_NOT_FOUND(8004010F)]]
to appear in test.asp. (By the way, if you are getting this in
test.asp, your portlets will not work).
EXPLANATION: When an ASP page uses CDO to logon to an Exchange
mailbox, IIS creates a temporary .mmp file to store
necessary profile information. However it stores the temporary
file in the directory where Windows is installed. Users who do
not have permissions for that directory will not be able to
access the .mmp file and they will get the
MAPI_E_NOT_FOUND error.
FIX: Configure the Windows Messaging Subsystem to store the
.mmp file to a directory that users have access to.
- Start Registry Editor (regedt32.exe) on the machine that has
IIS.
- Go to the following key:
HKEY_LOCAL_MACHINE/Software/Microsoft/Windows Messaging
Subsystem
- On the Edit Menu, click Add Value.
- Value Name: ProfileDirectory
- Data Type: REG_SZ
- String: Path to the directory you want the .mmp files to be
created in. E.g., C:\temp
- Make sure everyone has change permissions for the temp
directory.
James

Exchange 5.5 Portlet CDO error

Hi,
I'm trying to implement the Exchange 5.5 portlet. My specs:
IIS 4 on W2k Workstation
OWA on same machine
Exchange 5.5 SP4 on NT4 server SP5
I've followed all the directions (and suggestions) but stil run into the following error:
Collaboration Data Objects (0x505)
The Microsoft Exchange Server computer is not available.
Either there are network problems or the
Microsoft Exchange Server computer is down for maintenance.
[Microsoft Exchange Server Information Store - [MAPI_E_FAILONEPROVIDER(8004011D)]]
/ex_portlet/test.asp, line 16
Line 16 of test.asp is: set objInbox = objSession.Inbox
It just times out.
OWA alone works fine. Exchange is working fine.
I'm authenticating OK. But then nothing.
Any Help, Please????
Thanks,
Steve

Can Steve or anybody who has experienced the same error (as Steve has), while trying to install microsoft portlets, let me know whats the solution ?
I have Exchange 2000 though and have the latest (June) PDK, URL services and Exchange 2000 portlets. IIS and Exchange are on different machines but the same domain. OWA is installed on a different machine from IIS.
thanks
Sarita

Final and Finishing Touch needed for Exchange 5.5 Portlet

Hai,
I have seriously followed yours postings regarding Exchange
5.5 portlet implementation.I daresay I am able to see all my
inbox,calendar and contacts. But the problem I face is little
bit different. Please go through and analyse and get me a way
to avoid delay in Project Completion.
1. I have configured IIS,Exchange,Outlook as per the
installation Guide.
2. It woks fine for Single person's data ( Since I type a
default inbox name for the user when adding external application
( if I leave it as "null" I am getting "nullpointer exception "
from Java), only that user can login to my page and see the
content.
3. When I try to create another user I need to type his mailbox
name, but the older credentials vanishes and only the current
user's data are seen. ( Even though I create the new user after
running ssolocal script in portal30_sso schema ). The
subscriber_id in wwsso_appuserinfo_t table gets all values
as "1". I think this must be the problem. If such how we can set
subscriber_id column incremented whenever a new user is being
created.
So I face the problem only with single sign on, not with any
other else. Please solve me the problem and let me finish my
assignment as soon as possible.
Thanks in advance,
Sorry for disturbing you,
Johnson

Can you clarify what you mean by "only the current user's data
are seen"? Are you logging off and logging back in as the newly
created user?
3. When I try to create another user I need to type his mailbox
name, but the older credentials vanishes and only the current
user's data are seen. ( Even though I create the new user after
running ssolocal script in portal30_sso schema ). The
subscriber_id in wwsso_appuserinfo_t table gets all values
as "1". I think this must be the problem. If such how we can set
subscriber_id column incremented whenever a new user is being
created.

Exchange 5.5 portlet refresh fails

I have installed Exchange 5.5 Portlet, onto POrtal 3.0.9.8.3 running on 2000, and everything seems to be fine - the test pages of IIS worked, as did the External APplications test.When placed on a page, the Inbox and Calendar portlets appear correctly on a page. Items can also be succesfully opened, with correct prompting for SSO and OWA logins.
However, the following actions cause the portlets to be redrawn as just portlet header bars, with no data being displayed, and no apparent way of re-populating them other than closing the session and starting again:-
- going to the customize screen and returning
- clicking on the Next link for the next 10 messages
- refeshing
- using Back and FOrward buttons.
Does anyone have any help to offer me on this?
Many thanks
Mark

This is the contents of jserv.log after opening the page with the portlets on it, opening one email, then clicking "Next 10"
IN ExternalProvider.initSession...
App user: owainp
IN ApplicationLogin.getApplicationCookie...
App user:owainp
App password:password
App domain:wg
App mailbox:owainp
App exserver:wgex2
App serverURL:http://wgowa01/exchange_portlet/
App OutlookWebAccessURL:http://wgowa01/exchange/
Creating a user cookie
COOKIE: owainp|password|wg|owainp|wgex2|http://wgowa01/exchange_portlet/|http://wgowa01/exchange/
COOKIEPATH: /servlets/exchangeApp
User DOES have credentials.
After setting up Jser session cookie
After setting expiry
Returning cookies
IN ApplicationLogin Constructor...
Found cookie.
COOKIE: owainp|password|wg|owainp|wgex2|http://wgowa01/exchange_portlet/|http://wgowa01/exchange/
COOKIEPATH: null
App user: owainp
App password: password
App domain: wg
App mailbox: owainp
App exserver: wgex2
App webserverURL: http://wgowa01/exchange_portlet/
App OutlookWebAccessURL: http://wgowa01/exchange/
IN ApplicationLogin Constructor...
Found cookie.
COOKIE: owainp|password|wg|owainp|wgex2|http://wgowa01/exchange_portlet/|http://wgowa01/exchange/
COOKIEPATH: null
App user: owainp
App password: password
App domain: wg
App mailbox: owainp
App exserver: wgex2
App webserverURL: http://wgowa01/exchange_portlet/
App OutlookWebAccessURL: http://wgowa01/exchange/
IN ApplicationLogin Constructor...
IN ApplicationLogin Constructor...
The last two appear lines appeared after the Next link was pressed, but also after a refresh, Customize link or back/forward.
I hope this is enough info, Amjad
Mark

Exchange 3.2 Portlet Customization

We need Community Calendar functionality on a my page with Community prefernces set as Admin preferences . How can we implement that ? Alternativey we need to display read Only access Exhange calaendar, with users having no ability to add/modify or delete a calendar item. All they can do is simply read it.

This functionality is provided in the Exchange Calendar Community portlet. This portlet can only be added to a community page. Unless the community users have create/edit/delete permissions, they will have read only access to the calendar items.

Exchange Portlet problem

hi experts,
we have a problem getting the asp pages that come with the exchange portlet running. The inbox.asp script runs fine, when not the contacts.asp and calendar.asp, they both come back with the error message that the
the method 'GetDefaultFolder' is not supported. We are running IIS server on a different NT-Box(Service Pack 6) as the exchange 5.5 server, but within the same domain. Anybody experienced the same problem?
thanks,
Benjamin

Benjamin,
See if this thread helps:
Re: OCI JDBC Driver - Runtime UnsatisfiedLinkError
James

Error in Exchange 2K Contacts Portlet

There is an error in January PDK Exchange 2000 Portlet Contacts:
Error: Variable Undefined
'lngRowsLeft' line 428
To fix, add
'Dim lngRowsLeft'
under
'Variable declaration for locale-specific strings'
r/ George

This is a very strange problem. The asp specification doesn't mention that you need to declare a variable before using it in the code. But, in the contacts.asp, an error:"Variable Undefined...." is being thrown. And the same code seems to work fine in the other portlets, like inbox.asp and calendar.asp, without declaring the var lngRowsLeft. Asp experts may be able to help us out in resolving this mystery.

Exchange 5.5 Portlet, versions, etc. UPDATE

I have rectified my other problem but now have a new one. For
those wondering I ended up moving the ASP files to our
production web servers (where OWA is running) as I knew CDO
worked perfectly fine there.
However, the portlets are still not rendering, still displaying
the user authentication problems. I removed and recreated both
the Exchange provider and application, to no avail.
The test.asp script now works fine. I can also run the inbox.asp
script (passing the same parameters) and I get what I assume is
the portlet contents correctly (it displays the inbox with
messages). So it would appear the problem lies somewhere in
passing the login credentials from Login Server to the ASP files.
Any other ideas?

Thanx for the reply.
All machines are on the same domain. Have tried with 3 different
exchange mailboxes and NT accounts, none have worked from Portal
but all work from when passed to inbox.asp or in OWA. All
machines are also on the same subnet. I downloaded the JPDK
yesterday, so I assume it is the latest. Very frustrating! I
have a bit of experience with CDO so this is even more
frustrating!
Summary of machines used(3):
1. Win 2K Server SP1 - Oracle 8.1.7 DB, 9iAS 1.0.2.2.1, Apache
2. Win 2K Server SP1 - IIS 5.0, Outlook Web Access 5.5 SP3
3. Win NT Server SP5 - Exchange 5.5 SP3
-- all on same domain and subnet --
Is there anyway of getting a more specific error back from the
portlet? I assume the portlet simply traps ANY error from the
inbox.asp file and displays the authentication failure message
if it didn't work. I have no experience in Java yet so if you
could tell me a line to go in and add somewhere that would
return the actual output of the inbox.asp file regardless that
might help.

Exchange 5.5 portlet still not working

I have not been able to access the exchange portlet as an external application. I have tried the various sugestions from this forum but have still not succeded. It seems that the call to ../servlet/exchangeApp?ExchangeAction=performlogin has no effect -- it is not performing a login. Instead, it generates a login page with blank parameters.
After deleting the external application (Exchange Inbox) and adding it again will all of the parameters included, I still have the same problem -- the servlet generates a login page with blank parameters. Supplying the parameters to this new page and submitting the form has no effect.
The results of test.asp are "VALID".
Does anyone have any idea what may be going on here? We were hoping to go production in a few weeks with the exchange portlets working.
Environment: Portal 3.0.9/W2K -> IIS/W2K -> Exchange 5.5/NT

I have not been able to access the exchange portlet as an external application. I have tried the various sugestions from
this forum but have still not succeded. It seems that the call
to ../servlet/exchangeApp?ExchangeAction=performlogin has no
effect -- it is not performing a login. Instead, it generates a
login page with blank parameters.
>
After deleting the external application (Exchange Inbox) and adding it again will all of the parameters included, I still
have the same problem -- the servlet generates a login page with
blank parameters. Supplying the parameters to this new page and
submitting the form has no effect.
>
The results of test.asp are "VALID".
Does anyone have any idea what may be going on here? We were hoping to go production in a few weeks with the exchange
portlets working.
>
Environment: Portal 3.0.9/W2K -> IIS/W2K -> Exchange 5.5/NT First, let me state that there are many implementations of the
exchange portlets that are working. Unfortunately, none of
those users are coming to this forum and talking about their
successes! That being said, we want to help you resolve your
issues and get the portlets implemented in your environment.
Typically, if the external application login is failing, it
means that one or more of the fields or values is incorrect.
I have seen an earlier posting indicating that once an external
application has been created, subsequent edits are not being
saved. While I have not seen that for myself, my first
suggestion to you is to create another external application
entry with the correct values and try logging into it again by
clicking on the application name in the Administer External
Applications page.

Exchange 5.5 portlets working! (Almost)

For me, the problem of a "blank login form" displaying when
adding the Exchange Portlets External application was a result
of an incorrect password for the IUSR (Anonymous user). Stage
1, Step 7 of the installation instructions states you should
Allow Anonymous Access. Make sure the password for the the
Anonymous user (usually IUSER_<servername>) has not been
inadvertently changed or deleted by clicking on EDIT in the
Anonymous user section. Once I changed this to the correct
password, the "blank login form" problem was fixed and the
portlets displayed correctly.
The only issue I have now is that the portlets cannot be
customized and they do not refresh automatically. If I
click "Customize" on any of the portlets, make changes and click
either APPLY or OK, a blank screen is displayed with a "Home"
icon. Any changes are not applied. The log file shows the
following error:
exchangeAppProv/Error creating D:\exchange\72632261\1
\283_EXCHANGEINBOXPORTLET_72632261\testuser.dat : null
John

To anyone who is having problems customizing the Exchange
portlets:
Compare the result you get when you customize by specifying
values for SOME of the fields vs. the result you get when you
specify values for ALL of the fields.
In particular, does the customize work okay when you enter a
value for all of the customizable fields?
Also, please provide a specific Portal and JPDK version number
for reference.
Thanks,
James

Exchange 3.1 Portlets error

Hi all,
I'm working with Exchange Portlet 3.1. running on Portal 5.0.4 an Windows 2003.
After installing the package, importing the .pte file and properly configured the Exchange server and user credentials, I can see Inbox/Calendar/addressbook of my user, I can send messages, I can search the address book;
BUT when I try to open a received message i get the following error:
"There was a problem communicating with the backend system. Contact your portal administrator."
Any ideas? Am I missing something?
I also found someone else that faced the same problem but there is no posted solution.
Jacopo

Greetings,
I'm using Portal 5.0.4 Exchange suite 3.1
I get the same error. The install test page works fine. I can send email. I can view and search my contacts. When I try to open an email or open a calendar entry I get the "
There was a problem communicating with the backend system. Contact your portal administrator."
Error.
Any help would be great.

Exchange 2013 mail flow problem

Hello!
We have problem, could not send mails via Exchange 2013 server.
Symptoms:
-no messages in message queue
-if sending mail to this domain, the message seems sent at Sender.
-if sending mail from this domain, the messages are in the mailboxes' DRAFT folder
Here are some SMTP logs:
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,10,192.168.3.2:26408,192.168.3.2:2525,<,250-STARTTLS,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,11,192.168.3.2:26408,192.168.3.2:2525,<,250-AUTH NTLM,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,12,192.168.3.2:26408,192.168.3.2:2525,<,250-8BITMIME,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,13,192.168.3.2:26408,192.168.3.2:2525,<,250-BINARYMIME,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,14,192.168.3.2:26408,192.168.3.2:2525,<,250 CHUNKING,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,15,192.168.3.2:26408,192.168.3.2:2525,*,,"EHLO options between current server and proxy target do not match : Xrdst, . Critical
non matching options : Xrdst, . Failing over."
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,16,192.168.3.2:26408,192.168.3.2:2525,>,QUIT,
Software Enviroment:
-Windows Server 2012 Server Standard
-Exchange Server 2013
-fully patched system (includes the brand new Exchange 2013 CU1), the error was realized before this update.
Regards.
molni

Hi
Can you run ipconfig/flushdns or create hosts file recorder?
Terence Yu
TechNet Community Support

Exchange 2013 - Mail receive problem -Help!

Exchange 2013 SP1 -fresh install -test environment with one test mailbox setup in addition to the Administrator account. Using default Receive Connectors and it is set for Anonymous. Using OWA and Outlook 2010 for testing.
We can send/receive mail INTERNALLY in both Outlook & OWA between our test user and the Administrator user.
We can send mail externally from both accounts.
We are not receiving mail into the Inbox of either OWA or Outlook.
We are not seeing any authentication issues with Outlook -always shows connected to Exchange. But if we have same problem in OWA then we are just testing with it for now.
We ran the Microsoft Connectivity Analyzer for both Inbound and Outbound SMTP and it passed with no errors/warnings L
We did NSLOOKUP, from a Command prompt at the server wtith this result -not sure why it shows server as unknown?:

Thank you for replying. Yes the mailbox is at Time Warner and I can use their webmail interface and see the messages I sent to the test user are there.
No, our domain name is companyname.com (if you need the actual name..I am not sure if I should send it to you?) and we use
[email protected] for email.
Our external A records and MX records are at Network solutions and that is posted here-- but decided to start another thread with more concise information as I learned of it:
http://social.technet.microsoft.com/Forums/office/en-US/0b18e928-0207-4ab9-bc12-c00a75088bdc/new-deployment-outlook-can-send-but-not-receiving-messages?forum=exchangesvrsecuremessaging
When I do NSLOOKUP of our domain I get just the two MX records at Time Warner. Not anything with our actual domain name for email in it. I just added the A records for mail.companyname.com and autodiscover at Network Solutions yesterday...but though those
were only for use externally for OWA, ActiveSync, etc
Note we do not use Split-DNS on our internal domain either. Our AD name is different than our public domain name - The AD is named with a subdomain: qs.companyname.com
Lastly, I did not create an MX record at network solutions for mail.domainname.com. Should I do that and set it to a higher priority?

No new mail notification in Outlook - CAS Exchange RPC Client Access problem

Hi, we're facing this problem:
Users start complaining they suddenly don’t receive new mail notifications in Outlook (2010/2013) anymore
Inbox does not show the new mail either
When the user changes folders in outlook, the new mail does show in the Inbox folder
Restarting Outlook shows the new mail as well.
The same new e-mail arrives instantly (with notifications) in Owa and on mobile devices
Sometimes the new mail notification pops up after a longer period of time (from 30 seconds to 10 minutes). But more often not at all.
This issue seems to occur at random. We’ve been problem free for a week, and sometimes it comes back three times a day.
Clients running Outlook 2010, 2013 cached or online, on site and off site. So it seems server related, not client.
It was seen first around January 8th. We did not make any changes around that time that we can link to this problem.
Only one CAS server (EXCH1-RTD) shows this issue. CAS servers on other sites are ok
EXCH1-RTD has CAS and HUB transport roles. The same site has two mailbox only servers. EXCH2-RTD (mailbox server for normal mailboxes). And EXCH3-RTD (mailbox server for archive mailboxes)
No entries in the event logs that seems to be related
As the problem only occurs with Outlook clients, I suspected RPC issues. We cannot gracefully stop the “Microsoft Exchange RPC Client Access” service on EXCH1-RTD while the issue occurs. We
can only kill the process and restart the service, solving the issue instantly.
What we’ve tried until now:
Updated all Exchange servers from Exchange 2010 SP3 RU6 to RU8-v2 (server OS=W2K8R2)
Updated all Exchange servers to latest critical Windows updates
Recalculated requirements using MS Sizing tool. Upgraded EXCH1-RTD VM from 8GB and 2 vCPU (1 core/cpu) to 16GB
and 4vCPU (1 core/cpu)
Ran various perfmon counters and compared them with other Exchange servers, not finding any obvious anomalies.
Any ideas would be greatly appreciated!
Ron

Hi Ron,
From your description, OWA works well, the issue is related to Outlook side. In your case, I recommend you use Outlook safe mode to determine whether the issue is related to add-ins. If the issue persists, you can create a new profile to check the result.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Exchange 5.5 portlets problems

Similar Messages

Maybe you are looking for