Inconsistency Excel Launch via terminal server

Dear All,
Currently, we are running on BPC NW 10 SP 14 and encounter an error launching Excel via terminal server.
The result is not consistent as sometimes Excel was able to launch.
Step:
Portal -> Terminal -> Portal (SSO) -> BPC Web (via terminal)
Error Message:
Error Launching Office Client: Object reference not set to an instance of an object
There are couple of notes which have been checked and does not seems to help.
https://support.wdf.sap.corp/sap/support/notes/1922019
https://support.wdf.sap.corp/sap/support/notes/1990386
https://support.wdf.sap.corp/sap/support/notes/1922056
https://support.wdf.sap.corp/sap/support/notes/1702693
Please advise if there could be any other possibility that could lead to the inconsistency in launching EPM excel via terminal server.
At the same time, is looking if upgrading the service pack to either SP15/SP16 would help.
Would appreciate if anyone could share some information(known issue,bug) in both service pack.
Thanks in advance.
Regards,
Michael Lim

Hi,
It Might be permission issue.
Try to give rights to folder where reports are kept.
Also give rights to windows\TEMP folder.
Regards,
Shweta

Similar Messages

Outlook via Terminal Server possible ?

Hello,
in the 9i release the Outlook Connector didn't work when outlook was accessed via Terminal Server and no local outlook installation was available.
Did this change with 10g ? Is this now possible ?
It would be important to have this function in order to do Application Service Providing
with OCS.
thanks,
Jochen Zehe

Hi, thanks for response.
Additionally i found the following in the doc:
As of 10g Release 1 (10.1.1), Oracle Connector for Outlook is certified to work with Windows Server 2003 Terminal Services. Terminal Services were conceived to provide organizations with a secure and cost-effective means of hosting Windows desktop sessions on a remote server. Remote users connect to a server through a desktop or Web interface and benefit from the full Windows experience without the overhead of running applications locally. Windows Server 2003 Terminal Services requires greater than normal bandwidth, and you must ensure that all drives are mapped correctly.

Issues with WebDav over SSL via Terminal Server when Accessing SharePoint 2013

