Error during StarPort Startup...

[TheHecklerj]

Getting an error...

"Invalid Parameter was passed to the driver"
and
"Failed to create an empty document"

When I attempt to launch the application. This also occurs as system startup.

This is a Windows 2003 Enterprise machine. Please let me know if there is more info that I can provide on this. I will continue to review the documentation.

[alexander (staff)]

Yes, please provide the log file. By default, it is located in C:\Documents and Settings\<Your user name>\Local Settings\Application Data\StarPort.log

[TheHecklerJ]

20:45:46 - Entering func: CLanguager::LoadLanguage(language=0x409)
20:45:46 - Exiting func: CLanguager::LoadLanguage(language=0x409)
20:45:46 - Entering func: CStarPortAPI::CStarPortAPI()
20:45:46 - Entering func: CStarPortAPI::DriverOpen()
20:45:46 - Exiting func: CStarPortAPI::DriverOpen()
20:45:46 - Entering func: CStarPortAPI::DriverVersion(...)
20:45:46 - CStarPortAPI::DriverVersion: Calling DeviceIoControl(...)
20:45:46 - CStarPortAPI::DriverVersion: DeviceIoControl() failed, status == 87 !
20:45:46 - Exiting func: CStarPortAPI::DriverVersion(...)
20:45:46 - Exiting func: CStarPortAPI::CStarPortAPI()
20:45:46 - Exception caught: Invalid parameter was passed to the driver.

[TheHecklerJ]

16:52:19 - Entering func: CStarPortApp::InitInstance()
16:52:19 - Entering func: CLanguager::LoadAppropriateLanguage()
16:52:19 - Entering func: CLanguager::GetLANGIDFromRegistry()
16:52:19 - Exiting func: CLanguager::GetLANGIDFromRegistry()
16:52:19 - Entering func: CLanguager::LoadLanguage(language=0x409)
16:52:19 - Exiting func: CLanguager::LoadLanguage(language=0x409)
16:52:19 - Exiting func: CLanguager::LoadAppropriateLanguage()
16:52:19 - Entering func: CStarPortAPI::CStarPortAPI()
16:52:19 - Entering func: CStarPortAPI::DriverOpen()
16:52:19 - Exiting func: CStarPortAPI::DriverOpen()
16:52:19 - Entering func: CStarPortAPI::DriverVersion(...)
16:52:19 - CStarPortAPI::DriverVersion: Calling DeviceIoControl(...)
16:52:19 - CStarPortAPI::DriverVersion: DeviceIoControl() failed, status == 87 !
16:52:19 - Exiting func: CStarPortAPI::DriverVersion(...)
16:52:19 - Exiting func: CStarPortAPI::CStarPortAPI()
16:52:19 - Exception caught: Invalid parameter was passed to the driver.
16:52:21 - Exiting func: CStarPortApp::InitInstance()
16:52:21 - Entering func: CStarPortApp::ExitInstance()
16:52:21 - Exiting func: CStarPortApp::ExitInstance()
16:52:21 - Entering func: CLanguager::~CLanguager()
16:52:21 - Exiting func: CLanguager::~CLanguager()
16:52:21 - Entering func: CIcon::DestroyMember()
16:52:21 - Exiting func: CIcon::DestroyMember()
16:52:21 - Entering func: CIcon::DestroyMember()
16:52:21 - Exiting func: CIcon::DestroyMember()
16:52:21 - Entering func: CIcon::DestroyMember()
16:52:21 - Exiting func: CIcon::DestroyMember()

[Val (staff)]

Hi TheHecklerJ,

This error 87 can be reported in the following cases:
1) StarPort.sys driver is not started
2) You have different versions of the driver and the StarPort GUI. (this could happen if you have updated an old StarPort installation)

BTW do you use the last StarPort version?
If no, please download the last version from our site, uninstall your current StarPort, reboot your PC and then install the new package.

I've just retested the new StarPort installation on Win2003 SE machine - it works OK for me.

[TheHecklerJ]

This is a fresh install of Starport.

