Virtualization

Is the cache file on the root of C:\? Is the name of the file random? I think I know what might be going on but if you could provide more info that would be great.

The cache is not in the root of c:/

/Kalle - I actually saw your post on another messageboard and it provided some insight to the problem above. By deleting the directory, after monitoring, it does not virtualize folder structure where it was suppose to go. Thanks for that post.

Now - however, I am but am having problems now with a dll that is not getting instantiated - probably. Again this is a custom VB6 app that does not have the best error messaging. I am getting a "can not create object" error. Not sure where to go from here. I have monitored and launched the application. Upon launching - I am getting the same error. Any thoughts?

That sounds like a simple COM registration problem. Profile the application using dependency walker and you should be able to see the failed DLL call highlighted in red. You need to sort of match up when the error message happens to where you are in the trace because there is plenty of information in the trace.

So I thought that I fixed my dependency issue.

SoftGrid Client - local - WORKS FINE
1. I was able to run the application with no problems on a box where I have installed the SoftGrid Client with the command line option to run locally. And with this SoftGrid Client option running locally, I am having no problems.

2. SoftGrid Client - Streamed - COM issues
I am now getting a different COM error when I attempt to load the app. I know this is custom error, but may give you an idea of the issue. I was able to use a "net use" command to view the Q drive and registered the dll listed below with no luck. Any other thoughts?:
The VB Application identified by the event source logged this Application Authoring Tool Business Objects: Thread ID: 3096 ,Logged: rm94073: 3/6/2008 4:40:54 PM|Authoring Tool Business Objects.basBusObjRoutines::CreateServerObject|1|5|Invalid procedure call or argument

I'm not sure I get the two scenarios. When you say local the application is 100% cached and the second scenario is when you are only partially streaming the application?

The first scenario I am using the SoftGrid client with the an MSI install. Sorry. I know I was not that clear - The way I am deploying is with an MSI utilizing "softgrid-wd-setup.msi" MSIDEPLOYMENT=TRUE command line option. And using the MSI Utility to create an MSI for local deployments.

In the second scenario I am actually deploying like any other person would via the Softgrid client utlizing a softgrid server. Still not sure what the problem is.

Is there any difference between the two ways to deploy other then the obvious of the install command line option? I am very confused at why one would work and the other would not.

Thanks again for any help that you may provide.

When you stream in scenario #2 is the application 100% in the cache or is the SFT partially streamed. I've seen the rare instance where the application will not work with FB1 and FB2 type streaming.

Thanks for the reply - I figured it out my issue. I had conflicts with machine names in my registry. When I sequenced the custom app, the custom app recorded the machine name in the registry (which happened to be the same machine name in scenario), which is why scenario 2 worked and 1 did not. So I just needed to delete the registry key where of the machine name that the custom app was looking at.

Now I am having issues with MS Word 2003. Performance is horrible. Have you had any problems with Word? The only way I can sequence the custom app is to the c: drive, which is not recommended, I know. Unfortunately, this is the only way it will work. So I am sequencing Word to the same same directory as the custom app suite directory (c:\program files\custom app suite name\custom app). Would this be causing any performance issues?

Again thanks for any insight. You are the only person alive out there that I have posted questions to. Thanks you.

Does this app have a custom template? I've had Word take 20 seconds to launch when using a Hummingbird DM template. Otherwise Word should behave ok. You only take about a .004 second delay per I/O operation when the files are remapped from C:\ to Q:\. That means in most cases you won't notice the difference but this doesn't mean always.

Well - it looks like it is a conflict with a product called Proventia Desktop - Internet Security Systems (now IBM). Not sure what the root cause is yet, but I have uninstalled the product and the streaming and performance is fine. If you are interested in the root cause, let me know and Ill post it out here. Have a nice weekend kkaminsk.

If you could post what you find out that would be great. Might save somone some head bashing against the desk. :P