cancel
Showing results for 
Search instead for 
Did you mean: 

OpenPS 4.04 - Error Connecting

Former Member
0 Kudos

I am trying to install OpenPS 4 MSP (4.04) on a Windows 7 SP1 machine that has MSP 2003 SP3. On a similar machine, the installation was successful and the transfer happens successfully between MSP and SAP PS. However, on a second machine, I receive this error when I hit the "Connect" button on MSP. Has anyone seen this before and if so, your suggestions would be highly appreciated:

 

System.Runtime.InteropServices.COMException (0x800A0CC1): Item cannot be found in the collection corresponding to the requested name or ordinal.

at ADODB.Fields.get_Item(Object Index)

at ADODB.InternalFields.get_Item(Object index)

at OpenPS_LogonDB.PS_cSystems.GetSystem(Int32& I_id, String& E_Name, String& E_System, String& E_Client, String& E_Language, String& E_ApplicationServer, String& E_SystemNumber, String& E_RouterString, String& E_MessageServer, String& E_GroupName, Boolean& E_ABAPDebug, Boolean& E_UseSNC, String& e_SNCSystem, Boolean& E_BWRFC)

at OpenPS_LogonDB.PS_fLogon.initScreen()

at OpenPS_LogonDB.PS_fLogon.PS_fLogon_Load(Object eventSender, EventArgs eventArgs)

at System.Windows.Forms.Form.OnLoad(EventArgs e)

at System.Windows.Forms.Form.OnCreateControl()

at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

at System.Windows.Forms.Control.CreateControl()

at System.Windows.Forms.Control.WmShowWindow(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

at System.Windows.Forms.ContainerControl.WndProc(Message& m)

at System.Windows.Forms.Form.WmShowWindow(Message& m)

at System.Windows.Forms.Form.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

This is resolved now. It was an issue with the user profile being corrupted somehow.

Answers (0)