Work Manager 6.0 for SMP 2.3 - standalone server - Startup Exceptions

Hello Experts.
I am installing a standalone Agentry Server for Work Manager 6.0 on the server where we have installed SMP 2.3.
It has been installed successfully and does start up, however I get some annoying error messages during start up.
It seems that the server is running - I can succesfully synchronize to an ATE client.
Due to the results from this thread, I have changed all ports in the Agentry.ini file to separate ports numbered 7521, 7522, 7523 and 7524.
Port issues - SMP and Agentry
Errors from the startup.log:
13:26:00 05/05/2014: HTTP-XML Back End Back End: Started
13:26:00 05/05/2014: Server: Starting threads.
13:26:00 05/05/2014: 1 initial threads. Threads will auto-scale.
13:26:00 05/05/2014: Event: 20, 4, Server v6.1.0.3
13:26:00 05/05/2014: Starting front ends
13:26:00 05/05/2014: ANGEL Front End: Starting threads.
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: 3 initial threads. Threads will auto-scale.
13:26:00 05/05/2014: ANGEL Front End: opening listen socket on port 7523
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: Event: 17, 10, 0.0.0.0:7523 open
13:26:00 05/05/2014: Event: 17, 10, ANGEL Front End v6.1.0.3
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: Event: 0, 0, Old log files moved into Logs-Rolled\2014-05-05-132546
13:26:00 05/05/2014: Event: 0, 23, 4
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:01 05/05/2014: Event: 0, 2, Server startup is complete.
13:26:01 05/05/2014: Agentry Application startup complete
Can anybody help with the meaning and implications of these errors ?
Thank you.
Søren Hansen.

Damn... I missed one port
You are correct. The default port (8282) of Agentry is used multiple places in the Agentry.ini file, and collides with SMP.
Thanks Steve.
For others:
Please make sure the following ports of the Agentry.ini file are unique across all applications on the server. In this case I have chosen to call all my ports on this instance 752X.
Now the server starts without errors.
[ANGEL Front End Ports]
1=7523
[TCP Front End]
listenOn=7521
[Java-1]
nonStandardJavaOptions=-Xdebug -Xrunjdwp:transport=dt_socket,address=7524,server=y,suspend=n
[HTTPXML-2]
baseURL=http://localhost:7522
listenOn=7525
Søren Hansen.

Similar Messages

Work Manager 6.1 and SMP 3.0 with Agentry new features

Hi,
I know that Work Manager 6.1 is expected to be released by the end of June but I can't find any information about the product.
Since I'm starting a new project initially thought for Work Manager 6.0 but running in SMP 3.0, I would like to know the list of new features of 6.1 version.
At the same time I would like to know if the use of SMP 3.0 brings to the Agentry applications improvements regarding error handling, logging and administration in general since that was a bit poor in the previous versions.
The only thing I found regarding 6.1 version is this PDF where new functionalities regarding localization of assets in a map are added. I hope there is more than that.
Thank you for your help.

I guess the following thread answers my questions (except regarding SMP 3.0 logging, administrating and error handling with Agentry): http://scn.sap.com/message/15086739
I copy&paste the basic things to know:
More news during/after Sapphire
New features:
Based on SMP 3.0 using websockets for communication
GIS (ESRI) integration via Open UI
Visual Enterprise 3D integration via Open UI
SAP JCO 3 Support
Crew Management
WRP Customer Service
UX Improvements

Work Manager 6.1 on SMP 3.0 HEC

Hi Experts,
I want to deploy work manager 6.1 on HANA Enterprise Cloud-HEC. Is it possible,if so please provide document or procedure.
Thanks in Advance
Regards,
Sravanthi

SMP Cloud doesn't have Agentry Support currently.

Cannot get db mail to work via SMTP Relay for Office 365 in SQL Server 2014 on Windows Server 2012 R2

