PXI-8331 MXI-4 interface connection error

I am using the PXI-8331, PCI-8331 MXI-4 to control chassis PXI-1042. I installed the cards, software and connect chassis to the desktop. MAX window recognizes the chassis but on the chassis status under General tab, a message of "The MXI- connection to this chassis timed out" appears. For this reason, I could not see other modules on the chassis.
How do I solve this problem?
Thanks
Phuc

Hi Phuc,
It looks like there is already a discussion forum discussing the same issue: PXI MXI chassis timeout
Thanks,
Best regards,
Rohan B

Similar Messages

PCI-8331 MXI-4 Interface stops PC from booting

Hello
I’ve recently purchased a NI PCI-8331 MXI-4 Interface card and have installed it in a PC. The PC boots OK and the card and drivers seem to be OK. If I then attach it to a PXI rack, the PC no longer boots. Some details:
PC is a Dell Optiplex380
PC OS is Windows XP Pro v2002 Service Pack 2
I am powering up the PXI rack prior to the PC
The Pw and Lk lights on the PCI card light
I’ve tried the PCI-8331 card in another PC and it seems to work OK and connects to the PXI rack. Both PCs have been configured in a similar manner. Anyone come across this before?
Thanks
Stuart

I have had this issue previously on Dell computers and the MXI-3 interface cards.
If the computer never makes it past the BIOS screens then you have a hardware conflict with something in the PXI chassis and one of the resources on the motherboard of the computer.
1) Power down and remove all PXI cards from the chassis (leave the MXI-4 cards connected at both ends)
2) Reboot and ensure the system will boot.
3) Power down and install the first PXI card.
4) Repeat step 2 and 3 for all cards in the chassis.
I found that when you connect a loaded PXI chassis, the computer seems to have a bit of a mental breakdown and often times fails to boot. Adding the cards one at a time has resolved this issue for me in the past. It is a real pain to continually have to install, boot, shutdown, install boot, shutdown.......
If you find that you can't get the system to boot using this procedure, move the MXI card to another PCI slot within the computer and start adding cards over again. If I recall correctly, moving the card further out on the PCI slots may resolve the issue as it may put the card on the other side of one of PCI bridges on the motherboard.

Error-200284 for PXI-1010 MXI-3 fiberoptic connection to a PXI-6533.

In the instruction lab in which I work, we have two types of systems:
1)SCXI-1000 chassis connected by copper to a PXI-6035E card in a PC.
2)PXI-1010 chassis connected by fiberoptic from a MXI-3 to a PXI-6030E card in a PC. A PXI-6533 handles the digital I/O.
We have LabVIEW8.5.1 running on both types of systems. On the SCXI-1000 system, the LabView example Acq&GraphVoltage-IntClk-DigStart.vi runs just fine. It does not run on the PXI-1010 systems. Instead, I eventually get Error-200284. In both cases we use PFI0 or PFI1, and digital ground, for the triggers, connected to lines 38, 39, and 33, respectively, in the SCXI-1302 terminal block, which connects to an SCXI-1180 feedthrough panel.
I searched the forums and all ni.com for information on this problem, and have not been able to find any relevant information.
Joseph D. Rudmin

Hi Joseph,
I think I'm starting to understand the problem you are having. Unfortunately, since on a SCXI module, all channels are generally multiplexed through AI0, the PXI/SCXI backplane only shares the necessary channels i.e. one AI channel and any required timing signals. Therefore, even if though you are using the SCXI-1180 module with a SCXI-1349 communicating adapter, you will not be able to access the other channels on your PXI-6030E since there is no physical connections being made to those channels in the backplane. There are 2 solutions around this problem:
1. You can use an SCXI-1349 cable assembly to connect the front of the PXI-6030E module to the back of the SCXI-1349 adapter. This way the unused pins on the DAQ module can be accessed through the SCXI-1180.
2. You can decide not to use the SCXI-1180 and simply use a standard 68-pin terminal block with your PXI-6030E and connect your 5V sync pulse to the PFI pins. This will still allow you to sample off of the SCXI-1100 since those channels are connected via the backplane.
Here's a link to our online KnowledgeBase article which talks about this issue.
Can I Connect The SCXI-1180 To An SCXI Module In A PXI-1010 To Use The Additional Analog Input Chann...
Please let me know if this answers your question.
S_Hong
National Instruments
Applications Engineer