This is a new install using the current available software package from your site.

Can you please provide information on what Starport.sys depends on as far as lower drivers.

TY...

[TheHecklerJ]

According to MSINFO32, the Starport driver is currently running as well.

[Val (staff)]

TheHecklerJ,

StarPort driver doesn't depend on any other drivers.

Could you please uninstall your current StarPort installation and reinstall it after rebooting the PC?

[TheHecklerJ]

Ok, so I have performed the following...

Uninstall Starport
Reboot
Check Registry and Program Files directory, clear out anything related to RocketDivision / Starport.
Reboot
Reinstall Starport
Reboot

Still getting the same message. Since StarPort does not depend on any OS / HDW drivers directly to start, theoretically all machines would experience this as Starport would be a self contained application. Again I downloaded Starport off of RocketDivision.com the day that I started this thread.

[Val (staff)]

TheHecklerJ,

We have tested this StarPort package (version 0x20040615) with Win2003 Server EE and Win2003 Server SE - all works without problems...

Could you give us more information about your Win2003 Server EE installation? Is there any third party software installed?
What are your system default locale settings, Language, so on?

Has StarPort driver started OK according to the Device Manager?
(you can see this info in "SCSI and RAID Controllers/StarPort Storage Controller")

[TheHecklerJ]

The driver is started.

There are numerous 3rd party applications installed, but as previously mentioned, Starport does not depend on other drivers or applications to run, however I have disabled any 3rd party software that I could.

This is an installation on a Dell PowerEdge 1600SC server, I have tested this on a few machines with the same issue. However this issue does not occur when I test it within a Virtual PC or VMWare installation.

The system is installed with an English US locale.

Installed apps are...
Symantec AV - Corp 8.x
WinRar
VERITAS Storage Foundation for Windows 4.1 (replaces logical disk mgr, DMIO.SYS)
All Win2k3 hotfixes
Bandwidth controller (filter driver to limit bandwidth, configurable per nic and port / protocol).
Intel NIC driver / teaming package
Qlogic SANBlade software
Textpad

I will start removing components 1 by 1 to bring me back to a BASE install of the OS for troubleshooting...

[TheHecklerJ]

Ok, after removing VERITAS Storage Foundation for Windows 4.1, the issue went away, however this is not an application I can do without in my environment.

Is there any way that you can perform testing to find which part of Starport is conflicting with this software.

Please let me know, I can help obtain an eval version of the software for your testing.

Thank you...

[Val (staff)]

Ok, after removing VERITAS Storage Foundation for Windows 4.1, the issue went away, however this is not an application I can do without in my environment.

Is there any way that you can perform testing to find which part of Starport is conflicting with this software.

Please let me know, I can help obtain an eval version of the software for your testing.

Thank you...

TheHecklerJ,

Thank you for your hard work solving the problem.

We're suspecting the VERITAS software could intercept or block communications between StarPort GUI and StarPort stogage port driver...

But we have no VERITAS Storage Foundation for Windows in our hands, so it would be very helpfull for us to obtain an eval version of it to test our StarPort with it and fix the issue...

Thank you in advance.

[cqpanis3]

Hi,

I am also encountering the same problem. With Veritas Storage Foundation HA installed, I can't get StarPort to startup normally.

The last posting in this forum was dated July 2004. I was wondering if there is already a solution or a fix for this problem.

I am evaluating Starport v2.6.0

Thanks!

[Val (staff)]

Hi,

I am also encountering the same problem. With Veritas Storage Foundation HA installed, I can't get StarPort to startup normally.

The last posting in this forum was dated July 2004. I was wondering if there is already a solution or a fix for this problem.

I am evaluating Starport v2.6.0

Thanks!

Hi,

The problem was in Veritas Storage Foundation v4.1.
Their kernel mode filter driver intercepted StarPort's IOCTLs, so out control application was unable to communicate with the driver.

Veritas guys confirmed their bug and promised it to be fixed soon.
But we have no chances to evaluate the recent Veritas Storage Foundation version to check it.

What version of the Storage Foundation do you use?