Our company recently moved to Office 365 which mean our on premise exchange server went away as well with the move. I am trying to configure my new sql server (OS-Windows Server 2012 R2, DBMS- SQL 2014 Std Edtion). After some searching I found
this article (http://blogs.technet.com/b/meamcs/archive/2013/02/25/how-to-configure-sql-database-mail-so-send-emails-using-office-365-exchange-online-a-walkthrough.aspx) and have followed these steps exactly, but to no avail. I did some further research
on the SMTP relay I setup and found a way to test it (listed here http://technet.microsoft.com/en-us/library/dn592151(v=exchg.150).aspx at the bottom of the article). If I drop the email.txt file in the pickup folder, it gets sent out no problem.
I have configured my db email exactly as describe here(http://blogs.technet.com/b/meamcs/archive/2013/02/25/how-to-configure-sql-database-mail-so-send-emails-using-office-365-exchange-online-a-walkthrough.aspx). But keep getting an unable to connect
to SMTP server error. I have even tried completely shutting down firewall to see if that is the issue and multiple restarts. Any ideas how to get this to work on Office 365?
DB Mail error log:
Date 6/10/2014 10:28:41 PM
Log Database Mail (Database Mail Log)
Log ID 46
Process ID 2196
Mail Item ID 19
Last Modified 6/10/2014 10:28:41 PM
Last Modified By xx
Message
The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 2 (2014-06-10T22:28:41). Exception Message: Cannot send mails to mail server. (Failure sending mail.).

Hi,
I followed this blog and got the below error message in the Database Mail Log.
“The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 2 (2014-06-11T19:34:00). Exception Message: Cannot send mails to mail server. (Mailbox unavailable. The server response was: 5.7.1 Unable to relay
for [email protected]).”
If you are getting the same error message, you can try the below steps to resolve the issue.
1. Open the IIS 6.0 management console. Right click on the SMTP server and open the properties window.
2. Click on the Access tab, click Relay button under Relay restrictions. loopback IP address (i.e 127.0.0.1).
Then the email should be sent out from Database Mail without problem.
Thanks.
Tracy Cai
TechNet Community Support

Applying recommend settings from "microsoft security compliance manager 3.0.60.0" to a standalone Server using LocalGPO.wsf on Server 2012 R2

Hello
Can someone please help me with the following question.
I have a standalone Server and need to apply settings from SCM, I can see how to do this following the instructions in the following article
http://windowsitpro.com/security/q-how-can-i-apply-security-baseline-i-defined-through-microsoft-security-compliance-manager
The problem is the LocalGPO.wsf that ships with the above version of SCM does not run on Server 2012 R2 (only Server 2012)
my question is,
is there a later version of LocalGPO.wsf I can use that works on Server 2012 R2 ?
Thanks
AAnotherUser__
AAnotherUser__

Hi,
Thanks for your post.
SCM Baselines for Windows 8.1, IE 11 and Server 2012 R2 are now live!
http://blogs.technet.com/b/secguide/archive/2014/09/04/scm-baselines-for-windows-8-1-ie-11-and-server-2012-r2-are-now-live.aspx
For more SCM related issue, i think you may ask in:
https://social.technet.microsoft.com/Forums/en-US/home?forum=compliancemanagement
Regards.
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 Support, contact [email protected]

Best Practices for directory structure Grid (standalone server) + DB

I want to install Oracle Database and Oracle Grid Infrastructure for a standalone server for ASM and Oracle Restart. I understand that they need to be installed in different folders with different access rights. But how it is better for making?
In documentation "Oracle® Database Quick Installation Guide 11g Release 2 (11.2) for Linux x86-64" anything specific it is not written. Here exposures from the documentation with examples. Such examples only confuse me.
for oracle
# mkdir-p/u01/app/
# chown-R oracle:oinstall/u01/app/
# chmod-R 775/u01/app/
for grid
$ ORACLE_HOME=/u01/app/oracle/product/11.2.0/grid
$ export ORACLE_HOME
ORACLE_HOME =/u01/app/11.2.0/grid; export ORACLE_HOME
I made so - db_1 for Grid db_2 for DB:
/u01/app/oracle/product/11.2.0/db_1 - for Grid
/u01/app/oracle/product/11.2.0/db_2 - for DB
But I have doubts that so will be correct. I can not understand what permissions on what folder to give.
Questions:
1) What to create structure of folders for installation DB + Grid?
2) What permissions at users should be in this structure?

HI!
Check documentation again!!!

Replacement for 10g Forms&Reports standalone server in 11g?

is there a replacement for the 10g Forms&Reports standalone server in 11g environment? Without the need to install Metadata Repository?
thx, florian.
Edited by: fschulze on Oct 16, 2009 1:12 PM

I believe you can install the equivalent in Forms 11g.
If you don't install Portal or Discoverer, then you are not required to install any Metadata repository.
So the steps would be:
1) Install Weblogic Server 11g
2) Install Forms and Report Services 11g
How will you call reports from forms though?