PXI 8331 connectivity problems

I am using a PXI 8331 inside of the PXI-1042Q chassis. I have NI-VISA and NI MAX installed. I'm using a serial-to-USB adapter to connect my PC to the MXI card. The 8331 is the only card inside the chassis at the moment. I have no connetivity (link light is not lit). I don't see any MXI devices in device manager and I only see the serial-to-USB adapter (listed as a COM port) in NI MAX under "Devices and Interfaces". Does anyone have any ideas as to what my problem is? This is my first foray in the PXI system, so it could be something obvious, but I've been through every document I can find and I can't seem to find the problem. Thanks in advance.
Brandon

Ah! Something I neglected to mention: after unzipping "nipxips1400" I get the following error and the application looks like this (see included picture). I can click on anyone of the buttons, but then it just closes. I assume it's Win7 compatible (x64), so I'm curious why it's failing. Ever seen this before? Thanks again!
Brandon
Attachments:
error.PNG ‏30 KB

Communicating with modules in PXI-1042 via MXI-3 interface, all I get is PXI0::MEMACC appearing in MAX. I have OEM modules in the chassis, should these be displayed?

I have a PXI-1042 with PXI-MXI-3 interface kit. In the chassis I have inserted an OEM PXI module. When I run MAX, all I see is PXI System->PXI Bus 0->PXI0::MEMACC. Is this correct? How do I see the other modules?

Darren,
The only PXI modules that show up under the PXI System option in MAX are those cards that are registered with NI-PAL or NI-VISA. For 3rd party cards, it depends on how their particular driver functions. If the vendor creates their drivers based on NI-VISA, then the device will show up in MAX.
If the vendor created a Windows-specific driver, then there is no way that NI-VISA can find any information on the device, nor can it communicate with it. An example of this is a CompactPCI SCSI or Ethernet card, which is supported by a driver that is native to Windows. NI-VISA does not detect such devices.
It is important that you contact the manufacturer of your 3rd party modules and find out if they are NI-VISA complient devices.
Regards,
Andrew Mier
au
Applications Engineer
National Instruments

PXI-8320 MXI-2 software/hardware install problems.

Attempting to install a PXI-8320 MXI-2 bridge. My PXI chassis is connected to a PC via a PCI-PXI MXI-3 bridge. I have just received a new PC running Windows XP with Labview 7.1. I cannot find the MXI-2 interface in Measurement Explorer. I do get a find new hardware for the PXI board, but it cannot install a driver. As far as I know, all of the appropriate software was pre-installed. I am stumped. Any help would be appreciated.

Have you installed NI-VXI? The MXI-2 interface requires our VXI driver, NI-VXI, which is not automatically installed with LabVIEW. The latest version is available on our web site at http://www.ni.com/support/vxi/drivers.htm.

RFC connection error (VPN-access)

Hi!
I have the following error for the RFC connection:
The RFC connection is setup as follows.
/H/10.101.7.1/S/3299/H/10.151.6.194
10.101.7.1 = IP of our SAP Router
10.151.6.194 = IP of customer system
The RFC connection is established:
SAP Router (intern) --> Target systems
The error is:
Logon     Connection Error
Error Details     Error when opening an RFC connection
Error Details     ERROR: partner not reached (host 10.151.6.194, service sapgw20)
Error Details     LOCATION: SAP-Gateway on host bksapp01 / sapgw20
Error Details     DETAIL: NiPConnect2
Error Details     CALL: SiPeekPendConn
Error Details     COMPONENT: NI (network interface)
Error Details     COUNTER: 592
Error Details     ERROR NUMBER: 10060
Error Details     ERROR TEXT: WSAETIMEDOUT: Connection timed out
Error Details     MODULE: nixxi.cpp
Error Details     LINE: 8777
Error Details     RETURN CODE: -10
Error Details     SUBRC: 0
Error Details     RELEASE: 640
Error Details     TIME: Thu Jun 19 10:42:42 2008
Error Details     VERSION: 37
Can some one help to solve the problem?
Thank you very much
Thom

Hi
Change the saprouter string to
/H/10.101.7.1/S/3299/H/10.151.6.194/S/32<system number>
and try !!!