Hi All,
We have deployed a terminal server from which multiple users access and heavily use SharePoint 2013 (hosted on a separate server). The SharePoint site is published to the internet and is operating over an SSL certificate. Over the last few months we have
been encountering a randomly occurring issue where all the users become unable to use Open with Explorer or mapped drives to access the site. During this time they can still access the site through the browser OK and download files etc. This issue sometimes
reoccurs every few days, although at points it hasn't occurred for a couple of weeks before resurfacing.
Current Terminal Server Config
TS 2008 R2 Enterprise
Site added to Trusted Sites. (have checked during broken time and still recognized as trusted)
Using IE 11, site added as compatibility view
Registries updated as below
reg add HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters /v AuthForwardServerList /t REG_MULTI_SZ /d "*.clientsite.com"
reg add HKLM\SYSTEM\CurrentControlSet\Services\WebClient\Parameters /v BasicAuthLevel /t REG_DWORD /d 2 /f
reg add HKCU\Software\Microsoft\Office\14.0\Common\Internet /v BasicAuthLevel /t REG_DWORD /d 2 /f
registry added for tabprocgrowth added to 2
My test result are below:
Restarting the SharePoint server or the terminal server will resolve the behaviour
until the issue occurs again.
Users on the terminal server can still open the
ttps://clientsite2.harrierhc.com
URL (this url is bound to the same UCC cert) with open with explorer during this time.
While users are unable to access the ttps://clientsite.harrierhc.com
URL, if they access the same site from WebDAV with a separate binding (e.g. ttp://clientsite the behaviour works fine.
All other users not on the terminal server can still use the open with explorer behaviour during this time.
IIS reset on the SP Server & restarting the web client service on the terminal server have no impact
Reimporting the IIS certs have no impact
There are numerous errors in both server’s event logs but none at the time of the issue instigation.
Clearing the IE cached certificates has no impact
Going to IE properties for the site and clicking the ‘Install Certificate’ has no impact
Any ideas or suggestions would be much appreciated. If you need any more info let me know. (sorry for the ttps:// links cant be posted until my account is verified?
Thanks again

Hiya,
are there any load balancers involved?

Consultas - Exportacion Excel Terminal Server

Amigos tengo otro problema
Mis sucursales que trabajan por medio de Terminal server cuando realzan algun query y lo quieren exportar a Excel, se queda bloqueado, el servidor de Terminal server Tiene 12 GB Ram, el vpn esta por un enlace E1, tengo que reiniciar la aplicacion del usuario desde el servidor y no pueden exportar nada.
Espero su ayuda

Hola Oscar
para que funcione tu exportación a excel, trabajando con Terminal Server, debes tomar en cuenta que donde trabajas es en un servidor que fisicamente se encuentra en otra parte de tu empresa de esa cuenta debes otorgar los permisos necesarios al usuario para que pueda ejacutar la aplicación de excel en el servidor.
Basicamente debe estar instalado excel en el servidor y debes verificar que el usuario con el que trabajas pueda ejecutarlo, recuerda que las sesiones en los servidores son perfiles distintos.
Cuando hayas instalado excel y el usuario pueda hacer uso de el entoces la exportación de SAP se abrirá automaticamente.
Ahora bien tienes otra alternativa, generalmente en conexiones con Terminal Server el disco local, del usuario que se conecta, se puede llevar como unidad lógica al servidor, siendo así, puedes buscar tu disco local en el servidor y grabar ahi la consulta que quieres exportar, posteriormente en el equipo local buscas la carpeta en donde guardaste la consulta y la abres con excel.
Espero te sea de utilidad.
Saludos

Windows Server 2012 and win 8 app on terminal server

On a windows 2012 server, is it possible to install a windows 8 app that can be accessed (via terminal services/remote desktop) by client computers running prior version of Windows, such as 7, Vista and maybe XP? (Obviously without the touch capability).
In other words, can a windows 8 app be accessed via terminal server by other versions of Windows or it must be only Windows 8?
Also, I read that the new RDC can also be downloaded from the Windows Store to a tablet, but what tablet? "Surface" , iPad, Android?
Thanks so much
CBJunior

Hi,
Windows app store is only available on the windows 8 platform.So it is not possible to install a windows 8 app that can be accessed (via terminal services/remote desktop) by client computers running prior version of Windows, such as 7, Vista
and maybe XP.
Also, I read that the new RDC can also be downloaded from the Windows Store to a tablet, but what tablet? "Surface" , iPad, Android?
It is available in the windows app store on Surface which is installed with windows 8 RT.
Regards,
Clarence
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

DCOM error "1260" on Windows 2008 R2 terminal server when SAP exports data into Office 2007 (Excel or Word)

Hi all,
We are experiencing an issue which happens at random whenever a user tries to export data from SAP into Excel or Word. Excel or Word is started but remain empty. We then see the below errors in the event log. And the problem is very random
as sometimes all they have to do is wait 10 minutes and the next try will be successful. Not even log off/on. Could someone tell me what the error "1260" is saying?     thanks for your help.
Pete
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          7/23/2013 4:07:36 PM
Event ID:      10000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Servername.domain.com
Description:
Unable to start a DCOM Server: {00020906-0000-0000-C000-000000000046}. The error:
"1260"
Happened while starting this command:
"C:\Program Files (x86)\Microsoft Office\Office12\WINWORD.EXE" -Embedding
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          7/23/2013 3:54:34 PM
Event ID:      10000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Servername.domain.com
Description:
Unable to start a DCOM Server: {00024500-0000-0000-C000-000000000046}. The error:
"1260"
Happened while starting this command:
"C:\Program Files (x86)\Microsoft Office\Office12\EXCEL.EXE" /automation -Embedding

Hi,
Based on my research, please try the following:
Click Start, click Run, type regedit in the Open box, and then click OK.
Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\termsrv
Under this subkey, add the following registry entries:
Name
Type
Value data
Logoff
REG_SZ
TSEventLogoff
Logon
REG_SZ
TSEventLogon
Restart the Terminal Server computer.
Note: Serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry
before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, please refer to
How to back up and restore the registry in Windows.
Hope this helps.
Best Regards
Jeremy Wu

How to check folder sizes of the root directory on my VPS/Dedicated server via Terminal?

Hi,
I have following issue.
I have a VPS with Linux OS and I'd like to check size of the folders as well as remaining space on my server.
How can I do that via Terminal?
I would appreciate any input.

login into your VPS server via terminal and cd into the root of your hosted space. Then use the df -h command to see the listing
for i.e.
df -h /volumes/volume_1
Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
//john@ds00/volume_1 457Gi 12Gi 445Gi 3% 0 18446744073709551615 0% /Volumes/volume_1
for you it would be something like:
df -h [email protected]/share (ip address)

Outlook 2013 in a 2012 r2 Terminal Server environment and crashes after initial setup. It will not launch in safe mode

I am running terminal server 2012 R2 (RDS environment) In Windows Domain, 8 users across a LAN on a new server. Outlook 2013 crashes and will not load in safe mode. Outlook allows the initial profile setup and when the configuration is complete, it
crashes and will not launch or launch in safe mode. I have deleted the outlook profile and reconfigured it. The problem continues on all user accounts. The firm is not using Exchange and is using a POP3 account. I have a 13 user Office Volume License
(per device) and 15 terminal server Licenses ( per user)
Problem Event Name :      APPCRASH
Application Name:            Outlook.EXE
Application Timestamp :   52b0b282
Fault Module Name :        OUTLOOK.EXE
Fault Module Version :     15.0.4569.1503
Fault Module Timestamp: 52b0b282
Exception Code:                 C0000005
Exception Offset:                00340b9
OS Version:                      6.3.9600.2.0.0.16.7
Local ID :                         1033
Any help would be much appreciated.

follow this instruction to troubleshoot Outlook crash issue:
http://support.microsoft.com/kb/2652320
Flynn

Event ID 7031: DCOM Server Process Launcher service terminated unexpectedly - Causing a Reboot of Server

Hello All,
We recently had a situation where in our Windows Os 2003 SP2 server got rebooted.
Logged and found below event on server:
Event Type:        Error
Event Source:    Service Control Manager
Event Category:                None
Event ID:              7031
Date:                     30/07/2014
Time:                     20:16:28
User:                     N/A
Computer: XXXXXXXXX
Description:
The DCOM Server Process Launcher service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Reboot the machine.
I do not see any other event that could cause the DCOM to fail, not sure that could have been the reason for this.
Any idea?

Hi,
Based on your description, I find following KB in
List of updates in Windows Server 2003 Service Pack 2. It seems to be suitable for current
scenario. Please refer to and check if can help you.
DCOM programs do not work, and event ID 7031 is logged
after you install Windows Server 2003 Service Pack 1 (SP1)
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Address Book write LDAP server command via terminal or remote desktop

Hi folks.
I was wondering if anyone has had any experience issuing an 'address book' setting command, to ADD an LDAP entry, via terminal or remote desktop?
In particular, I want to "ADD" a new "LDAP" entry for a specific server, on 40 workstations, using terminal or remote desktop, so that I don't have to leave my desk
I recall that you can issue commands from the terminal, starting with "write"... to add such preferences.
Any thoughts, ideas, or inspiration?
Many thanks,
Derek

Hi,
As far as I know, We couldn't use Command Shell as you list to establish a Remote Desktop. You can use
mstsc /? command to view all mstsc.exe command parameter. We can use the command
mstsc [<connection file>] to establish a Remote Desktop Connection.
However, why did you want use command shell to establish a Remote Desktop? It would be more convenient using
mstsc [<connection file>] command to establish a Remote Desktop.
If you need further assistance on this particular issue or any other Windows related issue, let us know and we will be glad to assist you.
Roger Lu
TechNet Community Support

Users can only connect to RD farm website and cannot remote into terminal server , when connected via VPN

Hello,
I have a RD farm using 3 Win 2012 servers (1 broker and 2 session host), for internal use only, have not
configured gateway for internet access.
Users are able to connect to RD farm website and remote into terminal server, within office
but can only connect to RD farm website and cannot remote into terminal server , when connected via VPN
Its takes long time at securing connection and fails.
Thanks

Hi,
Thank you for your posting in Windows Server Forum.
First of all I would suggest you to configure RD gateway role on your server and pass all the connection through it because it’s a best practice to use RD Gateway in RDS Farm.
Apart from this, if you are not using RD Gateway then you must check that you have successfully forwarded port 3389 for RDS to access via VPN. Also check that you have made configuration under IIS Manager to enable Forms Authentication. Please check
this link.
In addition, please refer beneath article for additional details.
1. How to Access Windows Remote Desktop Over the Internet
2. Remote Desktop Services in Windows 2008 R2 – Part 3 – RD Web Access & RemoteApp
(For reference)
Hope it helps!
Thanks,
Dharmesh

Can't connect to terminal server via Mac RDC

Users can't log in to our terminal server (Server 2008) from Mac using RDC 2.1. After typing in the server name, the client asks the user to login. The user fills in their username, password and domain but receives and error stating "The credentials
that were used to connect to [server_name} are incorrect".
Any user, including myself who am a Domain Admin, get this error. When I log in using the domain's Administrator account, however, I can log in just fine.
None of this occurs when trying to login from a Windows client. The Mac I tested on is running OS X 10.5.8. Any help would be greatly appreciated. Thanks.

Hi,
For remote desktop in MAC OS, you can try to update the new Remote Desktop Connection. New Multiple Session Support gives Mac users simultaneous access to multiple
Windows-based PCs or to a network server that hosts remote applications and files. Since it is a Universal application, Remote Desktop Connection Client 2 is compatible with the latest technologies on Windows and Mac platforms.
Please refer to the following link:
Microsoft Remote Desktop Connection Client for Mac 2.1.1
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=18140
Setting 'Allow connections from computers running any version of Remote Desktop (less secure)' in the Terminal server to sees if it’s work well.
Technology changes life……

RDP to a Terminal Server via TTPT not working through routers.

I am having problems using RDP to a terminal server through a user home router and DSL connection.
User has a Linksys WRT5G v3 (Firmware 4.21.1) connected to a Cisco 678 DSL Modem.
If I direct connect the home computer to the Cisco DSL Modem everything works fine. When I try to go through the Linksys, I can get the PPTP authenticated but the RDP client just times out.
It would seem like this is a port forwarding issue, but I have tried to use the port forwarding to the IP address of the home computer(statically assigned) by forwarding ports 47, 1723 for the PPTP and port 3389 for RDP.
I have seen the same issue on my home Broadband cable setup with a NetGear Router. Having spent over an hour with the NetGear technical support without resolution. I swapped in a old Linksys Wireless Router BEFW11S4 v4 (firmware 1.52.02) and it fixed the issue.
What is the issue with some home routers letting RDP out? Is there a known model that it will work on?

I believe I have found what my issue is. The older Linksys BEFW11S4 model has a “hard coded” DHCP Server Start IP Address range of 192.168.0.X you can only change the last octet. The newer Linksys WRT5G and WRT54Gs have a “hard coded” DHCP Server Start IP Address range of 192.168.1.X.
Apparently this is their “dumb downed” solution for home routers. They do not allow you to select a different subnet to hand out with DHCP but interestingly they do allow you to fully configure the LAN IP address.
How this affected me is that my target server/network uses the same 192.168.1.X addressing scheme.
I was able to use the newer router by configuring the LAN address to like 192.168.0.200 and turning off the DHCP server. Then I assigned a static IP address to the computer in the home network to something like 192.168.0.250. Then I could successfully use PPTP and RDP to connect to a terminal server.

Office 2007 + Custom template (dot/dotm files) on terminal server -- issues

We are trying to transition to a terminal server + thin-client setup.
The TS runs Server 2008 R2, and the Office version is 2007 (for compatibility reasons -- we have a lot of macros etc that won't run with Office 2010).
The normal.dotm for Office, Excel & Word are customised in order to insert custom macros, font styling etc. A batch file runs on logon, copying the custom normal.dotm files from a network share to the local computer's C: drive in a folder called "Templates".
So it'd copy the data from "\\SERVER1\share\normal.dotm" to "C:\templates\" on the machine.
Then, a GPO would re-direct the location for the normal.dotm file from the default location to the new location (i.e. C:\Templates\) from above. This allowed updating of custom macros etc to all computers on the net. It was messy, but it worked.
Now that we're wanting to transition to terminal server, we're having an issue where the script still works, however when closing Outlook / Excel / Word, users are receiving a message stating "The file normal.dotm is in use".
I'm guessing what's happening is, the first person to log on to the Terminal Server and launch their instance of Outlook/Word/Excel is getting an exclusive handle to this file; And subsequently launched instances get this error.
There is nothing _wrong_ with the system per se -- everything works, however every time an Office app is closed, the user gets the annoying message.
What is the correct solution to this? Is there a cleaner way to deploy macros/styling settings rather than modifying normal.dotm? Another solution I can think of is to create a copy of the templates/normal.dotm for every single user in their %AppData% folder
and tell Office to use the %AppData% copy -- but this would mean as many copies of the templates as there are users which doesn't seem like a very clean solution.
I'm open to suggestions and insights on the cleanest and most efficient way to solve this problem.

Hi
update to this issue from my side:
We opened a Support call for this issue and got it solved.
The SQL script to recreate a fresh Enterprise Global (eglobal.SQL) does not exist for Project Server 2013 currently. But the support created one for us. So if someone has this issue, contact Microsoft Support, they will provide you the script.
Kind regards
Christoph
Christoph Muelder | Senior Consultant, MCTS, MCSE, MCT | SOLVIN information management GmbH, Germany

Acrobat 9 Reader with Windows 2008 Terminal Server

I am setting up a Windows 2008 Terminal Server and i need to have the Adobe Acrobat Reader installed. I downloaded and installed the Vista version and it worked from the console but when i try to access it via a terminal server session the application just crashes. If i try and run it as administrator in the same terminal server session it launches fine.
Any suggestions????
Jason
p.s The associated event log error is:
Log Name:      Application
Source:        Application Error
Date:          7/31/2008 1:17:57 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Comet.invera.com
Description:
Faulting application AcroRd32.exe, version 9.0.0.332, time stamp 0x4850f0a3, faulting module Annots.api, version 9.0.0.332, time stamp 0x4850e57f, exception code 0xc0000005, fault offset 0x001bd9e0, process id 0x1458, application start time 0x01c8f3316002e3b7.
Event Xml:
    1000
    2
    100
    0x80000000000000
    3663
    Application
    Comet.invera.com
    AcroRd32.exe
    9.0.0.332
    4850f0a3
    Annots.api
    9.0.0.332
    4850e57f
    c0000005
    001bd9e0
    1458
    01c8f3316002e3b7

Jason...
Make Certain that you Had the Server In "TS-Install" Mode When you Installed Acrobat. It Is In your Control Panel. I Have Pasted the MS Help File Below.
Install Programs on a Terminal Server
You should install the Terminal Server role service on the computer before you install any programs that you want to make available to users. If you install the Terminal Server role service on a computer that already has programs installed, some of the existing programs may not work correctly in a multiple user environment. Uninstalling and then reinstalling the affected programs may resolve these issues.
To ensure that an application is installed correctly to work in a multiple user environment, you must put the terminal server into a special installation mode before you install the application on the terminal server. This special installation mode ensures that the correct registry entries and .ini files that are needed to support running the application in a multiple user environment are created during the installation process.
You can put a terminal server into this special installation mode by using either of the following:
Install Application on Terminal Server tool under Programs in Control Panel. This tool will run a wizard to help install the application.
Change user /install command at a command prompt. You will have to start the installation of the application manually.
After the application is installed, you must put the terminal server into execution mode before remote users begin using the application. The Install Application on Terminal Server tool will automatically put the terminal server into execution mode when it is finished running. To put the terminal server into execution mode from a command prompt, use the change user /execute command.
Additional considerations
Some programs may require minor setup modifications to run correctly on a terminal server.
If you have programs that are related to each other or have dependencies on each other, you should install the programs on the same terminal server. For example, you should install Microsoft Office as a suite on the same terminal server instead of installing individual Office programs on separate terminal servers.
You should consider installing individual programs on separate terminal servers in the following circumstances:
The program has compatibility issues that may affect other programs.
A single program and the number of associated users may fill server capacity.
For more information about the change user command-line tool, see the Terminal Services Command Reference (http://go.microsoft.com/fwlink/?LinkId=89674).
For more information about deploying programs on a terminal server, see the Terminal Server page on the Windows Server 2008 TechCenter (http://go.microsoft.com/fwlink/?LinkId=79608).

Inconsistency Excel Launch via terminal server

Similar Messages

Maybe you are looking for