Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Anybody Install Admin Suite on Windows 10 Successfully??? 8
- Thread starter gknight1
- Start date
Just a word of warning to anyone on Windows 10 Insider program. The latest Fast Ring build (10532) breaks the IPO admin suite.
Tried uninstall/re-install/compatibility mode settings etc. Just refuses to start.
Even with latest SP4 9.1 admin suite.
Guess its my own fault for trying new things. :-(
Tried uninstall/re-install/compatibility mode settings etc. Just refuses to start.
Even with latest SP4 9.1 admin suite.
Guess its my own fault for trying new things. :-(
- Thread starter
- #5
RocketJTech
Technical User
I have a customer who just upgraded to windows 10. They wanted me to re-install Admin Suite, so I remoted in to their PC using Team Viewer. The download (Admin Suite Lite 9.1.4) went fine. However, on the install, it gets to the "copying Files" stage and runs a couple minutes, then freezes up. Have had to end the program multiple times. Any advice?
Thanks to technology, we can instantly communicate across the world, but it still doesn't help us know what to say.
Thanks to technology, we can instantly communicate across the world, but it still doesn't help us know what to say.
-
3
- #8
I have installed and tested the following applications on Windows 10.
IP office Manager
System Status
Monitor
Voicemail Pro – both the service and the client
Contact store – works fine except for playback. Edge and Chrome do not load the active X, so to get calls to play I had to install ie tab in chrome and then play calls back in that. I then found that ie11 was also available on the machine and it works fine in that.
One-X Call Assistant
App Server Access - Admin access on 7070 is fine, but the button to jump to the platform doesn’t work. To access the platform you can go directly to port 7071.
One-X – Admin – access on both 8080 and 9443 works as does the user login on the same ports.
IP Office softphone – Seems fine – haven’t tested every single feature
IP Office Communicator – Seems fine – haven’t tested every single feature
Scopia Desktop
IP Office Plug-in for Outlook
Skype for Business with Avaya plugin
Soft console – No obvious issues
Tapi (both 1st and 3rd person modes) – Tested using Dialler - Errors after install or when you switch from 1st to 3rd person mode, but exit and reopen and then it is fine
Oak Report
| ACSS SME |
IP office Manager
System Status
Monitor
Voicemail Pro – both the service and the client
Contact store – works fine except for playback. Edge and Chrome do not load the active X, so to get calls to play I had to install ie tab in chrome and then play calls back in that. I then found that ie11 was also available on the machine and it works fine in that.
One-X Call Assistant
App Server Access - Admin access on 7070 is fine, but the button to jump to the platform doesn’t work. To access the platform you can go directly to port 7071.
One-X – Admin – access on both 8080 and 9443 works as does the user login on the same ports.
IP Office softphone – Seems fine – haven’t tested every single feature
IP Office Communicator – Seems fine – haven’t tested every single feature
Scopia Desktop
IP Office Plug-in for Outlook
Skype for Business with Avaya plugin
Soft console – No obvious issues
Tapi (both 1st and 3rd person modes) – Tested using Dialler - Errors after install or when you switch from 1st to 3rd person mode, but exit and reopen and then it is fine
Oak Report
| ACSS SME |
JoshuaThompson
Technical User
Pepp77
Did you have any mapped network drives on your Windows 10 Box when testing TAPI 2 and 3?
TAPI install goes fine for me but when I test with Dialer my mapped network drives immediately show "Disconnected". I can still navigate the drives via File Explorer, but NET USE via the command prompt shows the drives are unavailable.
Joshua
Did you have any mapped network drives on your Windows 10 Box when testing TAPI 2 and 3?
TAPI install goes fine for me but when I test with Dialer my mapped network drives immediately show "Disconnected". I can still navigate the drives via File Explorer, but NET USE via the command prompt shows the drives are unavailable.
Joshua
Have Manager 9.1 loaded and working fine on my Windows 10 laptop. One thing though, I recently attempted to upgrade a customer from 9.1 sp 4 to 9.1 sp5 by doing a format and recreate. After the IPO rebooted only the expansion modules upgraded, not the control unit. This customer had 4 sites. I tried recreating the sd card at the next site and had the same result. I had to use the Manager program upgrade option to get the control unit to upgrade. Our own office system was a 9.1 sp4 so I tried the format/recreate to upgrade to 9.1 sp5 and got the same result - no upgrade. I then borrowed a co-workers Windows 7 laptop and did a format/recreate and the upgrade was successful. Weird! My laptop was upgraded to Windows 10 from Windows 7.
-
4
- #13
Hi all,
Here is an update for anyone interested who has a problem doing a format/re-create to upgrade an IPO. I have found a solution. I noticed Windows 10 was adding a "system volume" folder to the sd card. Once I stopped Windows 10 from doing that I was able to upgrade via format/recreate. Here is how I resolved the issue...
Type gpedit.msc in the search box in the Windows taskbar.
Go to Computer Configuration, Administrative Template, All Settings.
Scroll down until you see "Do not allow locations on removable drives to be added to libraries."
Double click then check "Enabled"
Click "Apply" and then "OK"
Close the Policy Manager and reboot the computer.
Here is an update for anyone interested who has a problem doing a format/re-create to upgrade an IPO. I have found a solution. I noticed Windows 10 was adding a "system volume" folder to the sd card. Once I stopped Windows 10 from doing that I was able to upgrade via format/recreate. Here is how I resolved the issue...
Type gpedit.msc in the search box in the Windows taskbar.
Go to Computer Configuration, Administrative Template, All Settings.
Scroll down until you see "Do not allow locations on removable drives to be added to libraries."
Double click then check "Enabled"
Click "Apply" and then "OK"
Close the Policy Manager and reboot the computer.
holdmusic34
Vendor
Ivan this information should be published in an FAQ with an appropriate title so that i can be easily found and linked to. Would you consider submitting this as an FAQ? Feel free to start a thread announcing your FAQ with a link to it.
If you can't or won't, it may have to be written anyway, crediting yourself.
Now experiencing escalation fatigue.
If you can't or won't, it may have to be written anyway, crediting yourself.
Now experiencing escalation fatigue.
-
1
- #15
JoshuaThompson - Finally, somebody else with my issue!
This isn't just Windows 10 - this is also a Windows 8 x64 issue. We have had this problem for months and we have been pushing our supplier to get it to Avaya, but they won't listen.
The problem lies in Avaya's implementation of TAPI. See below -
The TAPI service gets a client request that results in a line shutdown to be handled by the tspi.
0:003> kpnL
# ChildEBP RetAddr
00 047ff148 77cb055a ntdll!KiFastSystemCallRet(void)
01 047ff14c 74c625e8 ntdll!NtDelayExecution(void)+0xa
02 047ff1b4 74c6253f KERNELBASE!SleepEx(unsigned long dwMilliseconds = 0xa, int bAlertable = 0n0)+0x98
03 047ff1c4 1000313b KERNELBASE!Sleep(unsigned long dwMilliseconds = 0xa)+0xf
WARNING: Stack unwind information not available. Following frames may be wrong.
04 047ff22c 6013f1cd tspi2w!TSPI_lineSetAppSpecific+0x8ab
05 047ff284 6014fd44 tapisrv!DestroytLineApp(unsigned long hLineApp = 0x103ee, struct _TCLIENT * ptClient = <Value unavailable error>)+0x1a5
06 047ff290 6015a4a7 tapisrv!LShutdown(struct _TCLIENT * ptClient = 0x04501678, struct _LINESHUTDOWN_PARAMS * pParams = 0x04501c20, unsigned long dwParamsBufferSize = 0, unsigned char * pDataBuf = 0x04501c5c "", unsigned long * pdwNumBytesReturned = 0x00621880)+0x14
07 047ff2c0 7720a06c tapisrv!ClientRequest(void * phContext = 0x000103ff, unsigned char * pBuffer = 0x04501c20 "", long lNeededSize = 0n60, long * plUsedSize = 0x00621880)+0xa7
08 047ff2e4 771b427f rpcrt4!Invoke(void)+0x34
09 047ff72c 771b3e99 rpcrt4!NdrStubCall2(void * pThis = 0x00000000, void * pChannel = 0x00000000, struct _RPC_MESSAGE * pRpcMsg = 0x006213a0, unsigned long * pdwStubPhase = 0x047ff744)+0x3cf
0a 047ff748 77200215 rpcrt4!NdrServerCall2(struct _RPC_MESSAGE * pRpcMsg = 0x006213a0)+0x19
0b 047ff78c 771ff35d rpcrt4!DispatchToStubInCNoAvrf(<function> * Stub = 0x60168120, struct _RPC_MESSAGE * Message = 0x006213a0, long * ExceptionCode = 0x047ff878)+0x55
0c 047ff810 771ffb78 rpcrt4!RPC_INTERFACE:
ispatchToStubWorker(struct _RPC_MESSAGE * Message = 0x006213a0, unsigned int CallbackFlag = 0, int SelectedTransferSyntaxIndex = 0n0, long * ExceptionCode = 0x047ff878)+0x13d
0d 047ff844 771ebb2b rpcrt4!RPC_INTERFACE:ispatchToStub(struct _RPC_MESSAGE * Message = 0x006213a0, unsigned int CallbackFlag = 0, int SelectedTransferSyntaxIndex = 0n0, long * ExceptionCode = 0x047ff878, class RPCP_INTERFACE_GROUP * AddressIfGroup = 0x00000000)+0x78
0e (Inline) -------- rpcrt4!LRPC_SBINDING:ispatchToStub+0x6
0f 047ff8a4 771ec070 rpcrt4!LRPC_SCALL:ispatchRequest(int * AsyncReply = 0x047ff8ec)+0xfb
10 (Inline) -------- rpcrt4!LRPC_SCALL::QueueOrDispatchCall+0x2f
11 047ff918 771eed19 rpcrt4!LRPC_SCALL::HandleRequest(struct _PORT_MESSAGE * LpcRequestHeader = 0x006217c8, struct _PORT_MESSAGE * LpcReplyHeader = 0x00622970, void * LargeRequestData = 0x00000000, unsigned long LargeRequestSize = 0)+0x270
12 047ff95c 771f0845 rpcrt4!LRPC_SASSOCIATION::HandleRequest(struct _PORT_MESSAGE * LpcRequestHeader = 0x006217c8, struct _PORT_MESSAGE * LpcReplyHeader = 0x00622970, void * LargeRequestData = 0x00000000, unsigned long LargeRequestSize = 0, int MessageIsExactSize = 0n0, class RPCP_ALPC_TOKEN_ATTR * TokenAttributes = 0x047ffa18, class RPCP_ALPC_HANDLE_ATTR * HandleAttributes = 0x00000000)+0x219
13 (Inline) -------- rpcrt4!LRPC_ADDRESS::HandleRequest+0x128
14 047ffa38 771d4583 rpcrt4!LRPC_ADDRESS:rocessIO(void * Argument = 0x00000000)+0x315
15 (Inline) -------- rpcrt4!LrpcServerIoHandler+0x18
16 047ffa78 77c59516 rpcrt4!LrpcIoComplete(struct _TP_CALLBACK_INSTANCE * Instance = 0x047ffc74, void * Context = 0x0061e994, struct _TP_ALPC * Alpc = 0x0061ea10, void * CompletionContext = 0x00000000)+0x93
17 047ffb5c 77c57dc6 ntdll!TppAlpcpExecuteCallback(struct _TP_CALLBACK_INSTANCE * Instance = 0x047ffc74, struct _TP_DIRECT * Direct = 0x0061ea10, void * ApcContext = 0x00000000, struct _IO_STATUS_BLOCK * IoSB = 0x047ffd14)+0x2c6
18 047ffd6c 757c95f4 ntdll!TppWorkerThread(void * Parameter = 0x00602ed8)+0x3c6
19 047ffd80 77c422ca kernel32!BaseThreadInitThunk(unsigned long RunProcessInit = <Value unavailable error>, <function> * StartAddress = 0x77c57a00, void * Argument = 0x00602ed8)+0x24
1a 047ffdc8 77c42299 ntdll!__RtlUserThreadStart(<function> * StartAddress = 0x77c57a00, void * Argument = <Value unavailable error>)+0x2b
1b 047ffdd8 00000000 ntdll!_RtlUserThreadStart(<function> * StartAddress = <Value unavailable error>, void * Argument = <Value unavailable error>)+0x1b
The tspi handles it and tries to read on a socket with an invalid handle.
0:007> kpnL
# ChildEBP RetAddr
00 049ff7b8 77cb196f ntdll!KiRaiseUserExceptionDispatcher(void)+0x37
01 049ff7e4 77b9fa7f ntdll!KiFastSystemCall+0xf
02 049ff804 77b97a49 ws2_32!DSOCKET::FindIFSSocket(unsigned int SocketHandle = 0x23c)+0x1d
03 (Inline) -------- ws2_32!DSOCKET::GetCountedDSocketFromSocket+0x15cb8
04 049ff838 10007e51 ws2_32!recv+0x15d29
WARNING: Stack unwind information not available. Following frames may be wrong.
05 049ff8a8 77c5780c tspi2w!TSPI_lineSetTerminal+0x45f1
06 (Inline) -------- ntdll!RtlpHpLfhSubsegmentGetBlockIndex+0x39
07 00000000 00000000 ntdll!RtlpHpLfhSubsegmentFreeBlock(struct _HEAP_LFH_CONTEXT * LfhContext = <Memory access error>, struct _HEAP_LFH_SUBSEGMENT * Subsegment = 0x00000000, char * Block = <Memory access error>, unsigned long Flags = <Memory access error>)+0x6c
This causes the TAPI service to throw an unhandled exception (You can verify this using a service debugger to watch the service whenever TAPI shuts down, for example, loading and then closing Dialer.exe) and this exception causes any other services running in the same svchost to bomb as well (verify with Event Viewer after closing TAPI - all other services will end unexpectedly as well).
I have contacted Microsoft which is where this information comes from, who basically said that Avaya need to be the ones to fix it. The more people who mention it, the more likely to get sorted it is.
As a temporary fix, Microsoft recommend Isolating Tapisrv in its own service. Although TAPI continues to throw the exception, at the very least your network drives wont lose connection. You can do that by running Command Prompt with elevated privileges and using the following command;
sc config Tapisrv type= own
This command isolates it in its own svchost.
Any questions, let me know, and spread the word! My company would like this fixed, alas we are too small for Avaya to take us seriously.
Regards,
Ryan
This isn't just Windows 10 - this is also a Windows 8 x64 issue. We have had this problem for months and we have been pushing our supplier to get it to Avaya, but they won't listen.
The problem lies in Avaya's implementation of TAPI. See below -
The TAPI service gets a client request that results in a line shutdown to be handled by the tspi.
0:003> kpnL
# ChildEBP RetAddr
00 047ff148 77cb055a ntdll!KiFastSystemCallRet(void)
01 047ff14c 74c625e8 ntdll!NtDelayExecution(void)+0xa
02 047ff1b4 74c6253f KERNELBASE!SleepEx(unsigned long dwMilliseconds = 0xa, int bAlertable = 0n0)+0x98
03 047ff1c4 1000313b KERNELBASE!Sleep(unsigned long dwMilliseconds = 0xa)+0xf
WARNING: Stack unwind information not available. Following frames may be wrong.
04 047ff22c 6013f1cd tspi2w!TSPI_lineSetAppSpecific+0x8ab
05 047ff284 6014fd44 tapisrv!DestroytLineApp(unsigned long hLineApp = 0x103ee, struct _TCLIENT * ptClient = <Value unavailable error>)+0x1a5
06 047ff290 6015a4a7 tapisrv!LShutdown(struct _TCLIENT * ptClient = 0x04501678, struct _LINESHUTDOWN_PARAMS * pParams = 0x04501c20, unsigned long dwParamsBufferSize = 0, unsigned char * pDataBuf = 0x04501c5c "", unsigned long * pdwNumBytesReturned = 0x00621880)+0x14
07 047ff2c0 7720a06c tapisrv!ClientRequest(void * phContext = 0x000103ff, unsigned char * pBuffer = 0x04501c20 "", long lNeededSize = 0n60, long * plUsedSize = 0x00621880)+0xa7
08 047ff2e4 771b427f rpcrt4!Invoke(void)+0x34
09 047ff72c 771b3e99 rpcrt4!NdrStubCall2(void * pThis = 0x00000000, void * pChannel = 0x00000000, struct _RPC_MESSAGE * pRpcMsg = 0x006213a0, unsigned long * pdwStubPhase = 0x047ff744)+0x3cf
0a 047ff748 77200215 rpcrt4!NdrServerCall2(struct _RPC_MESSAGE * pRpcMsg = 0x006213a0)+0x19
0b 047ff78c 771ff35d rpcrt4!DispatchToStubInCNoAvrf(<function> * Stub = 0x60168120, struct _RPC_MESSAGE * Message = 0x006213a0, long * ExceptionCode = 0x047ff878)+0x55
0c 047ff810 771ffb78 rpcrt4!RPC_INTERFACE:
ispatchToStubWorker(struct _RPC_MESSAGE * Message = 0x006213a0, unsigned int CallbackFlag = 0, int SelectedTransferSyntaxIndex = 0n0, long * ExceptionCode = 0x047ff878)+0x13d0d 047ff844 771ebb2b rpcrt4!RPC_INTERFACE:
ispatchToStub(struct _RPC_MESSAGE * Message = 0x006213a0, unsigned int CallbackFlag = 0, int SelectedTransferSyntaxIndex = 0n0, long * ExceptionCode = 0x047ff878, class RPCP_INTERFACE_GROUP * AddressIfGroup = 0x00000000)+0x780e (Inline) -------- rpcrt4!LRPC_SBINDING:
ispatchToStub+0x60f 047ff8a4 771ec070 rpcrt4!LRPC_SCALL:
ispatchRequest(int * AsyncReply = 0x047ff8ec)+0xfb10 (Inline) -------- rpcrt4!LRPC_SCALL::QueueOrDispatchCall+0x2f
11 047ff918 771eed19 rpcrt4!LRPC_SCALL::HandleRequest(struct _PORT_MESSAGE * LpcRequestHeader = 0x006217c8, struct _PORT_MESSAGE * LpcReplyHeader = 0x00622970, void * LargeRequestData = 0x00000000, unsigned long LargeRequestSize = 0)+0x270
12 047ff95c 771f0845 rpcrt4!LRPC_SASSOCIATION::HandleRequest(struct _PORT_MESSAGE * LpcRequestHeader = 0x006217c8, struct _PORT_MESSAGE * LpcReplyHeader = 0x00622970, void * LargeRequestData = 0x00000000, unsigned long LargeRequestSize = 0, int MessageIsExactSize = 0n0, class RPCP_ALPC_TOKEN_ATTR * TokenAttributes = 0x047ffa18, class RPCP_ALPC_HANDLE_ATTR * HandleAttributes = 0x00000000)+0x219
13 (Inline) -------- rpcrt4!LRPC_ADDRESS::HandleRequest+0x128
14 047ffa38 771d4583 rpcrt4!LRPC_ADDRESS:
rocessIO(void * Argument = 0x00000000)+0x31515 (Inline) -------- rpcrt4!LrpcServerIoHandler+0x18
16 047ffa78 77c59516 rpcrt4!LrpcIoComplete(struct _TP_CALLBACK_INSTANCE * Instance = 0x047ffc74, void * Context = 0x0061e994, struct _TP_ALPC * Alpc = 0x0061ea10, void * CompletionContext = 0x00000000)+0x93
17 047ffb5c 77c57dc6 ntdll!TppAlpcpExecuteCallback(struct _TP_CALLBACK_INSTANCE * Instance = 0x047ffc74, struct _TP_DIRECT * Direct = 0x0061ea10, void * ApcContext = 0x00000000, struct _IO_STATUS_BLOCK * IoSB = 0x047ffd14)+0x2c6
18 047ffd6c 757c95f4 ntdll!TppWorkerThread(void * Parameter = 0x00602ed8)+0x3c6
19 047ffd80 77c422ca kernel32!BaseThreadInitThunk(unsigned long RunProcessInit = <Value unavailable error>, <function> * StartAddress = 0x77c57a00, void * Argument = 0x00602ed8)+0x24
1a 047ffdc8 77c42299 ntdll!__RtlUserThreadStart(<function> * StartAddress = 0x77c57a00, void * Argument = <Value unavailable error>)+0x2b
1b 047ffdd8 00000000 ntdll!_RtlUserThreadStart(<function> * StartAddress = <Value unavailable error>, void * Argument = <Value unavailable error>)+0x1b
The tspi handles it and tries to read on a socket with an invalid handle.
0:007> kpnL
# ChildEBP RetAddr
00 049ff7b8 77cb196f ntdll!KiRaiseUserExceptionDispatcher(void)+0x37
01 049ff7e4 77b9fa7f ntdll!KiFastSystemCall+0xf
02 049ff804 77b97a49 ws2_32!DSOCKET::FindIFSSocket(unsigned int SocketHandle = 0x23c)+0x1d
03 (Inline) -------- ws2_32!DSOCKET::GetCountedDSocketFromSocket+0x15cb8
04 049ff838 10007e51 ws2_32!recv+0x15d29
WARNING: Stack unwind information not available. Following frames may be wrong.
05 049ff8a8 77c5780c tspi2w!TSPI_lineSetTerminal+0x45f1
06 (Inline) -------- ntdll!RtlpHpLfhSubsegmentGetBlockIndex+0x39
07 00000000 00000000 ntdll!RtlpHpLfhSubsegmentFreeBlock(struct _HEAP_LFH_CONTEXT * LfhContext = <Memory access error>, struct _HEAP_LFH_SUBSEGMENT * Subsegment = 0x00000000, char * Block = <Memory access error>, unsigned long Flags = <Memory access error>)+0x6c
This causes the TAPI service to throw an unhandled exception (You can verify this using a service debugger to watch the service whenever TAPI shuts down, for example, loading and then closing Dialer.exe) and this exception causes any other services running in the same svchost to bomb as well (verify with Event Viewer after closing TAPI - all other services will end unexpectedly as well).
I have contacted Microsoft which is where this information comes from, who basically said that Avaya need to be the ones to fix it. The more people who mention it, the more likely to get sorted it is.
As a temporary fix, Microsoft recommend Isolating Tapisrv in its own service. Although TAPI continues to throw the exception, at the very least your network drives wont lose connection. You can do that by running Command Prompt with elevated privileges and using the following command;
sc config Tapisrv type= own
This command isolates it in its own svchost.
Any questions, let me know, and spread the word! My company would like this fixed, alas we are too small for Avaya to take us seriously.
Regards,
Ryan
JoshuaThompson
Technical User
We found the problem occurs when the tapi driver closes or stops being used.
In our situation when this issue occurred we found our network drives would show disconnected (even though we can still manually explore them). Windows explorer would show a red x next to the network drive. When this happened we could not also elevate any process on said network drive.
In our troubleshooting we determined that as long as something used the tapi driver everything still worked just fine.
We would open the windows dialer, make a call and hang up and our network drives would still be active. It wasnt until we closed the dialer that the network drives disconnected.
We created a standalone service that always maintains an active tapi session. With this active connection we no longer experience these drive disconnects.
This problem occurred as soon as we started our Windows 10 testing. We run 64 bit machines.
We have both TAPI2 and TAPI3 installed on the client machines and are using only TAPI2 in a Third Party mode.
We are running r9.0 on IP office 500 (non V2).
In our environment TAPI Is not throwing any errors.
We could have saved some time if we knew about MS's recommendation to isolate the service.
In our situation when this issue occurred we found our network drives would show disconnected (even though we can still manually explore them). Windows explorer would show a red x next to the network drive. When this happened we could not also elevate any process on said network drive.
In our troubleshooting we determined that as long as something used the tapi driver everything still worked just fine.
We would open the windows dialer, make a call and hang up and our network drives would still be active. It wasnt until we closed the dialer that the network drives disconnected.
We created a standalone service that always maintains an active tapi session. With this active connection we no longer experience these drive disconnects.
This problem occurred as soon as we started our Windows 10 testing. We run 64 bit machines.
We have both TAPI2 and TAPI3 installed on the client machines and are using only TAPI2 in a Third Party mode.
We are running r9.0 on IP office 500 (non V2).
In our environment TAPI Is not throwing any errors.
We could have saved some time if we knew about MS's recommendation to isolate the service.
- Status
Similar threads
