LabVIEW 2013 SP1 Compile Worker Fails

Hello,
after receiving the new DVDs with LabVIEW 2013 SP1 and successfull installation, I wanted to compile my FPGA.vi.
The Compile Worker does not start an I get the attached error Message. The additional Download of Xilinx Compilation tools 14.4 from the NI Website does not help.
When I choose the FPGA Compilation Tools via the Start menu, the Compile Worker does not start. When I try to start the FPGACompileServerConfiguration an Error occurs (see picture).
At the Moment I hav not Idea what to do. Perhaps someone can help.
What does I have to do to convert my system back to the Version 2013?
Attachments:
FehlermeldungCompileWorker.jpg ‏41 KB
ErrorwhenstartingFPGACompileServerConfiguration.jpg ‏15 KB

dfschunk,
Thanks for your post. We are aware of an issue with the compile tools installed from the 2014 developer suite (2013 sp1) where the compile worker is installed with missing dependencies. We are taking immediate action to push out a fix for this and you will receive a notification through NI update service when the fix is available.
In the meantime, our recommendation is to downgrade to the 2013 installation of the Xilinx tools. No fixes were made between 2013 and 2013 sp1 in the compile worker or in the Xilinx tools so no worries there.
Go to Control Panel >> Programs and Features and select National Instruments Software.
This will launch a window where you have the option to select various NI software products and modify/repair/remove them.
Select NI LabVIEW FPGA Xilinx 14.4 Tools and select Remove.
After the software has been un-installed, go to the NI LabVIEW 2013 FPGA Module Xilinx Tools 14.4 donwloads page and install this version of the tools (released with 2013) or you may install the tools from your original LabVIEW 2013 developer suite disks.
Please post back or call support if you have any problems with this process, we want to make sure you are up and running until we push out a fix.
Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

Similar Messages

Como instalar Labview 2013 SP1 si tengo instalado Labview 2013

Buenos Días,
tengo Instalado Labview 2013 y quisiera saber si tengo que desinstalarlo para instalar labview 2013 SP1
Espero sus respuestas
Gracias!
Solved!
Go to Solution.

* Yo no hablo español. He utilizado Google Traductor.
No. Usted debe ser capaz de instalar LabVIEW 2013 SP1 en la parte superior de la original de LabVIEW 2013. No debería haber necesidad de desinstalar. Sólo asegúrese de que usted tiene el Programa de Servicio Estándar (SSP). LabVIEW 2013 Service Pack 1 es una actualización exclusiva para LabVIEW 2013 para el Programa de Servicio Estándar (SSP) a los clientes.
descargar
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
*I do not speak Spanish. I used Google Translator.
No. You should be able to install LabVIEW 2013 SP1 on top of the original LabVIEW 2013. There should not be a need to uninstall. Just make sure you have NI Standard Service Program (SSP). LabVIEW 2013 Service Pack 1 is an exclusive update to LabVIEW 2013 for NI Standard Service Program (SSP) customers.
Download
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If someone helped you out, please select their post as the solution and/or give them Kudos!

Exchange 2013 SP1 readiness check failing

Trying to install our first Exchange 2013 SP1 server on Windows 2012 R2 in our datacentre, the readiness check fails with:
Error:
The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
There are many more errors relating to Enterprise admin rights etc.
Please note that:
My account is Domain admin, Schema admin and Enterprise admin member, it always has been.
I tried the built-in AD Administrator which of course is part of the groups as well, no difference.
Active Directory is at 2008 R2 for domain and forest functional levels.
I tried rejoining the new Exchange designated server to the domain
I've installed RSAT-ADDS, the Managed API 4.0 and all the other windows roles via powershell
There is a local domain controller that is a global catalog server on the new Exchange server subnet
I tried running the Exchange Setup on a different server on the same subnet as where the active 2010 Exchange server resides as well as the FSMO AD role holder resides, this works fine. I even did the AD prep from there no problem, that made no difference
on the datacentre server
AD replicates fine between the FSMO role holder and the Datacentre (no errors in dcdiag or repadmin /showrepl)
This error is in the event log:
The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ExSetupUI.exe
6724
Get Servers for domain.local
TopologyClientTcpEndpoint (localhost)
3
System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0475315. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.ICommunicationObject.Open()
at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Boolean useCache)
at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
the message resource is present but the message is not found in the string/message table