Connection error in mail_logs

Hello,
since some days I have a lot of entrys like this in my mail_logs:
Tue Feb 12 12:23:31 2008 Info: Connection Error: DCID: 32131664 domain: 7-11.com IP: 199.196.10.25 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:31 2008 Info: Connection Error: DCID: 32131666 domain: www.yangzhou.cn IP: 61.177.180.12 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:31 2008 Info: Connection Error: DCID: 32131667 domain: alzinger-vogel.de IP: 81.3.54.34 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:31 2008 Info: Connection Error: DCID: 32131668 domain: zedpointrecruiters.com IP: 209.62.20.192 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:32 2008 Info: Connection Error: DCID: 32131669 domain: thinkmachine.net IP: 64.69.68.141 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:32 2008 Info: Connection Error: DCID: 32131827 domain: mm-outgoing-107.amazon.com IP: 207.171.178.142 port: 25 details: 421-'SMTP service not available, closing transmission channel' interface: 192.168.0.10 reason: unexpected SMTP response
Tue Feb 12 12:23:32 2008 Info: Connection Error: DCID: 32131670 domain: dssop.com IP: 213.171.192.236 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:32 2008 Info: Connection Error: DCID: 32131671 domain: d055108.adsl.hansenet.de IP: 80.171.55.108 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:32 2008 Info: Connection Error: DCID: 32131672 domain: sexatlas.com IP: 216.130.185.4 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:32 2008 Info: Connection Error: DCID: 32131673 domain: dannowicki.com IP: 66.246.195.42 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:32 2008 Info: Connection Error: DCID: 32131674 domain: curvanti.rw IP: 64.18.138.88 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:32 2008 Info: Connection Error: DCID: 32131675 domain: audioforums.com IP: 66.249.253.49 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:32 2008 Info: Connection Error: DCID: 32131677 domain: orgyhome.net IP: 8.15.231.104 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:32 2008 Info: Connection Error: DCID: 32131678 domain: huw.cn IP: 218.85.137.147 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:32 2008 Info: Connection Error: DCID: 32131679 domain: jieke.com.cn IP: 202.165.98.232 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:32 2008 Info: Connection Error: DCID: 32131680 domain: 263.com IP: 211.100.28.126 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
Tue Feb 12 12:23:32 2008 Info: Connection Error: DCID: 32131681 domain: aaaaa.com.tw IP: 211.21.231.130 port: 25 details: timeout interface: 192.168.0.10 reason: connection timed out
What is going wrong ?
I checked in the gui in Outgoing Destinations, for this domains and I didnt find anything about this domains. Also isn't there not much more emails like before (it seems everything is ok). Only my mailservers are allowed to send emails over the appliance. But I didnt find anything at the mail servers in the logs.
Thanks for any comment.

Looks like you've got at least two different causes in there. You managed to connect to Amazon, but they hung up on you. That at least verifies that your network connectivity is working, but who knows why Amazon hung up on you.
Most of the rest look like spam domains:
sexatlas.com
orgyhome.net
263.com
aaaaa.com.tw
Spam domains typically don't run SMTP servers, so any mail sent to them will be undeliverable. You say that only your own mail servers are allowed to send via your appliance, but someone is injecting those messages. Look them up in your mail_logs to see where they're coming from.

Heart beat could not open connection, error code 110

Hi, where can I find error codes for NFR and NSM?
I have problems with some agents connecting to the engine:
2/17/2010 16:02:55 EngineInterface: Heart beat could not open connection, error code 110
Both engine and agent runs on the same server (10.236.19.147):
AgentNCP Service Config
Host Address: 10.236.19.147
Service Ports: HTTPS: 3037 HTTP: 0
Data Path: /var/opt/novell/filereporter/agentncp
Debug Logging: Enabled
Heartbeat: 60 seconds
Engine Address: 10.239.19.147:3035
Use SSL: Yes
Alternate Hostname: huanovellfs1
Engine Service Config
Host Address: 10.236.19.147
Service Ports
Client HTTPS: 3033 HTTP: 0
Agent HTTPS: 3035 HTTP: 0
Data Path: /var/opt/novell/filereporter/engine
Debug Logging: Enabled
Heartbeat: 60 seconds
DSI Address: 10.236.19.89:8009
Use SSL: Yes
Scans per Volume: 2
Another OES2 server connects fine to the engine, butI have a Netware agent, which also fails to connect:
Feb 17, 2010 4:08:11 PM SR Interface: Heart beat could not open connection.
NFR is 1.0.0
Thanks for any input.
Istvan