Upgrading work manager 5.3 to 6.1 with out SMP 3.0

Hello Experts,
As per the blogs and posts, work manager 6.0 is designed for SMP 2.3 and work manager 6.1 for SMP 3.0.Can we use work manager 6.1(with its additional features)without SMP 3.0 similar to work manager 5.3.Can we have standalone work manager 6.1 server or we need to install complete SMP 3.0 runtime .
Please suggest can we upgrade work manager 5.3 to 6.1 without SMP 3.0 to have standalone Agentry server for work manager 6.1(Like standalone server for work manager 5.3)
Thanks in advance
Thanks & Regards,
Sravanthi Polu

Hi Bill,
Thanks for your reply.What about the customization's done in Work Manager 5.3, will they have impact when we upgrade from 5.3 to 6.1 on SMP 3.0.What is the better approach to retain the custom logic if we go for upgrade(SMP 3.0).As per my knowledge if we go for 6.1 on SMP 3.0, then custom logic need to be implemented again, so considering customization's as higher priority, can we migrate existing Work Manager 5.3(With custom logic(Editor,Java,ECC Changes)) to SMP 3.0.If we migrate custom logic would be retained,but can we make use of the new features in SMP 3.0 like open ui,client branding .... etc.
Please help in this regard.
Thanks in advance.
Regards,
Sravanthi

Upgrading SAP Work manager 5.3 to 6.1 on SMP 3.0

Hi Experts,
We have SMP 3.0 server,work manager 5.3.Now want to upgrade from 5.3 to 6.1 and deploy standard work manager 6.1 (without crew management,meter management,customer service,linear asset management components)on to SMP 3.0
Agentry Editor and SMP 3.0 server are in different systems
Please suggest prerequisite add-ons needed,development and customization guides(for work manager 6.1 on SMP 3.0)
Manju Venkatesha, Please suggest in this scenario.
Thanks
Siva chandu
Tags edited by: Michael Appleby

Deploying WM 6.1 on SMP 3.0 can be found in
http://scn.sap.com/community/mobile/blog/2014/08/30/quick-start-guide-sap-work-manager-6x-with-smp-agentry
Thanks
Manju

SMP 3.0 - Deploying Work Manager 6.1 - Production Landscape

Hi All,
From this blog, I understood how to deploy a development version of Work Manager application on the SMP Development Server.
http://scn.sap.com/docs/DOC-56329
What is the main difference when deploying to a SMP Production Server?
Just copying the Production folder instead of Development folder while creating the archive to deploy on the SMP Server?
Kindly help. And please point to any other useful blogs which have similar information like this.
Regards
Ankur
Tags edited by: Michael Appleby

Ankur,
Deploying to production involves creating a zip file and deploying the zip file to the SMP server through the Management Cockpit..
The Work Manager documentation should also cover the steps needed to deploy the production version to the server as well.
--Bill

Work Manager 6.1: java.lang.reflect.InvocationTargetException

