Error Codes on SG 4.1
I am running SoftGrid 4.1 in a Virtual Enviroment (VMware). I have virtualized Foxit PDF to verify that communications are working between Application Server and Clients.
XP Pro running SQL Server 2000
2003 Server running Virtual Application Server
XP Pro running SoftGrid Client
The application suite that I am trying to virtualize uses the ODBC to point to SQL Databases. I am able to ping the SQL Server and the Virtual Application Server from the client. I checked the ODBC registry settings to make sure that the correct DB names are included. Any ideas on what is happening based on these errors? I did some research on these errors and they are typically associated with the client not being able to connect to the Application Server.
[02/27/2007 11:08:17.252 JGSW ERR] {hap=20:app=ProForm for Windows 3.0.0.11:tid=A48:usr=brbarber}
The SoftGrid client could not connect to stream URL 'rtsp://%SFT_SOFTGRIDSERVER%:554/SoftPro%204.0/SoftPro%204.0.sft' (FS status: 15601C2A-00002AFC).
[02/27/2007 11:08:17.252 SWAP ERR] {hap=20:app=ProForm for Windows 3.0.0.11:tid=A48:usr=brbarber}
The client was unable to connect to a SoftGrid server (rc 15601C2A-00002AFC)
[02/27/2007 11:08:20.677 TRAY ERR] {tid=F84:usr=brbarber}
The SoftGrid Client could not launch ProForm for Windows 3.0.0.11.
The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.
Error code: 410038-15601C2A-00002AFC
XP Pro running SQL Server 2000
2003 Server running Virtual Application Server
XP Pro running SoftGrid Client
The application suite that I am trying to virtualize uses the ODBC to point to SQL Databases. I am able to ping the SQL Server and the Virtual Application Server from the client. I checked the ODBC registry settings to make sure that the correct DB names are included. Any ideas on what is happening based on these errors? I did some research on these errors and they are typically associated with the client not being able to connect to the Application Server.
[02/27/2007 11:08:17.252 JGSW ERR] {hap=20:app=ProForm for Windows 3.0.0.11:tid=A48:usr=brbarber}
The SoftGrid client could not connect to stream URL 'rtsp://%SFT_SOFTGRIDSERVER%:554/SoftPro%204.0/SoftPro%204.0.sft' (FS status: 15601C2A-00002AFC).
[02/27/2007 11:08:17.252 SWAP ERR] {hap=20:app=ProForm for Windows 3.0.0.11:tid=A48:usr=brbarber}
The client was unable to connect to a SoftGrid server (rc 15601C2A-00002AFC)
[02/27/2007 11:08:20.677 TRAY ERR] {tid=F84:usr=brbarber}
The SoftGrid Client could not launch ProForm for Windows 3.0.0.11.
The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.
Error code: 410038-15601C2A-00002AFC
0 Comments
[ + ] Show comments
Answers (22)
Please log in to answer
Posted by:
ksaunam
17 years ago
There has been some cases during these years where sequencing on virtual machine has resulted non-working packages but the exact same thing on physical machine results perfectly valid and working package so it might be that this is one of those odd cases.
In case of vmware, before going to physical Sequencer installation, I would suggest that you modify your installation of VMware Tools and remove "Shared Folder" feature from the installed features, I remember this one causing some problems in the past as well.
br,
Kalle
In case of vmware, before going to physical Sequencer installation, I would suggest that you modify your installation of VMware Tools and remove "Shared Folder" feature from the installed features, I remember this one causing some problems in the past as well.
br,
Kalle
Posted by:
kkaminsk
17 years ago
This is one of those common undocumented error codes (I believe). Check the log file on the server. If you look in there you will see the full path to where the server thinks the SFT is. Check that against the real path to the SFT file and you should find a typo.
Posted by:
ksaunam
17 years ago
[02/27/2007 11:08:17.252 JGSW ERR] {hap=20:app=ProForm for Windows 3.0.0.11:tid=A48:usr=brbarber}
The SoftGrid client could not connect to stream URL 'rtsp://%SFT_SOFTGRIDSERVER%:554/SoftPro%204.0/SoftPro%204.0.sft' (FS status: 15601C2A-00002AFC).
Do you have %SFT_SOFTGRIDSERVER% environment variable present on your client machine? If not, that's the most probable reason as your OSD refers SoftGrid Server address by that name..
Note that client does not add this env. variable automatically in any way, it's just something that sequencer will offer as default for server name during Package Configuration Wizard and something you need to remember to change to something valid for your environment (that is, ip-address or network name your SoftGrid Server has)
/Kalle
Posted by:
windmiller
17 years ago
Is the %SFT_SOFTGRIDSERVER% environment variable something that can only be\should only be designated in the package while sequencing? This is entered in during the Sequencing under Host Name? Or is there additional locations this should be specified?
I tried Sequencing a new version just to try out specifiying a HostName and now I am getting "A Sharing violation occured while accessing C:\Program Files\Softricity\SOftGrid Sequencer\Logs\sft-seq-log.txt.
I tried Sequencing a new version just to try out specifiying a HostName and now I am getting "A Sharing violation occured while accessing C:\Program Files\Softricity\SOftGrid Sequencer\Logs\sft-seq-log.txt.
Posted by:
BadShadd
17 years ago
During my application sequencing & client installation testing, I 'hard-coded' the SoftGrid server name & everything worked fine. If you've decided to stick with the variable, this is the note I found in the Softricity SoftGrid 4.0 Administration Training Guide:
NOTE: If the variable %SFT_SOFTGRIDSERVER% is used it will check the User Environment Variables and use that value if found. If it can’t find a value in the User Environment Variables, it will check the System Environment Variables. If the client can not find a value for the environment variable, it will leave the environment variable and log a warning message to the client log indicating that the environment variable could not be found.
NOTE: If the variable %SFT_SOFTGRIDSERVER% is used it will check the User Environment Variables and use that value if found. If it can’t find a value in the User Environment Variables, it will check the System Environment Variables. If the client can not find a value for the environment variable, it will leave the environment variable and log a warning message to the client log indicating that the environment variable could not be found.
Posted by:
windmiller
17 years ago
I am reconfiguring the clients and packages to include the server name instead of %SFT_SOFTGRIDSERVER%
I had installed a second instance of Sequencer on a second PC, I wonder if that is what is causing the "A Sharing violation occured while accessing C:\Program Files\Softricity\SOftGrid Sequencer\Logs\sft-seq-log.txt." error?
Update:
Uninstalling 2nd Seqeuncer PC didnt do the trick. Going to reimage the PC and see if some residual files are causing this. Cant imagine what though.
I had installed a second instance of Sequencer on a second PC, I wonder if that is what is causing the "A Sharing violation occured while accessing C:\Program Files\Softricity\SOftGrid Sequencer\Logs\sft-seq-log.txt." error?
Update:
Uninstalling 2nd Seqeuncer PC didnt do the trick. Going to reimage the PC and see if some residual files are causing this. Cant imagine what though.
Posted by:
ksaunam
17 years ago
ORIGINAL: windmiller
Is the %SFT_SOFTGRIDSERVER% environment variable something that can only be\should only be designated in the package while sequencing? This is entered in during the Sequencing under Host Name? Or is there additional locations this should be specified?
Well, it's just a default that Sequencer offers to you. You can define any other environment variable there as well (e.g. %mysoftgridserver%), but you must make sure that all the clients will have that environment variable set, otherwise client won't know which server to contact for stream-operation.
Or as it's usually done, just put your SoftGrid Server's physical hostname, some DNS alias or such over there.
Later on you can modify this by opening OSD file(s) and changing HREF="rtsp://..." attribute.
/Kalle
Posted by:
windmiller
17 years ago
I reinstalled a fresh copy of XP Pro and then the Sequencer but am still getting the following error. I've got the SQ Application Server and clients turned off to see if one of them was causing it but still getting same error.
"A Sharing violation occured while accessing C:\Program Files\Softricity\SOftGrid Sequencer\Logs\sft-seq-log.txt." error
"A Sharing violation occured while accessing C:\Program Files\Softricity\SOftGrid Sequencer\Logs\sft-seq-log.txt." error
Posted by:
ksaunam
17 years ago
ORIGINAL: windmiller
I reinstalled a fresh copy of XP Pro and then the Sequencer but am still getting the following error. I've got the SQ Application Server and clients turned off to see if one of them was causing it but still getting same error.
"A Sharing violation occured while accessing C:\Program Files\Softricity\SOftGrid Sequencer\Logs\sft-seq-log.txt." error
That's pretty weird error, never have I seen that before. What else you might be running on Sequencer machine, I hope no antivirus or anything like that?
At which point (after doing what) exactly you are getting that error message?
/Kalle
Posted by:
windmiller
17 years ago
After the package is complete and I go to save it to a local folder. It gets about 75% of the way through saving and is during the "Encoding Blocks" section that I get this error. I am going to do some more testing this afternoon or tomorrow but it seems to be happening with the MSADE version of our software. The SQL version doesnt seem to be having this issue.
Posted by:
kkaminsk
17 years ago
ORIGINAL: windmiller
"A Sharing violation occured while accessing C:\Program Files\Softricity\SOftGrid Sequencer\Logs\sft-seq-log.txt." error
Did you get rid of some exclusions in the sequencer?
Posted by:
windmiller
17 years ago
I checked and everything looks ok, but I went ahead and set it back to default just in case. It is showing that the following folder is excluded
C:\Program Files\Softricity\SoftGrid Sequencer\Logs
I assume that means that the sft-seq-log.txt that the error is referencing is included in that exclusion?
I checked the sft-seq-log.txt and here is where it goes haywire.
[03/06/2007 16:25:45 VRB CORE] Reading index header...
[03/06/2007 16:25:45 VRB CORE] Reading index header...
[03/06/2007 16:25:45 VRB CORE] Encoding blocks...
[03/06/2007 16:25:46 ERR ] CSGApplicationManager::FindSuiteByProcessId PID 0x8110 FAILED (0x 2)
[03/06/2007 16:25:48 ERR ] CSGApplicationManager::FindSuiteByProcessId PID 0x8110 FAILED (0x 2)
" "
I feel like I must be doing something wrong but cant think of anything that I am doing that is different from the last time it worked. I was able to successfully package 3 versions of our software without any issues. I also tryed to create a package with our SQL version and got the same error so it doesnt seem to have to to with the version as I had speculated earlier. I am going to go back over my process and see if there is something I am doing different and then try packaing without any customizing of shortcuts, etc.
Is there anything that is a major no no like naming conventions, etc?
After I press ok to this error I do get the foolowing but it is probably just a generic prompt.
"An internal error has occurred while saving the package The package file could not be saved. Please contact your system administrator"
Thanks to everyone for your help on this, I appreciate it!
C:\Program Files\Softricity\SoftGrid Sequencer\Logs
I assume that means that the sft-seq-log.txt that the error is referencing is included in that exclusion?
I checked the sft-seq-log.txt and here is where it goes haywire.
[03/06/2007 16:25:45 VRB CORE] Reading index header...
[03/06/2007 16:25:45 VRB CORE] Reading index header...
[03/06/2007 16:25:45 VRB CORE] Encoding blocks...
[03/06/2007 16:25:46 ERR ] CSGApplicationManager::FindSuiteByProcessId PID 0x8110 FAILED (0x 2)
[03/06/2007 16:25:48 ERR ] CSGApplicationManager::FindSuiteByProcessId PID 0x8110 FAILED (0x 2)
" "
I feel like I must be doing something wrong but cant think of anything that I am doing that is different from the last time it worked. I was able to successfully package 3 versions of our software without any issues. I also tryed to create a package with our SQL version and got the same error so it doesnt seem to have to to with the version as I had speculated earlier. I am going to go back over my process and see if there is something I am doing different and then try packaing without any customizing of shortcuts, etc.
Is there anything that is a major no no like naming conventions, etc?
After I press ok to this error I do get the foolowing but it is probably just a generic prompt.
"An internal error has occurred while saving the package The package file could not be saved. Please contact your system administrator"
Thanks to everyone for your help on this, I appreciate it!
Posted by:
kkaminsk
17 years ago
Hmm the sequencer puts nice Win32 error codes in there so the 0x2 should be file not found.
http://help.netop.com/support/errorcodes/win32_error_codes.htm
But the problem with your log snippet is that it is not showing a filename before the 0x2.
http://help.netop.com/support/errorcodes/win32_error_codes.htm
But the problem with your log snippet is that it is not showing a filename before the 0x2.
Posted by:
ksaunam
17 years ago
It's probably not looking for file but rather some process from the system (... FindSuiteByProcessId PID 0x8110 ...) that it then cannot found.
The whole sharing violation -thing seem to indicate something else besides Sequencer itself might be accessing the sequencer logfile (or alternatively Sequencer itself internally accesses it in some unexpected manner).. what if you try to run Sysinternals (well, Microsoft's ;-) Process Monitor on the sequencer machine while doing the save operation. Set filters to watch that logfile and see which processes access it?
The whole sharing violation -thing seem to indicate something else besides Sequencer itself might be accessing the sequencer logfile (or alternatively Sequencer itself internally accesses it in some unexpected manner).. what if you try to run Sysinternals (well, Microsoft's ;-) Process Monitor on the sequencer machine while doing the save operation. Set filters to watch that logfile and see which processes access it?
Posted by:
windmiller
17 years ago
I ran ProcessMon and the only thing that accessed the sft-seq-log.txt was VMWARE. Since I was able to complete a few packages previously this seems strange that Vmware might be the issue. I have a fresh machine without VMware that I am going to try this on today.
Posted by:
kkaminsk
17 years ago
I had one app that would only run correctly if VMWare tools was installed. Didn't matter if the machine was physical or virtual. I wasn't on site to see if there was a better solution but don't ask me what is in the VMWare Tools footprint that would fix a Crystal Reports issue.
Posted by:
ksaunam
17 years ago
ORIGINAL: kkaminsk
I had one app that would only run correctly if VMWare tools was installed. Didn't matter if the machine was physical or virtual. I wasn't on site to see if there was a better solution but don't ask me what is in the VMWare Tools footprint that would fix a Crystal Reports issue.
That sure is interesting case.. maybe some C++ runtime files or such were installed by vmware tools that incidentally Crystal was also using (but not installing itself)?
Posted by:
kkaminsk
17 years ago
The best I could get with troubleshooting the error was dependency walker showing a float inact result from a DLL call to the system to get date / time information. We did have the latest C++ runtimes as part of the core install but it took me many hours just to figure out VMWare tools had something to do with the issue. They ended up putting the app on a virtual server and called it a day.
Posted by:
windmiller
17 years ago
I finally had some time to test again. When I removed the Vmware variable and setup the sequencer on a physical machine I kept getting the error, this time the culprit was McAffee. What is strange and correct me if I'm wrong but shouldn't the exceptions take care of these applications accessing the log file?
I finally built a machine with just XP w/ SP2, i386 folder and completely patched. We'll see how it goes, my guess is that it will work but I was oping to be able to use this with VMware.
I finally built a machine with just XP w/ SP2, i386 folder and completely patched. We'll see how it goes, my guess is that it will work but I was oping to be able to use this with VMware.
Posted by:
ksaunam
17 years ago
But did you have that McAfee on VM as well? As general rule, antivirus and sequencing together is pretty much no-no because AV might mess up with things when it does on-access scanning (as you witnessed with your physical machine).
Sequencer exceptions only affect (or should I say, sometimes affect) on what Sequencer adds or more accurately NOT add to the virtual environment when it detects that something changes during installation and launch phases.
Sequencer exceptions only affect (or should I say, sometimes affect) on what Sequencer adds or more accurately NOT add to the virtual environment when it detects that something changes during installation and launch phases.
Posted by:
ConanTheDeployer
17 years ago
Hi all,
I got this error with my Cognos Impromptu Administrator sequence. During sequencing I specified to install to the Q:\IMPADM71.001 folder, but I noticed that the Cognos installer also installed some files to the root of Q:
I figured that this might be the problem, so I re-sequenced the whole thing while installing to Q:\IMPADM71.001\cer3
The extra installation files now where installed into the Q:\IMPADM71\ folder. All other specs were not changed.
This sequence functioned properly without the error right from the start!
Perhaps this info can be useful to someone out there....
I got this error with my Cognos Impromptu Administrator sequence. During sequencing I specified to install to the Q:\IMPADM71.001 folder, but I noticed that the Cognos installer also installed some files to the root of Q:
I figured that this might be the problem, so I re-sequenced the whole thing while installing to Q:\IMPADM71.001\cer3
The extra installation files now where installed into the Q:\IMPADM71\ folder. All other specs were not changed.
This sequence functioned properly without the error right from the start!
Perhaps this info can be useful to someone out there....
Posted by:
Jurjen
16 years ago
As a best practice we always sequence to a subfolder beneath the assetdir. Like Q:\ASSETDIR.XXX\AppName\
Tip: replace c:\program files\ by your q:\assetdir.xxx\.
Jurjen
Tip: replace c:\program files\ by your q:\assetdir.xxx\.
Jurjen
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.