Hi Istvan! Sorry for the delay in our response! we are in the process
of building a list of error codes for everyone! in the meantime the 110
means the following:
// Couldn't create a new network interface
#define CC_STATUS_CCS_CANT_CREATE 110
Is this an NSM integration installation?
Also, remove the alternate hostname.
If you don't mind, let's move this support issue to
filereporter"@"novell.com!
Thank you!
icseke wrote:
> Hi, where can I find error codes for NFR and NSM?
>
> I have problems with some agents connecting to the engine:
>
> 2/17/2010 16:02:55 EngineInterface: Heart beat could not open
> connection, error code 110
>
> Both engine and agent runs on the same server (10.236.19.147):
>
>
> AgentNCP Service Config
> ------------------------------------------------------------------------------
> Host Address: 10.236.19.147
> Service Ports: HTTPS: 3037 HTTP: 0
>
> Data Path: /var/opt/novell/filereporter/agentncp
> Debug Logging: Enabled
> Heartbeat: 60 seconds
> Engine Address: 10.239.19.147:3035
> Use SSL: Yes
> Alternate Hostname: huanovellfs1
>
> Engine Service Config
> ------------------------------------------------------------------------------
> Host Address: 10.236.19.147
> Service Ports
> Client HTTPS: 3033 HTTP: 0
> Agent HTTPS: 3035 HTTP: 0
>
> Data Path: /var/opt/novell/filereporter/engine
> Debug Logging: Enabled
> Heartbeat: 60 seconds
> DSI Address: 10.236.19.89:8009
> Use SSL: Yes
> Scans per Volume: 2
>
> Another OES2 server connects fine to the engine, butI have a Netware
> agent, which also fails to connect:
>
> Feb 17, 2010 4:08:11 PM SR Interface: Heart beat could not open
> connection.
>
> NFR is 1.0.0
>
> Thanks for any input.
>
> Istvan
>
>

SMuFF1ASDCCN CONNECTION ERROR

when I used tcode SMSY to create a RFC from Solution manager to Target system,the system displayed red light and had a error as follow:
SDCCN connection error; connect manually
Message no. SMSY_EDIT_LANDSCAPE154
Diagnosis
You tried to put the RFC destination SM_SLMCLNT100_BACK in the satellite system in the SAP Solution Data Manager (SDCCN). The action could not be performed.
Procedure
Put the RFC destination in the SAP Solution Data Manager (SDCCN) satellite system, if necessary.
when I used Tcode SDCCN in satellite system,
I found a error with
> error reading function module interface DSWP_API_SESSIONLIST_GET from SM_SLMCLNT100_BACK
> hostname 'slmprd01' unknown / CPI-C error CM_PRODUCT_SPECIFIC_ERROR.
> Sessions cannot be refreshed from destination SM_SLMCLNT100_BACK ( SLM , 0020230467 )
Refresh of session overview failed from destination SM_SLMCLNT100_BACK
who did meet this kind of problem?
waiting for...
thanks

Hi
First u maintain the target sytem client user id profile as sap_all,sap_new,s_rfcacl_all.
Then go to the smsy, maintain the rfc connection between solman and satlite system.
RFC destination SM_SLMCLNT100_BACK, it means rfc connection not generated properly, First u delete the rfc conection in u r satlite system useing sm59. Then again try to maintain the connection between the system.
Provide u r mail id i will sent the sddcn docs.
Feel free to revert back
---venkat.

OBIEE 11.1.1.3 - Fatal NI connect error 12157