Hi all,
Please, I need your help with this issue. I installed Work Manager 6.1 over SMP 3.0.3.
I added a field to complex table ctCatalogGroup. The field was already contemplated on the backend so I only had to add it in Agentry. It worked fine for a while but suddenly it started giving me this error during transmit every time since then:
My Java class looks like this:
And I added the field in Agentry accordingly:
Config Panel parameters for this are:
The first thing I noticed is this error in the SMP log:
2015/04/23 08:29:12.540: + WorkFunction=00000001496AF658
2015/04/23 08:29:12.540: + User=invpos_out30
2015/04/23 08:29:12.540: + Server=Agentry
2015/04/23 08:29:12.540: + Complex Table=ctcatalogprofile
2015/04/23 08:29:12.540: Update BHT 'ctcatalogprofile' for 'User': Client last data update 12:00:01 a.m. 01/01/1900
2015/04/23 08:29:12.540: Update BHT 'ctcatalogprofile' for 'User': Getting back end connections
2015/04/23 08:29:12.540: client last data update=12:00:01 a.m. 01/01/1900
2015/04/23 08:29:12.540: Backend step is configured as a Java Class; using Java class com.syclo.sap.ComplexTable
2015/04/23 08:29:12.540: Using Java Class com.syclo.sap.ComplexTable for ComplexTable
2015/04/23 08:29:12.555: + BackEnd=Java-SAPJavaConnection
2015/04/23 08:29:12.555: Exception while starting complex table update for table 'ctcatalogprofile': JavaBackEndError: JAVA EXCEPTION CAUGHT: java.lang.reflect.InvocationTargetException in AgentryComplexTableFactory::createComplexTable at AgentryComplexTableFactory.cpp:129
As well as this other one in the events.log:
04/23/2015 08:23:32, 0, 20, 16, Thr 9240, Threads in thread pool 'Runtime' expanded to 2. Adding thread 3580
04/23/2015 08:25:13, 1, 29, 1, Thr 3580, java/net/SocketException, java.net.SocketException: Connection reset by peer: socket write errorAngelJavaStreamsConnection.cpp#189:AngelJavaStreamsConnection::handleException
04/23/2015 08:25:13, 1, 4,3221225477, Thr 3580, EXCEPTION_ACCESS_VIOLATION, 000000018000DE02, 0, R, 0000000000000000, ..\agentry\threadManager.cpp#354:ThreadManager::WorkerThread::function
04/23/2015 08:25:27, 0, 0, 6, Thr 7572, invpos_out30: relogin failed at ANGEL: B4A91958-A9A4-46F8-B323-20C61E7E76E8; attempt from ANGEL: 97E1F7AF-4E38-4ECB-8D3C-2E2D4AFEA2AE
04/23/2015 08:25:56, 0, 0, 6, Thr 7572, invpos_out30: relogin failed at ANGEL: B4A91958-A9A4-46F8-B323-20C61E7E76E8; attempt from ANGEL: 15FAC37B-A017-46AB-B528-B2B4610423CC
04/23/2015 08:26:27, 0, 0, 6, Thr 7572, invpos_out30: relogin failed at ANGEL: B4A91958-A9A4-46F8-B323-20C61E7E76E8; attempt from ANGEL: BFDB1CBE-12D9-4A66-8EBA-A855B2B90D23
04/23/2015 08:29:12, 1, 20, 18, Thr 3580, JAVA EXCEPTION CAUGHT: java.lang.reflect.InvocationTargetException
I would like to know if anyone faced something like this before or any suggestions on how to dig deeper for a solution. What confuses me is that it worked ok at first and now I can no longer start the client. That is as far as I can get.
Best regards!
Leonardo.

Hi,
Can you modify the step
public void setProperties(Table tbl) throws Exception {
        super.setProperties(tbl);
        setShortText(tbl.getString("KURZTEXT")).trim());