So I decided to re-install the OS, worked perfectly now. Only difference from before would be:
SCCM hasn't pushed SCEP 2012 to the new build of the same server yet
The original server was installed in a different AD site and then it was physically mode and reassigned to an new AD site and subnet
I might have installed the pre-reqs in a slightly different order (RSAT-ADDS, all the IIS etc things via powershell
and then the UCM API 4.0. (saw few comments that the order of how you install them matters in other forums).
10 or so Microsoft Windows updates haven't installed on the new OS build yet.
Other than that, its identical. But if its not broken don't fix it, perhaps the above can help someone else though.

Exchange 2013 SP1: Fix for failing MSExchangeTransport service

We had a newly updated Exchange 2013 SP1 that would not start the Transport service
"Netstat -b" showed that a service was listening to port 25 on all IP's (0.0.0.0:25) and when the service could not get the port, it would die, and Exchange would attempt to restart it over and over.
After many tears, I found this solution:
Through the console or the ECP, check the Frontend receive connectors and find the one that is listening on 0.0.0.0:25, which is probably the Default Frontend Receive. Disable it.
Restart the MSExchangeTransport and MSExchangeTransportFrontEnd services.
If both services restart normally, troubleshooting is complete.
We use several custom connectors carried forward from the previous installation, which was SBS 2008. If this applies to you, take notice.

Normally, the Default Frontend Receive Connector (0.0.0.0:25) is the messaging entry point for your organization (I am assuming that you have a single MBX/CAS server).
1. If you disable the Default Frontend Receive Connector (0.0.0.0:25), you block inbound email.
2. Most probably, the cause for your problem are the Custom Receive Connectors. Check their type, and if it is Hub Transport, delete and re-create them as Front End Receive connectors.
Step by Step Screencasts and Video Tutorials

LabVIEW 2013 SP1 Quit LabVIEW

Hello all,
I have a question regarding the Bug 425800 (Quit LabVIEW will not quit if the event 'Application Instance close' is present) in LV2013. According to NI this Bug is fixed in LV2013 SP1.
I have an application, which was converted from LV2011. The application compiled in LV2011 worked well.
After converting to LV2013 I had the issue, that the exe won't quit. I updated to LV2013 SP1 and mass compiled my project. After building the executable again, I have the same issue. My compiled EXE (LV2013 SP1) will not quit.
One VI contain the 'Application Instance close' event, because the PC is connected to an UPS and the application should be terminated in a save way in case of power loss.
Is there any other reason why the 'Quit LabVIEW' will not work?
As a little reminder: The application worked well in LV2011.
Regards
Heinrich Eidloth

Dear Mr Eidloth,
I would like to help you resolve this issue.
Would you mind sending me your program to look into so I can help you better?
Alternatively you could try running the added example to test the functionality of the "Application Instance close" Event and the "Quit LabView" funktion.
Thank you very much in advance.
Best Regards
Veronika Kurz
Veronika Kurz
National Instruments
Applications Engineering
www.ni.com/support
Attachments:
Quit LabVIEW CAR-1.vi ‏10 KB

Exchange 2013 SP1 server working for several months now messages are getting stuck in drafts folder

This a small, simple environment. There is a MS Server 2012 R2 server hypervisor with a MS Server 2012 R2 VM running Exchange 2013 patched to SP1. This server has been deployed into production and passing mail without issues for several months.
Upon initial deployment, we experienced the issue that many have reported and that has been widely documented where Mail Flow works fine inbound, but outbound will stick in the drafts folder. We resolved the issue by manually configuring the IP Address of
our internal DNS server (which is an installed role on our hypervisior / base layer server). The issue was immediately resolved and mail was flowing in both directions without issue. We later installed SP1 and there was no issue. Mail has
been flowing normally all the while.
Now fast-forward through several weeks of reliable mail delivery... We experienced a power loss and a system shutdown and upon reboot, inbound is working and outbound goes to drafts. I've confirmed DNS Lookup settings in ECP still points to our internal
server as previously configured. Both servers have internet access, NSLOOKUP returns expected values, and DNS appears to be working normally.
I'm not sure if we had an MS Update that installed with the reboot that caused the breakage, if there was a lingering settings change that took effect on reboot, or what is causing the interruption. I'm looking for some fresh ideas on where to look
for answers, and all the information available on the drafts folder issue points to DNS settings that have already been put in place.
Any constructive ideas are welcome! Thanks in advance.
David

Amit,
Long story short, I'm not sure how or why, but there were a few automatic services that were not starting "automatically." I'm used to seeing some services that are triggered by the application to start and stop on their own, so I didn't necessarily
panic when there were a few automatic services that were stopped..
However, The MS Exchange Health Manager, and the Mailbox Submission services weren't running. After manually starting the services my drafts folder emptied and we are back in business.. Maybe not "innovative" as you said, but it certainly put us on
the right track. We were looking so hard at DNS because of all the reported cases of "stuck in drafts" being related to DNS, we totally overlooked the obvious, so THANKS!
Now the only question is, what stopped the services and why did they not restart automatically??

Exchange Server 2013 SP1 Standard: Installation failing can't progress

I'm trying to install Exchange Server 2013 and I keep getting this error and I am unable to progress, I can't find any support on the issue and frankly I don't want to/can't afford to spend $500 to ask Microsoft for technical support (what kind of racket
do they think they're running?).
The error message:
Error:
The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
Yet, I see no PushNotifications virtual directory or anything remotely related to that on IIS or in the inetpub folders and files. If I try to resume the set-up after this error I get:
Error:
The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The AD configuration for virtual directory 'PushNotifications' already exists in 'CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local', please remove this AD configuration manually.
Parameter name: VirtualDirectoryName".
And I have to remove this config using ADSI Edit, which just returns me to the first error.

1. Prodution
2. Just 1 DC for 1 site.
3. Setup.EXE
4. Matches SP1 version numbers
5. That's just what was made available to me via MSPP, the installer doesn't see any updates?
6. Here is the log files:
[03/23/2015 22:06:52.0940] [1] Setup failed previously while performing the action Install. Looking for the failed task with ID ClientAccessComponent___75f8c93d15314369983d33ec0742e189.
[03/23/2015 22:06:52.0941] [1] 131 tasks were found to run.
[03/23/2015 22:06:52.0941] [1] Processing component 'Client Access Configuration' (Configuring Mailbox role: Client Access service.).
[03/23/2015 22:06:52.0941] [1] Executing:
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
[03/23/2015 22:06:52.0955] [2] Active Directory session settings for 'New-PushNotificationsVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'SVR01.OFFICE.local', Preferred Global Catalog: 'SVR01.OFFICE.local', Preferred Domain Controllers: '{ SVR01.OFFICE.local }'
[03/23/2015 22:06:52.0956] [2] User specified parameters: -Role:'Mailbox' -DomainController:'SVR01.OFFICE.local'
[03/23/2015 22:06:52.0956] [2] Beginning processing New-PushNotificationsVirtualDirectory
[03/23/2015 22:06:52.0999] [2] Searching objects "SVR02.OFFICE.local" of type "Server" under the root "$null".
[03/23/2015 22:06:53.0066] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
[03/23/2015 22:06:53.0068] [2] Processing object "SVR02\PushNotifications".
[03/23/2015 22:06:56.0763] [2] The properties changed on the object '' (CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local) are: "{ MetabasePath[msExchMetabasePath]='IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications', AuthenticationMethodFlags[msExchInternalAuthenticationMethods]='Ntlm, WindowsIntegrated', AuthenticationMethodFlags[msExchExternalAuthenticationMethods]='Ntlm, WindowsIntegrated', Id[distinguishedName]='SVR02\PushNotifications (Exchange Back End)', InternalAuthenticationMethods[msExchInternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, ExternalAuthenticationMethods[msExchExternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, OrganizationId[msExchOURoot, msExchCU]='' }".
[03/23/2015 22:06:56.0764] [2] Saving object "SVR02\PushNotifications (Exchange Back End)" of type "ADPushNotificationsVirtualDirectory" and state "New".
[03/23/2015 22:06:57.0073] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
[03/23/2015 22:06:57.0587] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:57.0591] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0378] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0378] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0386] [2] Ending processing New-PushNotificationsVirtualDirectory
[03/23/2015 22:06:58.0388] [1] The following 1 error(s) occurred during task execution:
[03/23/2015 22:06:58.0388] [1] 0. ErrorRecord: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0389] [1] 0. ErrorRecord: System.InvalidOperationException: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it. ---> System.Runtime.InteropServices.COMException: Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
at Microsoft.Web.Administration.Interop.IAppHostAdminManager.GetAdminSection(String bstrSectionName, String bstrPath)
at Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String locationPath)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, String moduleName, String moduleType, ExchangeVirtualDirectory advdir)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetLiveIdBasicAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, ADExchangeServiceVirtualDirectory advdir)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServiceVirtualDirectory`1.InternalProcessComplete()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewPushNotificationsVirtualDirectory.InternalProcessComplete()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
--- End of inner exception stack trace ---
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[03/23/2015 22:06:58.0389] [1] [ERROR] The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
[03/23/2015 22:06:58.0389] [1] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0389] [1] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0390] [1] [ERROR-REFERENCE] Id=ClientAccessComponent___75f8c93d15314369983d33ec0742e189 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[03/23/2015 22:06:58.0390] [1] Setup is stopping now because of one or more critical errors.
[03/23/2015 22:06:58.0390] [1] Finished executing component tasks.
[03/23/2015 22:06:58.0406] [1] Ending processing Install-ClientAccessRole
It says it can not log on with the supplied details, but the account is an Administrator account with full privileges so I can't see why this would be the case.

LabVIEW 2013 Web Service works on debug server but not on application server

I have made a LabVIEW web service, that needs to get 2 inputs from the user through html request, and one input from a running VI. For this communication I have used a notifier to transfer data between the VI and the webservice method. This works perfectly fine on the debug server, but doesn't work when I deploy the web service on the Application Web Server. As shown in the attached snippets, I use a FGV to transfer the reference of the Notifier from the VI to the web service method. This is the same method that is described in this link.
Is this method correct? Or am I missing something?
Chinmay Anand Misra
CLD
Technical Marketing Engineer
NI IndRA

I can't find the right link but....
There is something I ran across a while ago about how to enable the correct server port in you application. The VI Server debug port gets enabled with debugging enabled but, you need to specify your services port in the <MyApp>.ini file.
I'll sit back and watch the masters now
Jeff

Exchange Server 2013 SP1 - Readiness Check Failing - Detected Non-existent Exchange 2007 Servers

For development purposes, I needed to install Exchange Server 2013 in our environment. Our current environment includes a couple Domain Controllers, a Sharepoint Server, and a SQL Server. So, it's got a very simple topology. The one thing
our environment does NOT have are current Exchange servers.
During the "Prerequisite Analysis" phase of the install it complained that two servers, that I can find nowhere in our active directory domain, are running Exchange 2007. Obviously, this presents some unique problems. Perhaps as a test
many years ago, someone installed Exchange 2007 to "play" with, but we've never run Exchange for any length of time.
So, this is quite the conundrum, given the above does anyone have any suggestions as to a potential solution? Ideally, I'd like to be able to "lift the covers" and cleanup the references to the non-existent servers somehow, but ANY suggestions
for fixes are MUCH appreciated.
Cheers,
Nate

Here is the thing I would do (Only if I am not going to have any exchange 2007 ever in the environment).
On any of windows server 2008 download
Exchange 2010 SP3
Extract the file and run the below command:
Setup.com /ps
This will make Exchange 2013 install. Also Deleting Exchange Administrator Group wouldn't help as Setup will look for the information about schema into AD.
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.

Lync integration not working after Exchange 2013 SP1 is installed...

Hi,
I have two Exchange 2013 servers running and everything is fine, almost.
The problem is that on the first server we had OWA with Lync integration working before installing SP1, but after the installation of SP1, it doesn't Work any more.
The second server was installed with SP1 from the start, but we can't get the Lync integration to Work on this one either..
When we log in to OWA, it just starts to sign in but then says "there was a problem signing in, if this continues please contact your helpdesk"
I have checked the Exchange server for events, and i can see the event ID 112 everytime i recycle the Application Pool, so there are some connection between Exchange and Lync..
Have any of you Guys seen or experienced any thing like this?
Thanks in advance.
Regards
Kenneth

Hi,
I recommend that you refer to the following article to troubleshoot the issue:
Troubleshooting tips for Exchange 2013 OWA IM Integration to Lync 2013
This post describes how to configure Exchange 2013 OWA to have IM integration to Lync 2013. Here I would like to give some troubleshooting tips in case you can't get the integration to work.
In addition, here is a similar thread for your reference:
Lync 2013 with Exchange 2013 SP1 OWA integration failed
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 SP1 and CUCM 9.1.2 - Exch not recognizing called extension

I think I'm almost there in getting Exchange 2013 SP1 UM working with CUCM 9.1.2...I've got two issues at the moment that I need a little help with.
1) When I dial my VM pilot (6040) from a UM enabled extension it prompts to enter an extension. When I dial the same extension and let it ring to VM, Exchange picks up and says "the person you are trying to reach does not have a valid voice mail box
on our system".
2) This just started happening this afternoon, when I dial my VM pilot (6040) exch3 picks up as thats what I have my route pattern pointing to. If I enter the extension of a mailbox on exch2, I get stuck in a endless loop.
I've followed this post as a guide but it hasn't resolved my issue.
https://supportforums.cisco.com/discussion/11914031/exchange-2013-um-and-cucm-86
My Exchange environment looks like this:
Site 1:
exch1 - CAS/Mailbox, used for mainly utility type work, journal, dedicated SMTP flows etc
exch2 - CAS/Mailbox, part DAG13
exch3 - CAS/Mailbox, part of DAG13
Site 2:
exch2dr - CAS/Mailbox, part of DAG13
exch3dr - CAS/Mailbox, part of DAG13
DAG13 is stretched between two sites, there are no users at our DR site so CUCM is pointing to Site 1 for UM. Each site has an internet facing CAS-only server for OWA/EAS etc.
Any help is greatly appreciated. I'd love to get rid of Unity.
EDIT:
I just found this event in the event logs:
The Microsoft Exchange Unified Messaging service on the Mailbox server received a diverted call with ID "d51600-3a3140c5-9b8-c1414ac@EXCH3-IPADDR" for extension "4099" on UM dial plan "CUCM" from UM IP gateway "CUCM IP",
but no UM-enabled mailbox for the corresponding extension could be found. Please check the extension and make sure that the corresponding mailbox is enabled for UM and associated with the correct UM dial plan.

9.1.2 I think it is, we upgraded to avoid the known DNS bug
I cant see how to PM you either
The crux of it was outlined below with some tweaks
http://blogs.technet.com/b/canitpro/archive/2014/04/30/step-by-step-integration-between-exchange-2013-um-and-cisco-unified-communication-manager.aspx
As we have multiple combined role servers, our trunks are set up as follows:
1. 1 x CAS Trunk - contains all CAS Servers on port 5060
2. 4 x MBX Trunks - contains Maibox Server with ports 5062-5068
On top of that, we had to Allow "Redirecting Diversion Header Delivery - Inbound (and Outbound)" on the CAS Trunk but DISABLE it on the Mailbox Trunks
Also, make sure that you are using Telephone Extension Dial plans in Exchange 2013 (Despite them being unable to be associated with a 13 Server - EX13 answers for all calls anyway)
Lastly, the MS documentation is a little strange - it says that as your last step of UM migration, you should point your Call Manager to 2013 - I don't agree with that statement, EX13 routes calls back to 2010 UM Servers perfectly fine, so treat it the same
as any other CAS based service - point to 2013, and it will handle the rest

LabVIEW 2013 Patch f2 update problem

I have installed LV 2013 (13.0.1f1) Patch f1 (32-bit). I tried to install NI LabVIEW 2013 f2 Update but I got error message: "NI LabVIEW 2013 must be installed before you can install this update."
So, why it doesn't recognize installed app?
BR,
Jick

There is a difference between
LabVIEW 2013 f2-Patch and
LabVIEW 2013 SP1 f2-Patch
Choose the right one.

Cannot Adding Mailbox Server for Database Copy for Exchange 2013 SP1

Before I upgraded to 2013 SP1 everything works find but after I upgrade to SP1 I cannot add database copy. the details are...
I have 2 sites
Site 1 : 4 Mailboxes (Mailbox01,Mailbox02,Mailbox03,Mailbox04)   + 2 CAS
Site 2 : 2 Mailboxes (Mailbox05,Mailbox06)   + 2 CAS (just for standby site)
So I have 2 DAG group  (6 Mailboxes separate to 3 Mailboxes for 1 DAG group Mailbox01,Mailbox02,Mailbox05 for DAG1 and Mailbox03,Mailbox04,Mailbox06 for DAG2)
After I upgrade Exchange 2013 to SP1 , I try to create new database on Mailbox01 and after that I try to add mailbox02 and mailbox05 to database copy of new database that I created.
"Mailbox05 can added to be database copy but Mailbox02 cannot add database copy for it , Error "Network path not found" occur" but Im very sure that path is the same for each mailbox database server.
so I try to create new database on Mailbox 03 and add database copy on mailbox04 and mailbox06.... the result is the same only Mailbox06 can add mailbox copy of database.
It look like I cannot have 2 mailbox in site 1 for database copy of each new database (I already try to create new database on Mailbox 02 and add database copy on mailbox01 and mailbox05 , the result is only mailbox05 can be database copy of database).
Please help me to fix this out.

Hi,
I recommend you check if the Remote Registry service is running on Mailbox01, Mailbox02, Mailbox03 and Mailbox04. If not, please start it and then add mailbox database copy to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Does the license number of labview2013 sp1 32bit fit for lavbiew 2013 sp1 64bit?

I bought a LabVIEW 2013 sp1 32bit full version one month ago. Now I want to use the 64bit LabVIEW 2013. Does the license number I used to active the 32bit software still fit for 64bit LabVIEW?
Solved!
Go to Solution.

Yes.
You always have the option to call NI to discuss all licensing questions…
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

LabVIEW 2013 Fpga will not compile tutorial solutions

Y'all
I am working to get the CRIO evaluation software to compile the tutorial solutions. so far it will not and complains about missing XILINX_EDK (warning.) Attached is the xilinx log. (Do I need to reinstall? or what)
Thanks for help!
Sincerely,
Paul
Attachments:
XilinxLog.txt ‏130 KB

Hi Paul,
What version of LabVIEW (2013/2013 SP1), LabVIEW FPGA and Xilinx Compile Tools do you have (or are you compiling on an external server)?
Which example specifically are you trying to compile? You mentioned tutorials, but I'm not sure exactly what example you are referring to.
Thanks!
Xavier
Applications Engineering Specialist
National Instruments

LabVIEW 2013 SP1 Compile Worker Fails

Similar Messages

Maybe you are looking for