Hi,
I installed OBIEE 11.1.1.3 on linux 64 bit machine. I am not able to start the scheduler process. The scheduler is not able to connect to the database for some reason. I get following error in my sqlnet.log.
Fatal NI connect error 12157, connecting to...
I ensured that tnsnames.ora file in Oracle_BI1/network/admin has the correct sid defined.
I also entered valid connection settings in coreapplications/deployment/scheduler page in the Enterprise manager.
If I turn on tracing in my sqlnet.ora file, I get
1083935040) [18-OCT-2010 15:13:14:905] niotns: niotns failed to create NS ctx, error code 12157
(1083935040) [18-OCT-2010 15:13:14:905] niotns: Couldn't connect, returning 12157
If I try to run tnsping from Oracle_BI1/bin directory, i get error
TNS-12538: TNS:no such protocol adapter
even though the protocol has been specified correctly as tcp.
Any, ideas what may be wrong ? Here are my scheduler page settings in enterprise manager
Database     Oralce 11g
Call Interface OCI 10g R1/R2
Data Source     mytnsentry
Username     myusername
Password     xxxx
Confirm Password     xxxx
Note that my database is Oracle 11g but I am using OCI 10g R1/R2 as that is the max oci version available in the dropdown. Can this be my problem? If yes, can anybody tell me how to let scheduler use different set of drivers ?

H:\>lsnrctl statusLSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 15-DEC-2008 11:04
:45
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
TNS-12541: TNS:no listener ....
It seems you don't have a listener service.
H:\>lsnrctl startLSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 15-DEC-2008 11:05
:00
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Starting tnslsnr: please wait...
Failed to start service, error 1053.
Because you still don't have a service, this error is thrown. But this statement SHOULD create a listener service,check control panel.
Since you don't have a listener.ora port 1522 is useless (until you tell Oracle to listen on a non-default number dynamically), but port 1521 can be used by default. Obviously your excel application connects sometimes to port 1522 and fails (it was already asked is this a RAC environment?). In such an environment you definitely need a working listener.ora.
Werner

SAP-OSS Connection Error

Hi,
     Am facing a problem while connecting SAP-OSS from SM59. I can able to ping 194.39.131.34 successfully from my saprouter system,router command also working fine as below.
D:saprouter>saprouter -r -S 3299 -K "p:CN=<hostname of saprouter> , OU=0000849108,OU=SAProuter, O=SAP, C=DE"
trcfile dev_rout
no logging active
Iam able to login my devleopment and solution manager systems from out side network also successfully.
But iam unable to connect the SAP-OSS (SM59) from development and solution manager.before that its working fine from last days iam getting the problem of SAP-OSS connection.
Here Iam sending the OSS Connection error on SM59 and dev_rout file after iam checking SAP-OSS through SM59.
SM59 Error :
Error Details     Error when opening an RFC connection
Error Details     ERROR: SNC processing failed: SncSessionInitiatorAK
Error Details     LOCATION: SAProuter 39.3 (SP4) on 'AEOM1SAP05'
Error Details     DETAIL: NiSncIInitHdlSecurity: sncrc=-4;000000000275AE40
Error Details     COMPONENT: NI (network interface)
Error Details     COUNTER: 8
Error Details     MODULE: nisnc.c
Error Details     LINE: 1121
Error Details     RETURN CODE: -104
Error Details     SUBRC: 0
Error Details     RELEASE: 710
Dev_Rout File :
ERROR => SncPAcquireCred()==SNCERR_GSSAPI [sncxxall.c 1439]
      GSS-API(maj): No credentials were supplied
      GSS-API(min): No credentials found for this name (not logged on) (USER=sncadm)
    Could't acquire INITIATING credentials for
    name="p:CN=AEOM1SAP05, OU=0000757839, OU=SAProu"
<<- SncSessionInitiatorAK()==SNCERR_GSSAPI
'target_acl_key' (addr=000000000202C374, len=86) full hexdump
0x00000 00030401 00080606 2b240301 25010000 ........ +$..%...
0x00010 00443042 310b3009 06035504 06130244 .D0B1.0. ..U....D
0x00020 45310c30 0a060355 040a1303 53415031 E1.0...U ....SAP1
0x00030 12301006 0355040b 13095341 50726f75 .0...U.. ..SAProu
0x00040 74657231 11300f06 03550403 13087361 ter1.0.. .U....sa
0x00050 70736572 7632                        pserv2
ERROR => NiSncIInitHdlSecurity: SncSessionInitiatorAK failed (sncrc=-4;00000000027DFB50) [nisnc.c      1124]
ERROR => NiSncHandleForAddr C9/-1, 194.39.131.34 (rc=-17) [nirout.cpp   3272]
ERROR => NiRClientHandle: NiRExRouteCon for C9/-1 'AEOM1SAP05.aeom.local' failed (rc=-17) [nirout.cpp   2650]
Guide me the same.
Thanku
Thanku