to
public void setProperties(Table tbl) throws Exception {
        super.setProperties(tbl);
        setShortText(tbl.getString("KURZTEXT"));
Thanks & Regards,
Sravanthi

Work Manager 6.1: Uploading pictures or documents error

Hi,
I'm working with SMP 3.0 and Work Manager 6.1 for Android platform
I'm trying to attach a picture and/or a document to a Work Order and to a Notification, but when I start the transmit the following error is displayed in the client:
Sending Document Link Picture Add For Work Order...
Unexpected disconnection from server (11)
'Angel' connection failed
I tried to debug the Java but it didn't reach any break point or "catch", I also checked the SMP 3.0 Agentry logs and there is nothing.
I went through the installation notes and documents and I haven't been able to find out if I missed some configuration. I also checked this nice blog http://scn.sap.com/community/mobile/blog/2014/03/25/troubleshooting-sap-work-manager-60-attach-document-issue with no luck.
Can you help me with this?
Thank you in advance
Tags edited by: Michael Appleby

Short update for this issue. I created a SAP incident regarding it.
It's only failing when attaching pictures in Android (iOS works fine), and it seems due a platform bug documented here: http://code.google.com/p/android/issues/detail?id=17535
But since WM 6.1 is supported for Android 4.0 or higher, I expect some help from SAP if the cause is what I think.

SAP Work Manager status STOPPED in SCC

Hi All,
We have installed and deployed SAP Work Manager 6.0 on SMP 2.3. In the SCC it shows the app was registered or started successfully, however the Agentry instance server status is STOPPED. The Task Manager shows the Agentry Server is running, and can actually accessed from ATE.
The problem is we can't see anything in any of the other tabs. The tab Configurations is blank and we are not able to see or maintain any settings and/or parameters. The other tabs are also blank, for example Logs is not pulling in the data from the log files. See screenshots below.
The startup.log is also noit giving me any indications or errors. See also below.
Any suggestions as to what might be wrong? And how this can be resolved?
Kind regards,
Edwin
STARTUP.LOG
09:16:47 03/27/2014: Starting server (64-bit Windows)
09:16:48 03/27/2014: Administration client command port is 60880, status port is 60881
09:16:48 03/27/2014: Looking for initial status connection...
09:16:58 03/27/2014: Event: 0, 2, Status connection not detected. Continuing startup
09:16:58 03/27/2014: Reading system ini file.
09:16:58 03/27/2014: ID: SAP Work Manager Server v6.0.0.0, Name: ???, Location: ???
09:16:58 03/27/2014: Starting log file.
09:16:58 03/27/2014: Loading message groups.
09:16:58 03/27/2014: Starting threads.
09:16:58 03/27/2014:    1 initial threads. Threads will auto-scale.
09:16:58 03/27/2014: Starting Server: Agentry v6.1.3.10212
09:16:58 03/27/2014: Event: 0, 2, System Startup
09:16:58 03/27/2014: Loading 1 front ends
09:16:58 03/27/2014: Loading front end from angelvine.dll
09:16:58 03/27/2014: ANGEL Front End: reading init files.
09:16:58 03/27/2014: Event: 17, 14, ANGEL Front End v6.1.3.10212
09:16:58 03/27/2014: Event: 0, 2, Loading the Agentry Server's public/private key for password exchanges.
09:16:58 03/27/2014: Event: 0, 2, Key pair loaded successfully.
09:16:58 03/27/2014: Starting Server Agent.
09:16:58 03/27/2014: Agentry: Starting threads.
09:16:58 03/27/2014:    1 initial threads. Threads will auto-scale.
09:16:58 03/27/2014: Agentry: Adding messages.
09:16:58 03/27/2014: Event: 1, 4, Agentry v6.1.3.10212
09:16:58 03/27/2014: Loading 1 agents
09:16:58 03/27/2014: Loading agent from ag3.dll
09:16:59 03/27/2014: Starting Server
09:16:59 03/27/2014: Server: reading ini file
09:17:00 03/27/2014: Initializing 2-HTTPXML from ag3httpxmlbe.dll
09:17:00 03/27/2014: SystemConnection-2: Reading configuration information.
09:17:00 03/27/2014: SystemConnection-2: Setting name to 'HTTP-XML Back End'.
09:17:00 03/27/2014: HTTP-XML Back End: Initialized.
09:17:00 03/27/2014: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v6.1.3.10212) from ag3httpxmlbe.dll
09:17:00 03/27/2014: Initializing 1-Java from ag3javabe.dll
09:17:00 03/27/2014: SystemConnection-1: Reading configuration information.
09:17:00 03/27/2014: SystemConnection-1: Setting name to 'Java Back End'.
09:17:00 03/27/2014: Java Back End: Initialized.
09:17:02 03/27/2014: Java Back End: Java Virtual Machine loaded.
09:17:07 03/27/2014: Java Back End: Java Back End AJAPI version 5.0, release 6.1.3.10200
09:17:07 03/27/2014: Event: 23, 101, Java Back End: AJAPI JAR version 6.1.3.10200 does not match the version of the Agentry Server
09:17:07 03/27/2014: Java Back End: Initialized.
09:17:07 03/27/2014: Event: 23, 4, Loaded Java Back End (Java v6.1.3.10212 (JVM version 1.6.0_35, AJAPI version 5.0 build 6.1.3.10200)) from ag3javabe.dll
09:17:07 03/27/2014: Event: 20, 150, Loading Production application definitions using file "SAPWM-v1-0-0-app"
09:17:07 03/27/2014: Event: 20, 152, Loading Production application definitions for default localization
09:17:18 03/27/2014: Event: 20, 153, Finished loading Production application definitions for default localization
09:17:18 03/27/2014: Event: 20, 151, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"
09:17:18 03/27/2014: HTTP-XML Back End Back End: Started
09:17:18 03/27/2014: Server: Starting threads.
09:17:18 03/27/2014:    1 initial threads. Threads will auto-scale.
09:17:19 03/27/2014: Event: 20, 4, Server v6.1.3.10212
09:17:19 03/27/2014: Starting front ends
09:17:19 03/27/2014: ANGEL Front End: Starting threads.
09:17:19 03/27/2014:    3 initial threads. Threads will auto-scale.
09:17:19 03/27/2014: ANGEL Front End: opening listen socket on port 7003
09:17:19 03/27/2014: Event: 17, 10, 0.0.0.0:7003 open
09:17:19 03/27/2014: Event: 17, 10, ANGEL Front End v6.1.3.10212
09:17:19 03/27/2014: Event: 0, 0, Old log files moved into E:\SAP\MobilePlatform\Servers\UnwiredServer\logs\com.sap.wm\Rolled\2014-03-27-091647
09:17:19 03/27/2014: Event: 0, 23, SAP Mobile Platform
09:17:19 03/27/2014: Event: 0, 2, Server startup is complete.
09:17:19 03/27/2014: Agentry Application startup complete

Hi Stephen,
We installed SP04, but we are still experiencing the same issue. We even went as far as deleting and re-deploying the app.
Again it shows the app registered successfully:
On the General tab it still shows status STOPPED:
The other tabs don't show anything, e.g. Configurations or Logs:
After restarting SMP the node completely disappears:
The Region & Language settings on the SMP server:
Any further suggestions are much appreciated.
Regards,
Edwin

Work Manager 6.0

Hi All,
We are implementing the SAP Work Manager 6.0 for one of our clients.The device on which the application to be deployed is Windows Screen Size
(1024 * 768 ).The server is up and running and when I try to test the application on ATE by selecting the platform Windows 1024*768,The application is not looking as it is expected to be.
From my investigation I found that the SAP Work Manager 6.0 has no platforms and screens for Windows 1024*768.
I could see platforms as Ipads, Iphones for most of the screensets and PPC for some of the screensets.
So to deploy SAP Work Manager 6.0, do I need to create all the screen sets for Windows and Android Devices?
One solution which I could find was that I added platform as Windows 1024*768 and added the same Ipad screen and it was working fine for some of the screens .
Please help me find a solution .
Regards,
Deepak.M
Tags edited by: Michael Appleby

Deepak,
At this point I would highly recommend implementing Work Manager 6.1 instead of 6.0. As you noticed with Work Manager 6.x the Windows platforms were removed as Work Manager is now using the WPF client for the Windows (Win 7/8) devices.
The advantage of this is that iPad, Android tablets, and WPF all use the same screens from the application definitions. There are style/image differences that help control the look and feel on the different platforms.
Also in Work Manager 6.1 the did make changes to better support lower resolution Windows devices which would also be a reason to upgrade.
Either way the ATE will not render the screens well for the WPF stuff. You should test screen layouts and looks by using the actual clients (WPF, Andorid, iOS) and rely on the ATE to confirm Object data, CT/DT data and some rule/action debugging.
--Bill

Work Manager Installation Problem

Hi Experts,
I'm currently installing PCM Version 7.5 on Windows 2008 R2 with MS SQL Server 2008.
This installation is for a demonstration system, and has all components (database, Application Server, Web Server, etc) installed on one host.
The database has installed successfully and the Msschema script has also ran successfully.
I have been able to install the Primary Application server successfully too.
I am having some difficulty with installing the Work Manager, as follows:
In the Work Manager Options screen (for reference, page 39, point 14 to 18 of the installation guide), I have entered the details as requested by the installation guide.
I have checked that the account entered is the correct administrators account and password (logged on to OS using them), I have checked that the SMTP server and port are correct and have provided the correct path for temporary storage.
The error message that I receive when selecting next is:
Invalid Workflow User - Unable to Login
Invalid Username or Password
When referring back to the guide, the entry (point 14) is:
In the "Work Manager Options" screen, enter an Administrator user name and password in the User
Name and Password text boxes.
I can't account for why this is not working - it is a current administrator account that I am using and the guide asks me to enter it.
Has anyone had this issue before, what did you do to overcome it?
Thanks and regards,
Chris

First time configuration requires use of PCM administrator account. The username and password are administrator (lower case). Afterwards you can log into PCM Model Builder and change the credentials.
Thanks and best regards,
[Jeffrey Holdeman|http://wiki.sdn.sap.com/wiki/display/profile/Jeffrey+Holdeman]
SAP Labs, LLC
BusinessObjects Division
Americas Customer Solutions Adoption (CSA) team

Work Manager 6.0 for SMP 2.3 - standalone server - Startup Exceptions

Similar Messages

Maybe you are looking for