Hi hashit,
1 st Restart the Solman Server and go to command prompt. Then select the SAPROUTER drive ( D: > cd saprouter )
Currently, your SNC Saprouter process is not up and running, please stopyour saprouter process with command ' saprouter -s ' and restart it using the following with correct User.
D:saprouter> saprouter -r -V2 -K "p:CN=<hostname>, OU=<Number>, OU=SAProuter, O=SAP, C=DE"
Please note that to ensure you Saprouter process is running, you must not close the command prompt screen after you started the above. Once you closed the screen, your saprouter process is stopped and your connection to SAP is dropped.
Please try it and Let me know
Regards
Thomas.T

Mailbox Move Not Complete - Unable to make admin interface connection to server.

Hello,
I have added a second exchange 2007 server and have moved over 20 mailboxes to the new server. I seem to have a problem that the mailbox move has not been completed properly. I'm getting errors in the event log that the search indexer cannot connect to the
admin interface. I'm also unable to login as any one of the users who I've moved to the new server.
Here's one of the errors I'm getting:
Exchange Search Indexer has temporarily disabled indexing of the Mailbox Database Third Storage Group\Mailbox Database 03 (GUID = d4f3ee4d-68b0-4d21-8a76-ee96bf298f34) due to an error (Microsoft.Mapi.MapiExceptionNetworkError: MapiExceptionNetworkError:
Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
Diagnostic context:
    Lid: 10648   dwParam: 0x6D9      Msg: EEInfo: Generating component: 2
    Lid: 14744   dwParam: 0x6D9      Msg: EEInfo: Status: 1753
    Lid: 9624    dwParam: 0x6D9      Msg: EEInfo: Detection location: 501
    Lid: 13720   dwParam: 0x6D9      Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x6D9      Msg: EEInfo: NumberOfParameters: 4
    Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
    Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[1]: Unicode string: EP-SW-EX04
    Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[2]: Long val: -1988875570
    Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[3]: Long val: 382312662
    Lid: 24060   StoreEc: 0x80040115
    Lid: 23746
    Lid: 31938   StoreEc: 0x80040115
    Lid: 19650
    Lid: 27842   StoreEc: 0x80040115
    Lid: 20866
    Lid: 29058   StoreEc: 0x80040115
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Int32 ec, DiagnosticContext diagCtx)
   at Microsoft.Mapi.ExRpcAdmin.Create(String server, String user, String domain, String password)
   at Microsoft.Exchange.Search.NotificationWatcher.NotificationWatcherThread()).

Hello,
I have been fighting today with the migration off my old SBS2003 server to a brand new SBS2008 server. I have been preparing this migration for a couple off weeks
now (watching videos, reading migration manual from Microsoft, searching TechNet, etc.)
After some troubles with installing the server in Migration mode if finally came to the part to move my old (legacy) mailboxes to the new SBS2008 server. At this point the drama started @#$@$#&^%%#$@
I followed the manual off Microsoft which descripted how to move these mailboxes.
Exchange displayed a error message :
MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
When I googled this error message I realized that many people encountered the same problem but no one had the right answer to this question. I have searched hours and hours to find a solution. It started to drive me crazy and to make it even more worse i discovered
that even though i completed the first step in the migration proces (update the schema to allow a SBS2008 DC to join the domain) my replication with the other DC controllers came with a schema mismatch error???? WTF is going on !!!!!!!!
Finally a brilliant college off me came with the answer that solved all my problems: To GET RID OFF THIS ERROR MESSAGE INSTALL: Messaging API and Collabration Data Objects 1.2.1 on the Exchange server.
After moving about 60 mailboxes my blood pressure dropped and became stable again.
I Have on finall question WHY Microsoft? Was this to much trouble to put this in het migration manual off 81 pages?
from-a-very-disappointed-microsoft-user
PLS: send me a reply if this solved you're problem moving the mailboxes to the new server. !

MapiExceptionNetworkError: Unable to make admin interface connection to server

Receiving the following error trying to move mailboxes from Exchange 2003 to 2007 after installation. Verified all NIC's are configured. All Exchange processes are running as 'Local system'. Any other suggestions?
MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
Diagnostic context:......
    Lid: 10648   dwParam: 0x6D9      Msg: EEInfo: Generating component: 2
    Lid: 14744   dwParam: 0x6D9     Msg: EEInfo: Status: 1753
    Lid: 9624    dwParam: 0x6D9      Msg: EEInfo: Detection location: 501
    Lid: 13720   dwParam: 0x6D9      Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x6D9      Msg: EEInfo: NumberOfParameters: 4
    Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
    Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[1]: Unicode string: vienna1.cvesd.org
    Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[2]: Long val: -1988875570
    Lid: 15000   dwParam: 0x6D9      Msg: EEInfo: prm[3]: Pointer val: 0x0x04a4cef0 (UnknownPtag)
    Lid: 23746
    Lid: 31938   StoreEc: 0x80040115
    Lid: 19650
    Lid: 27842   StoreEc: 0x80040115
    Lid: 20866
    Lid: 29058   StoreEc: 0x80040115
Exchange Management Shell command attempted:
'e3e40217-6649-43be-9feb-0c4e594cbcf1' | move-mailbox -BadItemLimit '10' -TargetDatabase 'CN=Mailbox Database,CN=First Storage Group,CN=InformationStore,

I ran into the same problem during the migration from SBS 2003 Premium with ISA Server 2004 to SBS 2011 Standard, and that is how
I found this thread.
I have tried ALL of the proposed solutions but unfortunately nothing worked for me…
Even though you paid proper attention to the migration path from SBS2003 to SBS2011 manual, followed all the steps, and performed
the suggested step:
To configure remote procedure call (RPC) filtering
1.
Click
Start, click All Programs, click Microsoft ISA Server, and then click
ISA Server Management.
2.
In the ISA Server Management Console tree, expand
Microsoft Internet Security and Acceleration Server 2004, expand
ServerName, and then click Firewall Policy.
3.
In the details pane, click the
SBS Protected Networks Access Rule.
4.
On the
Taskstab, click Edit Selected Rule.
5.
On the
Protocolstab (for an access rule), click Filtering, and then click
Configure RPC protocol.
On the
Protocols tab, clear the Enforce strict RPC compliance check box, and then click
Apply.
…you will still get the notorious
MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80040115, ec=-2147221227) error.
Here is the solution to the Small Business Server 2003 with ISA Server 2004 migrating to the next level scenario:
*** Disable RPC Filter ***
To disable remote procedure call (RPC) filter
1.
Click
Start, click All Programs, click Microsoft ISA Server, and then click
ISA Server Management.
2.
In the ISA Server Management Console tree, expand
Microsoft Internet Security and Acceleration Server 2004, expand
ServerName, expand Configuration, and then click
Add-Ins.
3.
In the
Application Filters pane, click the RPC Filter.
4.
On the
Tasks tab, click Disable Selected Rule.
To save changes and update the configuration, click
Apply.
I also opted to restart the service when prompted after hitting the “Apply” button.
I hope this helps someone to keep whatever is left of his or her hair and lower the blood pressure a bit :)
This was the solution also!!
Thanks. My heart doctor says that now, ina few weeks i will be fine. and hope my hair grows again.. :)
Thank you very much
mpleite

PXI-1000B MXI-3 problems

my PXi 6071E cards does not get detected in slots 3 and 4 whereas the modules are getting detected in 5. previously all the modules where getting detected from 3.since i am using a MXI 3 interface. can anyone help me.

Suresh,
The MXI-3 extender is just a PCI-PCI bridge, so it should not affect any of the slots in your PXI-1000B chassis.
It would be good to try different MXI-3 boards, if you have more. Also you could try install other PXI boards (other than the PXI-6071E board) in slots 3 and 4.
If after doing this the board in slots 3 and 4 are still not being detected, there is a possiblity that the PXI-1000B chassis is damaged. In this case you will need to contact NI support (1-800-433-3488) to do further troubleshooting.
Claudia Lorente
Applications Engineer
National Instruments
http://www.ni.com

PXI-8331 MXI-4 interface connection error

Similar Messages

Maybe you are looking for